Re:Poor developer estimates, a.k.a. guesstimation
by jacques_chester on Sunday September 15, 2013 @07:38PM
(#6390788)
> The point is, you are unable to know the worst possible outcome. Since it will have huge input into your average, your average is therefore useless.
Unbounded worst cases don't happen on every project.
Re:Poor developer estimates, a.k.a. guesstimation
by jqjester on Monday September 16, 2013 @12:29AM
(#6391629)
They don't have to be unbounded to be destructive to this estimation method, just large and unknowable.
Re:Poor developer estimates, a.k.a. guesstimation
by jacques_chester on Monday September 16, 2013 @02:54AM
(#6391978)
All estimates, in theory, have large and unknowable corner cases. Your problem may require the invention of a new algorithm. Your office may burn to the ground. An asteroid the size of Rhode Island could strike the planet. And so on.
All estimates are uncertain because there is no knowledge of the future. This is true of every profession, of every project.
When we make estimates we have to accept that they are uncertain and that the degree of uncertainty is governed partly by the problem domain.
A quote from Michael O'Church I quite like:
The point is, you are unable to know the worst possible outcome. Since it will have huge input into your average, your average is therefore useless. Perhaps the project isn't specced fully enough and, during implementation, a dev discovers an ugly or impossible feature interaction. You now have to either cut features or rearchitect another feature, ie the dice come up 10 in Michael's analogy.An example from my background: I work on ml code. A learning algorithm was written in parallel with a particular loss function (essentially, this tells you if your estimates are good or bad). The person writing the spec assumed that a different loss function could be dropped in later. Indeed, this is how the math works on paper. But loss function number 2 required a different data layout between the machines. The vision was writing a new loss function should be one or two lines of code dropped into the middle of a hot loop; the reality was it took almost a month of work.
[1] https://news.ycombinator.com/item?id=3522910