10 ms·
I must strongly disagree with the article. The problem and its true cause are well known. Manager: "How long will it take to build X." Experienced developer:
by droithomme 14y ago
I must strongly disagree with the article. The problem and its true cause are well known.
Manager: "How long will it take to build X."
Experienced developer: "I'll need a couple weeks to prepare an estimate."
Manager: "I don't have two weeks. Just a rough estimate, no pressure."
Developer: "This is a big project with a lot of uncertainties, with Abdul, Karen, and Jim, we might be able to get it done in 12-18 months, minimum, assuming there are no scope changes."
Manager: "No, that's wrong, we need it in three weeks maximum, and you can only have Amy."
Developer: "The new girl? It will take months just to get her up to speed with the skills. It's impossible."
Manager: "Make it possible."
Developer: "Wishing doesn't make it possible."
Manager: "You geeks are unprofessional and your bad attitude is damaging the company. Where is the can-do team spirit like the sales team has?"
Later...
Executive: "How long will it take for the new project?"
Manager: "Five weeks, just like you wanted, assuming the dev doesn't spend the time posting on the internet."
Executive: "Good I am giving the project the green light then."
One, two, three and four weeks later:
1: "Here are some scope changes."
2: "Here are some change requests."
3: "This should be done completely differently."
4: "The way ABC works has been changed to DEF. Should just be a minor tweak."
End of five week death march:
Executive: "Why is this not done?"
Manager: "The stupid geeks are unprofessional! Please refer to this chart I found on the internet about how these losers don't know how to estimate!"
- ThomPete 14y agoEven with a couple of weeks the risk of the estimate being wrong is high.