Re:Poor developer estimates, a.k.a. guesstimation
by jacques_chester on Tuesday September 17, 2013 @08:12PM
(#6402681)
Wow. I don't take it personally. I gather that your internal process requires all changes to have estimates, regardless of task.
Estimates can be performed multiple times. Conceptually what you've done here is performed 3/4s of the total work (study the change, identify change points, perform basic design) before proceeding to estimate.
You've come across the Cone of Uncertainty in miniature: all that extra work substantially reduced uncertainty and so the estimate range was tiny.
But because of the size of the task, you have a clearly pathological case where estimation had a net negative value. This is a good case of where proceeding directly to the work would have been more effective.
Estimates can be performed multiple times. Conceptually what you've done here is performed 3/4s of the total work (study the change, identify change points, perform basic design) before proceeding to estimate.
You've come across the Cone of Uncertainty in miniature: all that extra work substantially reduced uncertainty and so the estimate range was tiny.
But because of the size of the task, you have a clearly pathological case where estimation had a net negative value. This is a good case of where proceeding directly to the work would have been more effective.
In your position I'd be pissed off too.