Humans are notoriously terrible at estimating how long complex tasks will take, a phenomenon known as the Planning Fallacy. When asked for an estimate, developers and managers typically provide a single number based on a best-case scenario where no unforeseen issues arise.
When tasks are estimated with single data points and stacked together, the probability of the entire project finishing on time approaches zero, because a delay in any single dependent task cascades through the entire timeline.
The PERT Estimation Formula
To counter this optimism bias, the US Navy developed the Program Evaluation and Review Technique (PERT) in the 1950s. Instead of one estimate, PERT requires three: an Optimistic time (O), a Most Likely time (M), and a Pessimistic time (P).
The PERT formula calculates a weighted average that heavily favors the Most Likely estimate while accounting for the extremes: Expected Time = (O + 4M + P) / 6. By forcing estimators to explicitly define a pessimistic worst-case scenario, the final calculated expected time is inherently more realistic and risk-adjusted.
Calculating the Standard Deviation
PERT also allows project managers to mathematically quantify the uncertainty of an estimate using Standard Deviation. The formula for the standard deviation of a PERT estimate is: (P - O) / 6. A larger spread between the pessimistic and optimistic bounds results in a higher standard deviation.
If Task A has an expected time of 10 days with a standard deviation of 1 day, it is highly predictable. If Task B has an expected time of 10 days with a standard deviation of 5 days, it is highly risky. Understanding this variance allows managers to allocate contingency buffers precisely where the uncertainty is highest in the project timeline.