3 ms·
There was a submission on this (in the annals of HN) where someone made the point that, more often than not and under normal project scenarios, unexpected probl
by ethbr0 6y ago
There was a submission on this (in the annals of HN) where someone made the point that, more often than not and under normal project scenarios, unexpected problems usually do derail the entire software engineering plan.
The gist being: estimates are given with zero as a lower bound, and some upper bound. In reality, there is no upper bound. Software engineering can and does involve unexpected problems that would take infinite time to solve.
Ergo, project timelines are more accurately averaged between {min_time} and {infinite}, and, given that, remaining risk is the only true metric that should be reported. I.e. how far are we along in terms of project completed, such that we can say only x% of the project remains, and therefore that 1-x% did not explode.
- imtringued 6y agoThe fundamental problem with estimates is that the recipient believes that the estimate will always turn out to be true, which is obviously not correct. So, why can't we express the upper bound in combination with uncertainty? Example: "There is a 50% chance that the feature will be delivered within 1 month." As time progresses confidence starts increasing and we get closer and closer to how much time it actually takes (be that 5 days, 5 months or 5 years). On the day the feature is completed, confidence is 100% because the real delivery date has become known.