Critical Path Method (CPM)

How the Critical Path Method Works

The critical path method is a scheduling technique that identifies the longest chain of dependent tasks from project start to project end. This chain, called the critical path, determines the earliest possible completion date. Any delay to a task on the critical path delays the entire project by the same amount. Tasks not on the critical path have float (schedule flexibility) and can slip without affecting the end date.

CPM was developed in the late 1950s by DuPont and Remington Rand for managing plant construction and maintenance projects. It was developed independently of PERT around the same time, and the two techniques are often used together: CPM for scheduling and PERT for estimation under uncertainty.

The method works through a two pass algorithm. The forward pass calculates the earliest start (ES) and earliest finish (EF) for every task by moving from project start to project end, adding durations and respecting dependencies. The backward pass calculates the latest start (LS) and latest finish (LF) for every task by moving from project end to project start, subtracting durations. The difference between latest and earliest times for each task is its float.

The Forward and Backward Pass

In the forward pass, each task’s earliest start equals the latest earliest finish of its predecessors. Its earliest finish equals its earliest start plus its duration. When two paths merge at a task, the later of the two earliest finish dates governs.

In the backward pass, each task’s latest finish equals the earliest latest start of its successors. Its latest start equals its latest finish minus its duration. When a task feeds into multiple successors, the earliest of the latest start dates governs.

Tasks where ES equals LS (and EF equals LF) have zero float. These tasks are on the critical path. Any delay to these tasks delays the project. Tasks where LS is greater than ES have positive float. They can start later than their earliest start without affecting the end date.

Total Float vs Free Float

Total float is the amount of time a task can be delayed without delaying the project end date. Free float is the amount of time a task can be delayed without delaying the start of any successor task. Free float is always less than or equal to total float. A task with total float but zero free float can slip without delaying the project but will delay its immediate successor.

Key Characteristics

A project can have multiple critical paths if two or more paths through the network have the same longest duration. Multiple critical paths increase schedule risk because a delay on any of them delays the project.

The critical path can change during execution. If a non critical task slips beyond its float, it may create a new critical path. If a critical path task finishes early, a previously non critical path may become the new critical path. This is why critical path analysis is not a one time exercise but an ongoing management activity.

Near critical paths (paths with very small float, such as 1 to 2 days) deserve almost as much attention as the critical path itself. A minor slip on a near critical path can make it the new critical path.

When to Use Critical Path Analysis

Any project with 20 or more tasks and meaningful dependencies benefits from critical path analysis. Without it, the project manager cannot distinguish between tasks that affect the end date and tasks that have schedule flexibility. This distinction is essential for prioritization: when resources are constrained, critical path tasks get priority.

Construction and engineering projects use CPM as their primary scheduling method because the work involves long chains of physical dependencies (foundations before framing, framing before electrical, etc.) where sequence cannot be changed.

Software development projects benefit from CPM during integration phases where multiple workstreams converge and dependencies determine whether the release date holds. During earlier development where work is more parallel and independent, critical path analysis is less informative.

Projects with hard deadlines (regulatory submissions, contract milestones, event launches) need critical path analysis because it is the only way to determine whether the deadline is achievable and which tasks must stay on schedule to meet it.

When Not to Use Critical Path Analysis

Short projects (under 2 weeks) with a small team and minimal dependencies do not need formal CPM. The sequence is obvious and the overhead of the forward/backward pass exceeds the benefit.

Agile teams working in sprints typically do not apply CPM to individual sprints because the work is designed to be largely independent within a sprint. At the program level, however, CPM is valuable for coordinating release dependencies across multiple teams.

Projects where all tasks are independent (no dependencies) have no meaningful critical path. Every task is effectively its own critical path. This is rare in practice but theoretically possible in highly parallel work structures.