Re:Practical Project Cost Management
by mathattack on Tuesday June 04, 2013 @09:35AM
(#5819291)
"Blimey, I don't trust anyone to effectively estimate their time over any period greater than 5 days. And I tell them to add 20%..."
I find it more accurate to double the # and bump the metric.
1 hour => 2 days 3 days => 6 weeks
Estimation is one of the hardest parts of the software management.
Agreed. I mean at some level of abstraction (EG status reporting to senior management/sponsors), rolling up sub-sub-tasks into one 20 day task would be OK but if I had direct oversight over the developers I'd aim more for 2-3 days.
Yeah, actually this is exactly what I think. I believe in agile approach, but for the old generation PMs 20 sounds better :-)
if you think construction then a 20 day subtask could be a trade for a floor
Re:Practical Project Cost Management
by anoressLucy on Tuesday June 04, 2013 @05:30AM
(#5818443)
Someone else even likes to schedule 2h tasks.... and the planning never stops!
Blimey, I don't trust anyone to effectively estimate their time over any period greater than 5 days. And I tell them to add 20%...