News for hackers. Stuff that matters.
Re:Tasking developers with creating detailed estimates is a ... by morelandjs on Friday November 19, 2021 @07:33AM (#29276507)
Exactly. One of the fundamental tenets of science is reporting estimates with appropriate precision, e.g. significant digits. If the probabilistic interquartile range spans multiple months, why would I report the mean of the estimate in "hours of effort"?

What's frustrating is I've articulated these thoughts clearly to managers in the past. They nod their head and agree and then ask for the hourly estimate again and we all collectively share our disappointment when our estimate is inaccurate after the fact.

Nothing like running head first into a wall and expecting a different result.

My management suggestion? Frequently identify and advocate for simplifications, and modulate the degree of simplification based on progress to date. If people enjoy their work, they will work hard regardless of timeline hawking. So the variable factor is really the volume and complexity of work, not worker intensity or motivation.

Re:Tasking developers with creating detailed estimates is a ... by gatlin on Friday November 19, 2021 @08:52AM (#29277089)
Yes that would mean managers have to do something, and while some are incidentally useful and productive, there are few external incentives for them to be so. Yet there are many incentives to let you burn out after hitting a wall a hundred times.