Comparing top-down and bottom-up estimates in Microsoft Project
Microsoft Project puts both estimates on the same Gantt bar and colours the difference. How to set it up in two minutes, and how to read the four cases.
Microsoft Project puts both estimates on the same Gantt bar and colours the difference. How to set it up in two minutes, and how to read the four cases.
One number on the whole project, then split downwards. It is the only method you can run at the start, and adding the phases back up proves nothing.
The most accurate method there is, and its flaw is in none of its lines. Forty small optimistic shortfalls with the same sign do not cancel: they add up.
A number that holds up even when you are not in the room, because the defence is not your seniority but a record of what your past projects actually did.
Twelve months said in January means between three months and four years. The cone narrows because decisions get taken, not because the calendar moves.
The three project estimating methods are not rivals: they live at different points on the cone of uncertainty. Where you stand decides which one you may use, and what you are allowed to promise.