# Critical Path Method

A network-scheduling method that identifies the sequence of dependent activities governing the earliest possible project completion date.

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

## What it means

The critical path method, or CPM, models activities, durations, and logical dependencies as a network. A forward pass calculates earliest start and finish dates; a backward pass calculates latest allowable dates. Activities with the least total float form the current critical path, meaning delay to them can delay the project unless later work is recovered or logic changes.

## Why it matters

CPM distinguishes schedule-driving work from activities that have flexibility. This helps managers focus analysis, contingency, and recovery decisions where delay has the greatest consequence. A sound network also reveals impossible sequencing, fragile handoffs, and the effect of proposed changes more clearly than a list of target dates can.

## When to use it

Use CPM when delivery contains meaningful dependencies and a completion date must be forecast or controlled. It is especially valuable for construction, launches, migrations, regulatory work, and integrated programmes. Recalculate it whenever actual progress, durations, calendars, constraints, or dependency logic materially change.

## How it works

1. Define activities at a controllable level and estimate durations using appropriate calendars and assumptions.
2. Connect activities with defensible predecessor and successor relationships, avoiding unnecessary date constraints.
3. Run the forward pass to find earliest dates and the backward pass to find latest dates and total float.
4. Inspect the critical and near-critical paths for missing logic, resource conflicts, risk exposure, and unrealistic estimates.
5. Update actual progress and forecasts regularly, then evaluate recovery options without damaging scope, quality, or safety.

## A practical example

A data-center migration requires hardware delivery before installation, installation before testing, and testing before cutover. Network analysis shows that delayed firewall configuration, not server installation, now governs the launch date. The team secures earlier security review and parallelizes approved test preparation rather than adding people to noncritical tasks.

## Where it breaks

Results are only as reliable as the activity logic, durations, calendars, and progress data. The critical path can shift, and several near-critical paths may be almost equally important. Basic CPM does not automatically model uncertainty or scarce resources, while hard constraints and optimistic status updates can create a misleadingly comfortable schedule.

## Common mistakes

- Calling the most important work critical without performing network calculations.
- Using fixed dates instead of complete and realistic dependency logic.
- Ignoring near-critical paths, resource limits, and changes to the critical path.
- Crashing activities without assessing cost, quality, safety, or downstream effects.

## Visualization

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

## Sources

1. [GAO Schedule Assessment Guide: Best Practices for Project Schedules](<https://www.gao.gov/products/gao-16-89g>) — U.S. Government Accountability Office · Government best-practice guide
2. [Follow the Yellow Brick Road \(the Critical Path\)](<https://www.pmi.org/learning/library/critical-path-scheduling-work-breakdown-6212>) — Project Management Institute · Professional conference paper

## Related topics

- [Work Breakdown Structure](<https://wiki.soroush.uk/topic/work-breakdown-structure/>)
- [PERT Estimation](<https://wiki.soroush.uk/topic/pert-estimation/>)
- [Gantt Chart](<https://wiki.soroush.uk/topic/gantt-chart/>)
