Skip to content
Tutorials Center
My learning

Topics

Lesson 18 of 41 ยท Scheduling and Critical Path

The Critical Path Method (CPM)

Learn to find the critical path: forward and backward pass, early and late dates, total and free float, with a full worked example and runnable Python that computes the schedule.

The Critical Path Method (CPM) finds the longest chain of dependent activities in a project. That chain, the critical path, determines the shortest possible project duration. Any delay on a critical activity delays the whole project; activities off the critical path have spare time called float. CPM tells you where to focus attention, which activities can slip safely and where speeding up actually helps.

The vocabulary

Term Meaning
ES (early start) Earliest an activity can start
EF (early finish) ES + duration
LS (late start) Latest it can start without delaying the project
LF (late finish) Latest it can finish without delaying the project
Total float (slack) LS - ES (or LF - EF): how much it can slip without delaying the project
Free float How much it can slip without delaying any successor
Critical activity Total float = 0

Step 1: forward pass

Move from start to end. For each activity: ES = the largest EF of its predecessors (0 for the first), and EF = ES + duration. The largest EF at the end is the project duration.

Step 2: backward pass

Move from end to start. Set the last activity's LF to the project duration. For each activity: LS = LF - duration, and the LF of an activity = the smallest LS of its successors.

Step 3: float and critical path

Total float = LS - ES. Activities with zero float form the critical path (there can be more than one).

Worked example

Using the website project from the previous lesson (durations in days): A 5, B 7, C 6, D 10, E 12, F 5, G 6, H 2.

Forward pass:

  • A: ES 0, EF 5
  • B: ES 5, EF 12. C: ES 5, EF 11
  • D: ES 12, EF 22. E: ES max(12, 11) = 12, EF 24
  • F: ES max(22, 24) = 24, EF 29
  • G: ES 29, EF 35. H: ES 35, EF 37

The project takes 37 days. Backward pass:

  • H: LF 37, LS 35. G: LF 35, LS 29. F: LF 29, LS 24
  • D: LF 24, LS 14. E: LF 24, LS 12
  • B: LF min(14, 12) = 12, LS 5. C: LF 12, LS 6
  • A: LF min(5, 6) = 5, LS 0

Floats: A 0, B 0, C 1, D 2, E 0, F 0, G 0, H 0. The critical path is A-B-E-F-G-H.

flowchart LR
    A["A 5 (crit)"]:::crit --> B["B 7 (crit)"]:::crit
    A --> C["C 6 (float 1)"]
    B --> D["D 10 (float 2)"]
    B --> E["E 12 (crit)"]:::crit
    C --> E
    D --> F["F 5 (crit)"]:::crit
    E --> F
    F --> G["G 6 (crit)"]:::crit
    G --> H["H 2 (crit)"]:::crit
    classDef crit fill:#fecaca,stroke:#dc2626,color:#111

Critical activities are highlighted. C and D have float.

Compute it with code

Python CPM forward and backward pass

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

What if we change something?

Use the same logic to test ideas. Suppose the Front end (D) slips by 3 days: does it matter? Float of D is 2, so yes, it becomes critical and the project grows by 1 day.

Python What-if: slip an activity

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Using the critical path

  • Focus management attention on critical activities; assign your best people and watch them daily.
  • Shorten the project only by shortening critical activities (see Schedule Compression). Shortening a non-critical one changes nothing, until it consumes its float.
  • Use float to level resources: slide non-critical work within its float.
  • Beware near-critical paths: with 1 day of float, C is a risk too.
  • Re-run CPM whenever durations or logic change; the critical path can switch.
  • Total float vs free float: total float is shared along a path; if one activity uses it, later activities on the path lose it.

Limits of CPM

CPM uses single-point durations (deterministic). Real durations vary, which is why PERT and Monte Carlo simulation add uncertainty. CPM also ignores resource limits unless you level them, and it assumes the logic is correct. A beautiful schedule built on wrong dependencies is a precise lie.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the critical path?

    No faster finish is possible than the longest chain of dependent activities.
  2. 2. An activity has ES = 10 and LS = 14. Its total float is...

    Float = LS - ES = 14 - 10 = 4 days.
  3. 3. In the forward pass, ES of an activity equals...

    It cannot start until all predecessors finish, so the latest finish matters.
  4. 4. To shorten the project you should...

    Only critical activities determine duration.

Summary

  • CPM computes early and late dates with a forward and a backward pass.
  • Total float = LS - ES; zero float marks the critical path.
  • Focus on critical activities, watch near-critical paths and recompute after changes.
  • CPM is deterministic; use PERT or simulation to handle uncertainty.

Next: PERT and Three-Point Estimates