PERT (Program Evaluation and Review Technique)

Definition

PERT (Program Evaluation and Review Technique) is a probabilistic scheduling method that uses three-point estimates — optimistic, most-likely, and pessimistic — for each activity duration to compute an expected duration and variance. The expected duration for each activity is the beta-weighted average:

tE = (tO + 4 × tM + tP) / 6

and the variance is σ² = ((tP - tO)/6)². Applied across a network, PERT produces an expected project duration and a confidence interval around it. Where CPM answers "when will it finish?" with a single date, PERT answers "with what confidence?"

History

PERT was developed in 1958 by the U.S. Navy Special Projects Office, Booz Allen Hamilton, and Lockheed for the Polaris submarine missile programme. The challenge was managing 9,000 contractors on a project whose components were largely first-of-a-kind and whose durations were genuinely uncertain. PERT and CPM emerged within a year of each other (CPM at DuPont, 1957) and dominated capital-project scheduling for the next two decades before Monte Carlo simulation began to supersede PERT in heavy-risk environments.

PERT vs CPM

• CPM uses single-point durations and assumes the plan is the truth. It is best when activities are well-understood and uncertainty is low.
• PERT uses three-point durations and produces a probability distribution. It is best when activities are novel and uncertainty is high.
• Monte Carlo generalises PERT to thousands of iterations and arbitrary input distributions. It supersedes PERT when computing power is available, but PERT remains useful as a quick analytical approximation.

Principles

• Three-point estimates are elicited, not invented. The optimistic, most-likely, and pessimistic values should come from discipline leads with field experience, not from desk-bound planners.
• The expected duration is not the most-likely. Beta weighting shifts the expected value toward the pessimistic side because real-world distributions are right-skewed.
• The critical path under PERT is the path with the highest expected duration, not the one with the longest deterministic duration. Sometimes the two diverge.
• Variance accumulates along paths. The total project variance is the sum of variances of the critical-path activities, giving a project-level standard deviation.
• The technique assumes path independence. Strongly correlated paths violate the assumption and lead to overconfident results.

Worked Example

A foundation activity: optimistic 8 days, most-likely 12 days, pessimistic 22 days. Expected: (8 + 48 + 22)/6 = 13.0 days. Variance: ((22-8)/6)² = 5.44 days². Across a 12-activity critical path, total expected duration is the sum of activity expecteds; total variance is the sum of activity variances; project standard deviation is the square root. A project with expected 240 days and standard deviation 18 days has roughly a 68% probability of finishing within ±18 days, a 95% probability within ±36 days. That confidence band is what PERT contributes beyond CPM.

Real-World Construction Example

On a deep-water port construction project, the deterministic CPM schedule showed 30 months to completion. The owner challenged the contractor to produce a confidence range. A PERT analysis on the 87 critical-path activities produced expected duration 32.4 months with a standard deviation of 2.3 months. The 80th-percentile completion came in at 34.4 months, the 95th-percentile at 36.2 months. The owner used the analysis to negotiate a realistic external commitment at P80 and to focus risk mitigation on the seven activities contributing 70% of total variance. The CPM plan had been understated by four months; PERT exposed it before the contract was finalised.

Real-World IT / Agile Example

An infrastructure migration team facing genuinely novel workstreams used PERT for release planning. For each major workstream they elicited three-point estimates from the two most experienced engineers. The aggregate expected release date was six weeks later than the original deterministic plan; the standard deviation was four weeks. The team committed externally to expected + 1.28σ (P90), used expected as the internal target, and tracked actuals against the distribution monthly. The technique reduced the rate of broken external commitments from roughly one in two to one in eight over the next three releases.

Project Controls Perspective

Controls teams use PERT as an entry-level quantitative-risk tool — easier to run and explain than full Monte Carlo, but capturing most of the benefit on modest networks. A common pattern is PERT at concept and feasibility stage to set realistic targets, then a full Monte Carlo at detailed-design baseline when more granular logic and correlations are available. The two are complementary, not competing.

Common Mistakes

• Using three-point estimates that all cluster narrowly — the planner has guessed instead of elicited.
• Assuming path independence on networks where several paths share common predecessors.
• Forgetting that the PERT critical path may differ from the CPM critical path.
• Quoting the expected duration as the commitment date, ignoring the uncertainty.
• Mixing PERT outputs with CPM milestones inconsistently in reports.
• Treating PERT as obsolete just because Monte Carlo exists; for many projects PERT is more than adequate and more comprehensible to stakeholders.

Expert Tips

• Elicit three-point estimates in workshops using calibration techniques — asking "if you bet your bonus on this, what range would you stake?" produces more honest values.
• Compare PERT expected to CPM duration. Significant divergence is itself a finding — usually that CPM optimism has crept in.
• Report PERT outputs as confidence ranges, not single dates. "P80 in October; P50 in August" communicates risk truthfully.
• Use PERT at concept stage; switch to Monte Carlo at detailed baseline. Each tool fits its phase.
• Re-run PERT after major scope or risk changes. The distribution shifts; the commitment date should follow.

Key Takeaways

• PERT uses three-point estimates and produces a probability distribution rather than a single date.
• Expected duration is beta-weighted: (O + 4M + P)/6.
• The PERT critical path may differ from the CPM critical path; check both.
• Quote outcomes as P50, P80, P90 ranges to communicate uncertainty honestly.
• PERT and Monte Carlo are complementary tools, not competitors.

Related Concepts

PERT interlocks with CPM, Monte Carlo Simulation, Network Diagrams, Uncertainty Analysis, and Risk Management. Worked PERT calculations and templates are at PMMilestone.org.