Underestimation
Still do it. Should know better, but I still do it. "Yep, I should get that finished by the end of the day."
Let's see I'll need to write Fixtures for those tests - get something passing - extract some stuff out into production. Oh and there's those couple of edge cases. Should be finished by lunchtime; I'll say end of the day to be sure.
Idiot. You need to estimate tasks and add up the estimates. It's not difficult you lazy git. Slap on back of head.
Update: after spending two minutes on a proper estimation I have 9 hours left on the story. I've already spent a day. Slap 2, coming up.
![Contact email to pwjobs [[ at ]] merecomplexities.com](email.gif)
1 Comments:
"You need to estimate tasks and add up the estimates."
But that's how I usually end up regularly underestimating - because I forget a task (especially a non-programming process task) or fail to imagine how one of the tasks will go extravagantly wrong.
I find that yesterday's weather is consistently a better estimate than my best one from first task-breakdown principles.
I am a particularly chronic optimist though, very vulnerable to Hofstadter's Law, and perhaps there's a way of blending the two (weather on the individual tasks and/or "what tasks came up when I tackled something like this yesterday?")
Post a Comment
<< Home