2 ms·
"Artificial Deadlines" are typically tied to some sales or marketing cycle. (ie We're announcing the launch of product ACME WidgetFoo at FooConf2013.) If you'r
by parsnips 13y ago
"Artificial Deadlines" are typically tied to some sales or marketing cycle. (ie We're announcing the launch of product ACME WidgetFoo at FooConf2013.)
If you're truly a member of a "team" (one that includes the positions of Marketing and Sales), hard deadlines are simply a fact that cannot be avoided (unless say, you're Apple Inc).
The key is for everyone to understand the difference between aspirational goals, and deliverable goals for the deadline.
If you're fighting this battle constantly, I'd take that as a sign that you're not a player on the team. Ball boy.
- stevedt 13y agoMore generally, when you are coordinating activity with others. If the code being deployed requires announcements to users, Help Desk people, changes to other applications, changes do documentation, etc., then these are not "artificial" at all.
- parsnips 13y agoWell put. It's all about context. Understanding your role and how to influence the result is part of the "game". You do not escape the "game" by being good at coding most times.