Re:Laws of Software Estimation for Complex Work
by doctor_eval on Tuesday December 20, 2022 @02:37AM
(#34062790)
But then there’s Hofstadter’s law: It always takes longer than you expect, even when you take into account Hofstadter's Law.
Re:Laws of Software Estimation for Complex Work
by fhd2 on Tuesday December 20, 2022 @02:27AM
(#34062735)
Let's call it what it is: Guessing. Guessing can be incredibly useful, and I've never seen an engineer or PM refuse to _guess_ (or "project"), because that implies they won't be held to it.
Re:Laws of Software Estimation for Complex Work
by commandlinefan on Tuesday December 20, 2022 @11:03AM
(#34067780)
> trying to estimate things is bad
I've never, not once, in 30 years of developing software professionally, seen a feature request that was well defined enough to estimate to any level of accuracy. The definitions are always so vague that the answer could range from "this is already done" to "this is not possible". The hard part, and what takes the most time, is always working out exactly what they want - and that's what they want (and expect) an estimate of. "Estimate how long it's going to take you to figure out what exactly it is that I'm asking for."
I will say I think that holding people to estimates is not fair because it doesn’t necessarily correlate with productivity/value added. When asked for estimates my general rule is: take a conservative estimate and double it.