# PERT Estimation

A three-point estimation method that combines optimistic, most likely, and pessimistic durations to represent uncertainty in project activities.

- Type: method
- Domain: Delivery & agility
- Level: Advanced
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/pert-estimation/>)

## What it means

PERT estimation comes from the Program Evaluation and Review Technique. For an activity, estimators provide optimistic, most likely, and pessimistic durations based on stated conditions. The classic expected duration is calculated as \(optimistic + four times most likely + pessimistic\) divided by six, giving the most-likely estimate greater weight while retaining information about uncertainty.

## Why it matters

A single estimate hides the range of plausible outcomes and encourages false precision. Three-point discussion exposes assumptions, unusual failure modes, and disagreement among knowledgeable contributors. Used with network analysis, PERT can improve schedule conversations and help teams identify activities whose uncertainty deserves mitigation, contingency, or further investigation.

## When to use it

Use PERT when activity durations are uncertain, historical data are limited, or work is novel enough that one deterministic estimate would be misleading. It suits research, engineering, migration, integration, and other dependency-rich projects. For high-stakes commitments, supplement it with reference data or simulation rather than relying on the formula alone.

## How it works

1. Define the activity, completion criteria, estimating unit, dependencies, resources, and conditions consistently.
2. Estimate an optimistic duration under credible favorable conditions, not an impossible best case.
3. Estimate the most likely duration and a pessimistic duration that reflects credible adverse conditions.
4. Calculate the weighted expected duration and record the range, assumptions, and major uncertainty drivers.
5. Use estimates in the schedule, test sensitivity, update them with evidence, and escalate material uncertainty.

## A practical example

A team estimates a legacy-data conversion at six days if mappings are clean, ten days under normal conditions, and twenty-two days if undocumented exceptions appear. The PERT expected duration is about eleven days. The wide range prompts an early data sample and a contingency plan instead of presenting eleven days as a guarantee.

## Where it breaks

The familiar formula depends on simplifying assumptions about distributions, independence, and the stability of the critical path. Estimates can still reflect anchoring or political pressure, and a weighted average can conceal a consequential downside. Summing expected durations is not the same as calculating a reliable completion probability for a complex network.

## Common mistakes

- Choosing optimistic and pessimistic values without stating the conditions behind them.
- Treating the weighted result as a commitment rather than an expected value.
- Ignoring correlation, critical-path changes, and shared sources of delay.
- Using three invented numbers when relevant historical or reference-class data exist.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/pert-estimation/#visualization-pert-estimation>)

## Sources

1. [Scheduling Guide for Program Managers](<https://s3vi.ndc.nasa.gov/ssri-kb/static/resources/Scheduling%20Guide%20for%20Program%20Managers%20Oct%202001.pdf>) — U.S. Department of Defense and NASA Systems Engineering Resources · Government scheduling guide
2. [An Assessment of PERT as a Technique for Schedule Planning and Control](<https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19820026105.pdf>) — NASA Technical Reports Server · Government technical memorandum
3. [Gate 2 Review: Delivery Strategy](<https://www.gov.uk/government/publications/gate-review-2-delivery-strategy/gate-2-review-delivery-strategy>) — UK Infrastructure and Projects Authority · Government assurance guidance

## Related topics

- [Critical Path Method](<https://wiki.soroush.uk/topic/critical-path-method/>)
- [Gantt Chart](<https://wiki.soroush.uk/topic/gantt-chart/>)
- [Risk Register](<https://wiki.soroush.uk/topic/risk-register/>)
