methodatlas
RunsheetDecision Making

PERT Estimation

ComplexityMedium
Time15-45 min
Participants1-8
FormatWorkshop + async
MaturityCanonical
01

Prerequisite

What needs to be finished first

Three values (O, M, P) per estimate item are collected or will be collected in the same session, including assumptions for each value.

Without: Without O/M/P triples, there is nothing the PERT formula can weight, so the method cannot be used.
02

Preparation

What needs to be ready before start

Materials

Estimation sheet with columns for item, O, M, P, expected value (PERT), standard deviation; estimate-item document; assumption list; calculator or sheet formula.

People / roles

A facilitator who collects values and makes the formula transparent; an estimation team (1-8 people); a scribe for assumptions and risk classification.

Pre-read

Estimate-item description; assumptions per O/M/P; list of risks that drive P; desired confidence level (1, 2, or 3 sigma).

Time needed

15-45 min

Setup

Prepare a sheet with formulas: expected value = (O + 4M + P) / 6, standard deviation = (P - O) / 6, range with ±1 sigma (68%), ±2 sigma (95%). Make each column definition visible.

03

Core question

The one question this method answers

What weighted expected value and confidence interval result from the three estimate values, and is that enough for the planning decision at hand?

04

Flow

Marker: Phase

StepDurationActionHint
1Phase 1: Capture three values
10-20 minCollect O, M, P per item with the estimation team (see Three-Point Estimation runsheet). Document assumptions for each value.If O/M/P values are taken from a prior estimate, update assumptions. Outdated assumptions lead to a wrong expected value.
2Phase 2: Apply formula
5 minPer item, calculate expected value with (O + 4M + P) / 6. Calculate standard deviation with (P - O) / 6. Enter values in the sheet.4M weighting is the core heuristic of the method. Equal weighting produces Three-Point, not PERT.
3Phase 3: Derive confidence interval
10 minCalculate expected value ± 1 sigma (68% confidence) or ± 2 sigma (95%) and choose the level that fits the planning situation.Normal distribution assumptions are sensitive for single items. The confidence interval is a guide, not a statistical guarantee.
4Phase 4: Aggregate and align risk
10-15 minFor project-level estimation, sum expected values. Calculate standard deviation of the total (square root of the sum of variances). Compare with the risk list: do assumptions match the risk assessment?Summed standard deviation is only valid for independent items. With dependencies (all items share the same engineer), dispersion is higher and assumptions must be documented.
05

Artifact

What comes out at the end

Form

Estimate table with columns for item, O, M, P, expected value (PERT), standard deviation, confidence interval, assumptions, and risks. Aggregated totals at the end of the table. Linked to the estimate-item document.

Versioning / ownership

Create a snapshot for each estimation round with date and assumptions version. For re-estimation, add a new row and keep old values with status. Aggregated values must be reproducible from item-level data.

Tool alternatives
  • Google Sheet with PERT formulas
  • Excel with Monte Carlo add-in for distribution simulation
  • MS Project with PERT view
  • Notion database with formula properties
  • Confluence page with embedded table

pert-estimation-working-template.md

Compact working template for PERT Estimation with context, input, output artifacts, and next step.

PERT Estimation Working Template

Goal

Weights three-point estimates, typically with the formula O plus 4M plus P divided by 6.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • PERT Estimate:
  • Expected Value:
  • Risk Notes:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

06

Example output

Concrete filled scenario, fictional example

pert-estimation-beispiel.md

Concrete filled scenario, fictional example

PERT Estimation - Tenant Data Migration, 2026-05-18

Estimate item: Migration from MariaDB to PostgreSQL for around 12,000 tenants. Unit: person-weeks.

ItemOMPPERTSigma95% range
Schema mapping1363.20.81.6 - 4.8
Data migration script25125.71.72.3 - 9.1
Test migrations1252.30.70.9 - 3.7
Cutover weekend0.5131.30.40.5 - 2.1
Total4.5112612.52.28.1 - 16.9

Assumptions: Items are treated as independent (shared engineer is a violation of this assumption; a 20% ramp is recommended).

Recommendation: Plan value 13 person-weeks, range 8-17, with a 10-20 dependent-task increase when adjusted for dependency.

Open risks: Compliance audit date is not fixed (spike @ben by 25.05.).

07

Pitfalls

Recognize symptoms and steer against them

Trap

Wrong weighting

Symptom

Expected value is calculated as (O+M+P)/3, and M weighting is missing.

What to do

Use formula (O+4M+P)/6 strictly. Without 4M weighting it is Three-Point, not PERT. Validate sheet formulas before the workshop.

Trap

Overstated statistics

Symptom

The 95% confidence interval is communicated as a guaranteed range.

What to do

Confidence interval is based on normal distribution assumptions, which do not hold strictly for single items. Present it as guidance, not as statistical certainty.

Trap

Aggregation ignores dependencies

Symptom

Standard deviations are summed (instead of taking the square root of summed variances), or items share resources but are treated as independent.

What to do

Use square root of variance sum for aggregation. For shared resources, add a 10-30% sigma uplift. Document the assumption explicitly.

Trap

Values without assumptions base

Symptom

The table is full of numbers, but no one can explain why O is so low or P so high.

What to do

Assumptions per O/M/P are mandatory. A PERT formula without an assumptions log is number choreography. After re-estimation, no one will understand what was assumed.

Trap

Expected value becomes commitment

Symptom

Stakeholders treat the PERT expected value as a delivery promise while sigma and range disappear from presentations.

What to do

Consistently report expected value, range, and confidence level together. Stakeholders using only expected value misuse the method.

08

Stop criteria

Done signals checkable in under a minute

No three values captured per item; PERT formula has no basis.
The estimation team does not understand 4M weighting, creating formula misuse risk.
Items are very small (<1 day); PERT overhead is not justified.
Stakeholder accepts only a point estimate and suppresses range reporting.
Assumptions per O/M/P are missing and values are not reproducible.
Estimation team lacks domain knowledge or risk perspective, so values are guessed.
High dependencies exist between items, and simple aggregation would produce a wrong range.

Finished the runsheet?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.