2 ms·
From my experience it is always the simple 80/20 rule. The last 20% takes around the same time as the original 80% estimate. 1. Break down "project" in small e
by ksec 5y ago
From my experience it is always the simple 80/20 rule. The last 20% takes around the same time as the original 80% estimate.
1. Break down "project" in small enough Tasks. Measured in days or weeks and not in months. The scale and margin of error tends to be wrong once you are in the months category.
2. Ask your frontlines ( Engineers, Sales or whoever that is doing the actual work ) to do Estimate for 80% of those task. Not their Managers. You should also know their personalities in their numbers. Some give you numbers that are too conservatives, some are too aggressive. And needs to be adjusted accordingly.
The total Add up Estimate for the project will be the time for you to reach 80% of your Goal. This tends to be +/- 20% accuracy.
The remaining 20% will somehow take the same amount of time for your initial 80%. The reason for that is in tech speak, we are very good at measuring and estimating bandwidth, but absolutely appalling at measuring and understanding context switching and latency. The amount of small things are the remaining 20%.
So if the original estimate of 80% is 10 months, the worst case scenario would be 10 months + 20% = 12 Month and doubling that to 24 months. And if you are the top of the line project manager, you should also expect that 24 months to be within +/- 20% accuracy. i.e You should report your number as 28 months to your line of report to save your ass.
I find this rules to be reasonably good. Ignoring catastrophic failure and other external factors. I mean if your whole team quit mid way there is no way your original estimate could factor those in. Remember, estimate are, just guesses. There is absolutely no way to be certain. I think this rule is simple and straight forward enough to be used across any industry.