3 ms·
I think one common problem with estimates is the assumption that all estimates are equal. We all know they're not, unless it's an estimate for something where t
by Silhouette 15y ago
I think one common problem with estimates is the assumption that all estimates are equal. We all know they're not, unless it's an estimate for something where the developer has solved a similar problem several times before.
Otherwise, you might have only a general feel for the magnitude of the problem at first: this is a 6-12 month kind of project. Perhaps a few days of prototyping and proof-of-concept tests will narrow that down a bit, though: we'll do the work in three stages, likely to take 2-3 months, 2-3 months and 3-4 months respectively, putting us in a 7-10 month window. As each stage develops, the reliability of any estimate for remaining time tends to increase, and perhaps a clearer idea emerges for the later stages as well.
In short, an estimate isn't worth much without some indication of confidence attached to it.
FWIW, my personal preference is to aim for about four qualitative levels: very general magnitude from initial overview of the project, more systematic estimate after clarifying detailed requirements and probably a bit of prototyping or proof-of-concept work, definite target date unless unexpected major disruption or change of requirements happens, and very confident once the project is into the final stages and no major hurdles remain.