Wednesday, August 19, 2009

Consumer Report Corn Stove

On the timing

short, the set time the project so, as if it depends YOUR LIFE.

Typical a conversation between two managers:
- Oleg, how much is it in your estimations take?
- I think a week

After this deadline driven into the plan and show leadership.
Notes:
1) no one manager is not an active developer of the product, the problem is discussed
2) is not one of the managers is not an expert in this area
3) According to the developers did not ask, although it was available

Where did this term? Why was he driven into the plans, as it is?

Development events is obvious: the developer does not have time for Voros managers: "What is it?", he replies that there is a problem that is just and that's that, besides the problem itself have difficulty in integrating that there are special cases, etc. Terms are broken, a developer in a hurry and does not perform the necessary testing (unfortunately, not at all and do not always have a separate team of testers). The product comes out later and crappy quality - after the problem starts with his support and fix.

Another note: this situation is most typical for Stationery programming, where time is important, but their failure can hardly depend on the fate of managers themselves.

If you are a manager / project manager:
1) Ask the opinion of the developers themselves. Not satisfied with the answer "Go" - get them to estimate the development stages (see below).
2) Use the coefficient multiplying the time based on your experience rather than books and articles. Often advised to multiply the term by 1.3-1.5. I'm an optimist, so My personal ratio is 1.5-2.0 depending on the complexity and temnosti "project. 3) If you think a term called too high, ask developers on what they lay so much time. Do not profitable pushes you time - people can simply call the consternation of the term который потом сорвет, а для Вас это будет "неожиданностью". 4) Если Вы называете срок - потрудитесь вникнуть в задачу на столько, насколько это возможно.

If you are a developer:
1) Conduct a baseline study of the problem, prikinte which there can be pitfalls. Break the task into subtasks, so that You could say with certainty how long it will take time.
2) Discuss the terms with the boss - if they're too tight, tell me about it. This lchuchshe than tear term. 3) Again from the discussion, ask the manager if he lays the coefficient of multiplication in nazavnny your time - if not, adjust with срок.

В любом случае, не бойтесь сказать: "мне нужно подумать. Я отвечу в четверг." Кажется, это было в "Пути камиказе" :) И наконец, подумайте, если be due to disruption of the term you could lose your job, do not get a regular salary or your entire family would be cut to 7 th knee, would you call the period "from the ceiling?