Can the critical path change during a project?

Yes. The critical path can change if task durations change (actual vs estimated), scope is added or removed, dependencies change, or if tasks on a near-critical path are delayed while critical path tasks are completed on time. Project managers should regularly re-evaluate the critical path throughout the project.

What is the difference between critical path and critical chain?

Critical path considers task dependencies and durations. Critical chain (developed by Eli Goldratt) adds resource constraints to the analysis, recognising that resource availability can affect the schedule as much as task dependencies. Critical chain also uses project buffers rather than padding individual task estimates.

What is crashing and fast-tracking?

Crashing adds resources to critical path tasks to shorten their duration (e.g., adding more developers). Fast-tracking runs tasks in parallel that were originally planned sequentially (e.g., starting development before design is fully complete). Both carry risks: crashing increases cost, and fast-tracking increases rework risk. They should be used judiciously when project timelines must be shortened.

Book Free Assessment Calculator

Critical Path

Also known as:CPMcritical path methodlongest path

The longest sequence of dependent tasks in a project that determines the minimum time required to complete the project - any delay on the critical path directly delays the project.

In-Depth Explanation

The critical path is the longest chain of dependent activities in a project schedule that determines the overall project duration. Tasks on the critical path have zero float (slack), meaning any delay to a critical path task directly delays the project completion date.

Critical Path Method (CPM) process:

List all activities: Identify every task needed to complete the project
Determine dependencies: Identify which tasks depend on other tasks completing first
Estimate durations: Assign time estimates to each task
Build the network diagram: Map out the task dependencies visually
Calculate the critical path: Find the longest path through the network
Identify float: Determine how much flexibility non-critical tasks have

Key CPM concepts:

Early start (ES): Earliest a task can begin
Early finish (EF): Earliest a task can finish
Late start (LS): Latest a task can start without delaying the project
Late finish (LF): Latest a task can finish without delaying the project
Float/Slack: The amount of time a task can be delayed without affecting the project end date
Near-critical path: Tasks with very little float that could become critical

Managing the critical path:

Focus management attention on critical path tasks
Assign the best resources to critical path activities
Monitor critical path progress closely
Have contingency plans for critical path delays
Consider crashing (adding resources) or fast-tracking (parallelising) to shorten the path
Re-evaluate the critical path when scope changes occur

Limitations of CPM:

Assumes task durations are deterministic (PERT addresses this with probabilistic estimates)
Does not account for resource constraints (Critical Chain Method adds this)
Network can change as the project progresses
Complex projects may have multiple near-critical paths

Business Context

Understanding the critical path helps project managers focus attention on the tasks that actually determine project duration, enabling better resource allocation and more accurate scheduling.

How Clever Ops Uses This

Clever Ops uses critical path analysis for complex client projects, ensuring that resources are focused where they have the greatest impact on project timelines. We help Australian businesses identify and manage their critical path activities to deliver projects on time.

Example Use Case

"A project manager identifies that the critical path runs through design, development, and user testing phases. When a design delay occurs, they reassign resources from a non-critical administrative task to support the design team."