Critical Path Method (CPM)

CPM operates on the assumption of fixed, known task durations. Unlike probabilistic methods like PERT (Program Evaluation and Review Technique), which uses three time estimates, CPM uses a single deterministic duration for each activity. This makes it ideal for projects with well-understood, repeatable tasks—such as construction or manufacturing—where historical data provides reliable estimates. The critical path is calculated by performing a forward pass to determine early start/finish dates and a backward pass to determine late start/finish dates.

A defining characteristic of CPM is the quantification of scheduling flexibility through float (or slack).

• Total Float: The amount of time a task can be delayed without delaying the project's finish date.
• Free Float: The amount of time a task can be delayed without delaying the early start of any immediately following task. Tasks on the critical path have zero total float. Any delay to a critical task directly extends the project's minimum completion time.

CPM requires explicit definition of logical dependencies between all activities. The most common is the Finish-to-Start (FS) relationship, where a successor task cannot begin until its predecessor is complete. The method also supports Start-to-Start (SS), Finish-to-Finish (FF), and Start-to-Finish (SF) dependencies, with optional lead (overlap) and lag (delay) modifiers. This dependency network forms a directed acyclic graph, which is the mathematical foundation for the forward and backward pass calculations.

Modern CPM uses the Activity-on-Node (AON) convention, where each task is represented as a node (box) and arrows represent dependencies. This contrasts with the older Activity-on-Arrow (AOA) method, which used arrows for tasks and nodes for events. AON is the standard in all modern project management software, including Microsoft Project and Primavera P6. Each node typically displays the task name, duration, early/late start and finish dates, and float values.

The basic CPM calculation assumes unlimited resources. In practice, resource availability often constrains the schedule. Resource Leveling and Resource Smoothing are extensions that adjust the schedule based on resource limits. When leveling, a new resource-constrained critical path emerges, which may differ from the original time-based critical path. This is sometimes called the Critical Chain, a related but distinct methodology that also incorporates resource dependencies and buffers.

A sophisticated application of CPM involves monitoring near-critical paths—sequences with very low total float. A path with only 1-2 days of float is statistically almost as risky as the critical path itself. Project managers use sensitivity analysis and Monte Carlo simulation (when combined with probabilistic durations) to identify these sub-critical chains. A common metric is the Criticality Index, which measures the percentage of simulations in which a given task appears on the critical path.

A statistical sibling to CPM that handles probabilistic task durations rather than deterministic ones. PERT uses a three-point estimation technique—optimistic, pessimistic, and most likely—to calculate expected durations and quantify schedule risk.

• Uses a weighted average: (O + 4M + P) / 6
• Calculates activity variance to identify schedule uncertainty
• Originally developed for the U.S. Navy's Polaris missile program
• Best suited for projects with high uncertainty in time estimates

The primary visual representation of a CPM schedule, displaying tasks as horizontal bars along a timeline. While CPM calculates the logic, Gantt charts communicate the plan to stakeholders by showing task durations, dependencies, and progress.

• Critical path tasks are typically highlighted in red
• Shows float or slack as thin lines extending beyond task bars
• Modern tools like Microsoft Project and Primavera P6 combine CPM logic with Gantt rendering
• Essential for resource leveling and what-if scenario analysis

A core metric derived from CPM analysis that identifies scheduling flexibility. Total float is the amount of time a task can be delayed without affecting the project finish date. Tasks on the critical path have zero float by definition.

• Free float: delay allowed without impacting any successor task
• Total float: delay allowed without impacting the project end date
• Negative float indicates the project is already behind schedule
• Float analysis drives resource allocation and risk mitigation decisions

The network modeling technique used to construct the activity-on-node diagrams that CPM analyzes. PDM defines four types of logical relationships between tasks that go beyond simple finish-to-start dependencies.

• Finish-to-Start (FS): Successor cannot start until predecessor finishes
• Start-to-Start (SS): Successor cannot start until predecessor starts
• Finish-to-Finish (FF): Successor cannot finish until predecessor finishes
• Start-to-Finish (SF): Rare; successor cannot finish until predecessor starts
• Enables realistic modeling of overlapping and parallel work streams

A methodology developed by Eliyahu Goldratt that extends CPM by addressing resource dependencies and human behavioral factors. CCPM replaces task safety margins with strategically placed buffers to protect the project completion date.

• Project buffer: protects the critical chain end date
• Feeding buffers: protect the critical chain from non-critical path delays
• Resource buffers: ensure resource availability at critical handoffs
• Explicitly accounts for Parkinson's Law and student syndrome