PMP Study Guide – Critical Path Method (CPM)

1. What is the Critical Path Method? CORE

Definition & Purpose

The CPM (Critical Path Method) is a schedule network analysis technique used to determine the longest path through a project schedule network — the path that determines the project duration. Activities on this path have zero float, meaning any delay to even one activity will delay the entire project.

CPM answers three vital questions every PM must know:

🕐 What is the earliest the project can finish?
🔍 Which activities cannot be delayed without delaying the project?
⚙️ Where can I compress the schedule (if I must)?

Simple Analogy: Imagine building a house. You can't put on the roof until the walls are up. You can't pour the foundation until the surveying is done. The longest chain of must-happen-in-order tasks is your critical path. Delay any one link — the whole house is late.

History & Context

CPM was developed in the late 1950s by Du Pont Corporation (with Remington Rand) for chemical plant construction. Simultaneously, the U.S. Navy developed PERT for the Polaris missile program. Both are network-based scheduling methods, but CPM uses deterministic durations while PERT uses probabilistic estimates.

📌 PMP Exam Context

CPM is referenced in the PMBOK Guide under the Develop Schedule process (Section 6.5). It is used in predictive (waterfall) project approaches. In agile, similar concepts exist (e.g., critical chain), but CPM specifically applies to predictive environments.

2. Core Concepts

Activities & Network Basics

Term	Meaning	PMP Context
Activity	A discrete, scheduled unit of work	Has duration, resources, predecessors
Predecessor	Activity that must start/finish before another	Defines dependency arrows
Successor	Activity that follows a predecessor	Cannot begin until predecessor condition met
Network Diagram	Visual map of activity sequence and flow	PDM (AON) most common in PMBOK
Path	Sequence of connected activities from start to finish	Multiple paths exist; longest = Critical Path
Critical Path	Longest duration path with zero float	Determines project end date

Forward Pass & Backward Pass

To find the critical path, you perform two mathematical passes through the network:

Forward Pass → Calculates Early Start (ES) and Early Finish (EF) for each activity.
Start at the beginning, move left-to-right through the network.

Backward Pass → Calculates Late Start (LS) and Late Finish (LF) for each activity.
Start at the project end date, move right-to-left through the network.

Float / Slack

Float (also called Slack) is the amount of time an activity can be delayed without delaying the project finish date. Activities on the critical path always have zero float.

Positive Float → Activity has flexibility; NOT on critical path
Zero Float → Activity IS on the critical path; any delay = project delay
Negative Float → Schedule is already behind! Compression needed immediately

💡 Real Scenario — Float in Action

You're managing a bridge rehabilitation project. Activity "Paint structural steel" has 5 days of float. That means you can delay starting it by up to 5 days before it affects the project handover. But "Pour concrete deck" has zero float — it's on the critical path. If concrete pours start 1 day late due to weather, the whole project moves 1 day.

3. Key Formulas MEMORIZE THESE

Forward Pass

ES (first activity) = 0 (or 1, per convention)
EF = ES + Duration – 1 (activity-on-node / day-based)
ES (next activity) = EF (predecessor) + 1

OR — Duration-Only Method (most common in PMP)

EF = ES + Duration
ES (successor) = EF (predecessor)

Backward Pass

LF (last activity) = EF (last activity) ← project end date
LS = LF – Duration
LF (predecessor) = LS (successor) – 1 (day-based)

OR — Duration-Only Method

LS = LF – Duration
LF (predecessor) = LS (successor)

Float / Slack

Total Float = LS – ES = LF – EF
Free Float = ES (successor) – EF (current activity)
Critical Path Float = 0

Schedule Compression — Crashing

Crash Cost per Day = (Crash Cost – Normal Cost) / (Normal Duration – Crash Duration)
Always crash the cheapest activity on the critical path first!

⚡ Exam Formula Tip

Most PMP exam questions use the duration-only method (ES + Duration = EF). Don't subtract 1.
If the project starts on Day 0: first activity ES = 0, EF = Duration.
Float = LS – ES OR LF – EF (both give same result — use as a check!)

4. Network Diagrams

AON vs AOA

Type	Full Name	Nodes Represent	Arrows Represent	PMBOK Preference
AON	Activity on Node	Activities (boxes)	Dependencies	✅ YES — PDM
AOA	Activity on Arrow	Events (nodes)	Activities	⚠️ Old method; rarely used

PMBOK uses the Precedence Diagramming Method (PDM), which is AON. Each activity is a box (node) with ES, EF, LS, LF, Duration, and Float displayed.

Activity Node Box Format

┌──────────────────────────────┐
│  ES = 3       |   EF = 7     │
│──────── Activity Name ───────│
│  LS = 5       |   LF = 9     │
│──────── Duration = 4 ────────│
│           Float = 2          │
└──────────────────────────────┘

▲ Interactive CPM network diagram — Critical Path highlighted in red

Dependency Types (Logical Relationships)

Relationship	Abbreviation	Meaning	Most Common?
Finish-to-Start	FS	B can't START until A FINISHES	✅ Most common
Start-to-Start	SS	B can't START until A STARTS	⚡ Overlap work
Finish-to-Finish	FF	B can't FINISH until A FINISHES	⚡ Parallel close
Start-to-Finish	SF	B can't FINISH until A STARTS	❌ Rarely used

5. How to Find the Critical Path

Step-by-Step Method

Step 1: List all activities with durations.
Step 2: Identify dependencies and build the network diagram.
Step 3: Perform Forward Pass → Calculate ES and EF for all activities.
Step 4: Perform Backward Pass → Calculate LS and LF for all activities.
Step 5: Calculate Float = LS – ES for each activity.
Step 6: Activities with Float = 0 are on the Critical Path.
Step 7: The Critical Path = the longest path through the network.

Worked Calculation Example

Project: Software Module Release — 5 Activities

Activity	Predecessor	Duration (days)
A – Requirements	None (Start)	4
B – UI Design	A	5
C – Backend Dev	A	8
D – Integration	B, C	3
E – Testing	D	4

Paths through the Network:

Path 1: A → B → D → E = 4+5+3+4 = 16 days
Path 2: A → C → D → E = 4+8+3+4 = 19 days ← CRITICAL PATH

Forward/Backward Pass Results:

Activity	ES	EF	LS	LF	Float	Critical?
A	0	4	0	4	0	✅ YES
B	4	9	7	12	3	No (3 days float)
C	4	12	4	12	0	✅ YES
D	12	15	12	15	0	✅ YES
E	15	19	15	19	0	✅ YES

🔴 Critical Path: A → C → D → E = 19 days. Activity B has 3 days of float and is NOT critical.

Multiple Critical Paths

A project can have more than one critical path. This happens when two or more paths have the same (longest) duration. This is actually more risky — any delay on either path delays the project, and you have less scheduling flexibility.

💡 Scenario — Two Critical Paths

On a highway project, both the paving subcontract chain (Path A: 22 weeks) and the utility relocation chain (Path B: 22 weeks) are the longest. Both are critical. The PM must manage resources carefully on both paths simultaneously — a single delay to either one pushes the project completion date.

6. Types of Float

Float Type	Formula	What it Tells You
Total Float	LS – ES or LF – EF	How long activity can delay without delaying PROJECT end
Free Float	ES(succ) – EF(current)	How long activity can delay without delaying SUCCESSOR
Project Float	Customer deadline – Calculated end date	Schedule buffer before customer deadline is missed

Key Point: Free Float ≤ Total Float (always). You can never have more free float than total float for a given activity.

💡 Scenario — Free Float vs Total Float

Activity X: EF=10, Successor Y has ES=14. Free Float = 14–10 = 4 days. But Total Float for X = LS–ES = 7. Meaning: you can delay X by 4 days without affecting Y at all; delay by up to 7 days total without delaying the project end — but days 5–7 of delay would push Y's start back and consume Y's float.

7. CPM vs PERT — Key Comparison

Feature	CPM	PERT
Duration Estimate	Single (deterministic)	Three-point (optimistic, most likely, pessimistic)
Uncertainty	Low — well-known work	High — R&D, first-time projects
Developed by	Du Pont (1957)	U.S. Navy (1958)
Focus	Time & Cost	Time & Uncertainty
Output	Critical Path, Float	Probability of meeting deadline
PMP Application	Develop Schedule (6.5)	Estimate Activity Durations (6.4)

PERT Three-Point Formula (for reference)

Expected Duration = (O + 4M + P) / 6
Standard Deviation = (P – O) / 6
O = Optimistic | M = Most Likely | P = Pessimistic

📌 PMP Exam Distinction

If the question mentions "single duration estimate" → CPM. If it mentions "three-point estimate," "uncertainty," or "probabilistic" → PERT or Monte Carlo. If asked which technique finds the critical path → always answer CPM (or PDM/Network Analysis).

8. Schedule Compression Techniques

When the calculated project end date is later than the required end date, you must compress the schedule. You should always compress activities on the Critical Path — compressing non-critical activities wastes money without helping the deadline.

Crashing

Crashing = Adding resources (cost) to reduce duration. Works best when the cost of compression is less than the penalty for delay.

Always crash the cheapest activity on the critical path first
Watch out: crashing one activity might make a non-critical path become critical
Crashing has limits — you can only crash up to the crash limit

🔧 Crashing Example — Bridge Construction

Critical Path: Survey (2d) → Excavation (10d) → Concrete pour (8d) → Cure (5d) = 25 days. Client needs it in 22 days. Options:

Crash Excavation by 3 days: Add $6,000 ($2,000/day)
Crash Concrete pour by 3 days: Add $9,000 ($3,000/day)

Decision: Crash Excavation first (cheaper per day). 3 days × $2,000 = $6,000 total crash cost. Project now = 22 days ✅

Fast Tracking

Fast Tracking = Performing activities in parallel that were originally planned sequentially. No extra cost, but high risk — increases rework potential if earlier activities change.

⚠️ Risk Warning: Fast tracking increases schedule risk. If you overlap design and construction and the design changes, the construction work done must be redone. Only use fast tracking when the risk is acceptable.

	Crashing	Fast Tracking
Method	Add resources / cost	Overlap sequential activities
Cost Impact	Increases cost	No direct cost increase
Risk Impact	Usually low	Increases rework risk
Best for	Cost-flexible projects	Cost-constrained projects

📌 PMP Exam: Crashing vs Fast Tracking

If a question says "no budget available" → Fast Tracking first
If a question says "risk must be minimized" → Crashing
PMBOK says: use fast tracking first, then crashing (to avoid cost overruns)

9. Scenarios & Real-World Examples

Scenario 1 — Road Construction Project

Activities: A(Mobilize, 3d) → B(Clearing, 5d) → C(Grading, 8d) → D(Paving, 7d). Also: A → E(Utility Install, 12d) → D.

Path 1: A–B–C–D = 3+5+8+7 = 23 days
Path 2: A–E–D = 3+12+7 = 22 days

Critical Path = A–B–C–D (23 days). Activity E has 1 day of float. PM should focus resources on B, C, D.

Scenario 2 — Software Product Launch

Sponsor asks: "Can we launch 2 weeks earlier?" Critical path is 16 weeks. What do you do?

First: Identify critical path activities that can be overlapped (fast track)
Example: Start QA testing while development finishes last module (risky but saves 1 week)
Then: Crash the remaining 1 week by adding testers (costs $5,000)
Report: 2-week compression achievable for $5,000 + increased rework risk

Scenario 3 — Negative Float Emergency

Project baseline shows end date = Nov 30. After monthly update, backward pass shows the critical path has -5 days float. What happened?

A critical path activity slipped by 5 days
The project is already 5 days behind schedule
PM must immediately crash and/or fast-track to recover
PMP exam would ask: "What should the PM do FIRST?" → Analyze variance and develop recovery plan

Scenario 4 — Resource Leveling Changes CP

After applying Resource Leveling to your schedule, some activities are delayed to resolve resource conflicts. This delay may change the critical path! The PM must re-run CPM analysis after resource leveling.

10. PMP Exam Tips READ CAREFULLY

🔥 Top 15 CPM Exam Tips

The critical path is ALWAYS the LONGEST path, not the most important or most risky.
Activities on the CP have zero total float. If a question gives you float ≠ 0, that activity is NOT on the CP.
When multiple paths exist with the same duration, the project has multiple critical paths — higher risk!
Adding resources to non-critical activities does NOT shorten the project.
Float can be NEGATIVE — means the schedule is already overrun.
Forward pass → use MAX when multiple predecessors converge. Backward pass → use MIN.
The project duration = length of the critical path (not the sum of all activities).
CPM is used in the Develop Schedule (6.5) process.
Resource leveling can lengthen the critical path.
Fast tracking = overlap activities; Crashing = add resources.
When schedule is behind, always compress the critical path first.
The Schedule Network Analysis includes CPM, resource leveling, and what-if scenario analysis.
Mandatory dependencies ("hard logic") cannot be changed. Discretionary dependencies ("soft logic") can be adjusted (fast tracking).
CPM uses deterministic durations. PERT uses probabilistic (3-point).
If asked what determines the project end date → Critical Path length.

11. Cheat Sheet

⚡ CPM Formula Quick Reference

Item	Formula
Early Finish	EF = ES + Duration
Late Start	LS = LF – Duration
Total Float	LS – ES (or LF – EF)
Free Float	ES(next) – EF(current)
Crash Cost/Day	(CC – NC) ÷ (ND – CD)
Critical Path	Float = 0 AND longest path
PERT Expected	(O + 4M + P) ÷ 6

⚡ Key Decision Rules

Schedule behind + no budget → Fast Track
Schedule behind + budget available → Crash
Float = 0 → Critical Path
Float negative → Schedule in trouble (overrun)
Multiple paths same length → Multiple Critical Paths (more risky)
Compress which path? → Always the Critical Path
Crash which activity? → Cheapest one on CP first
Resource leveling → May extend the CP

⚡ CPM Process Placement (PMBOK 6)

Process Group: Planning
Knowledge Area: Project Schedule Management
Process: 6.5 Develop Schedule
Inputs: Activity list, durations, sequence, resources, project calendar
Tools & Techniques: CPM, Schedule Network Analysis, Resource Leveling, What-If Scenario Analysis
Outputs: Project Schedule, Schedule Baseline, Schedule Data, Project Calendars

12. Clickable Keywords Reference

Click any keyword to review its definition quickly:

CPM Critical Path Float Total Float Free Float Early Start (ES) Early Finish (EF) Late Start (LS) Late Finish (LF) Crashing Fast Tracking PERT AON / PDM AOA Finish-to-Start (FS) Start-to-Start (SS) Finish-to-Finish (FF) Start-to-Finish (SF) Predecessor Successor Network Diagram Resource Leveling Project Duration Slack Lag Lead Near-Critical Path Path Convergence Critical Chain (CCM) What-If Analysis Monte Carlo Simulation Mandatory Dependency Discretionary Dependency External Dependency Internal Dependency Activity Path Project Float

13. Practice Quiz TEST YOURSELF

Question 1 of 8

A project has Path A (15 days), Path B (22 days), and Path C (18 days). What is the project duration?

15 days 55 days (sum of all) 22 days 18 days

Question 2 of 8

Activity X has ES=5, EF=10, LS=8, LF=13. What is the total float? Is it on the critical path?

Float=3; NOT on Critical Path Float=0; IS on Critical Path Float=5; NOT on Critical Path Float=3; IS on Critical Path

Question 3 of 8

The project sponsor demands the project be delivered 3 weeks earlier, and there is no additional budget. What is the BEST schedule compression technique?

Crashing — add overtime workers Fast Tracking — overlap sequential activities Remove scope to reduce duration Increase resource pool across all activities

Question 4 of 8

After resource leveling is applied to the project schedule, what is the most likely result?

The critical path gets shorter All float is eliminated The critical path may lengthen Non-critical activities gain more resources

Question 5 of 8

Which statement about the Critical Path is TRUE?

It is always the path with the most activities It is the path with the highest total cost It is the longest duration path with zero float It must go through the most complex activities

Question 6 of 8

Activity D has EF=12. Its successor Activity E has ES=15. What is the Free Float of Activity D?

2 days 3 days 12 days 27 days

Question 7 of 8

What is the MAIN difference between CPM and PERT?

CPM uses probabilistic durations; PERT uses deterministic CPM uses deterministic durations; PERT uses three-point probabilistic estimates CPM is only for construction; PERT is for IT projects PERT finds the critical path; CPM calculates budget

Question 8 of 8

A project's backward pass shows the critical path has –4 days of float. What does this mean?

The project has 4 extra buffer days The project is 4 days AHEAD of schedule The project is already 4 days BEHIND schedule Four activities need to be added to the path

Question 9 of 15

Activity A (4d) → B (6d) with FS + 2 day lag. What is the total duration of this path?

10 days 12 days 8 days 14 days

Question 10 of 15

Which type of dependency CAN be modified during fast tracking?

Mandatory (hard logic) External dependencies Discretionary (soft logic) All dependencies equally

Question 11 of 15

In Critical Chain Method (CCM), what replaces individual activity buffers?

Float on every activity Project Buffer and Feeding Buffers placed at strategic points Contingency reserve added to each activity Resource calendars with built-in slack

Question 12 of 15

Your schedule shows SPI = 0.75 on the critical path. What does this mean and what should you do?

Ahead of schedule; monitor and continue Behind schedule (only 75% of planned work done); compress the critical path Over budget; reduce scope 25% complete; nothing to worry about yet

Question 13 of 15

A near-critical path has 2 days of float. The project is 3 weeks long. What is the PRIMARY risk?

No risk — it has positive float It could become a second critical path with any small delay, increasing schedule risk Resources on this path should be moved to the critical path immediately Float will grow as the project progresses

Question 14 of 15

A project has an imposed finish date constraint that is EARLIER than the calculated critical path end. What is the result?

The project automatically adjusts to meet the constraint The project schedule shows negative float All activities gain extra float A new critical path is automatically created

Question 15 of 15

During execution, a critical path activity is delayed by 5 days. After crashing another CP activity by 3 days, what is the net schedule impact?

+5 days delay (crashing doesn't help) –3 days ahead of schedule +2 days delay to project completion No change — they cancel out

15. Leads & Lags — Deep Dive NEW

Leads and Lags modify the timing relationship between activities. They are applied to dependency relationships and directly impact path durations — and therefore the critical path.

What is Lead?

A Lead is an acceleration — it allows a successor activity to start before its predecessor finishes. Lead is essentially negative lag. It is commonly used in fast tracking.

Example: Activity A = Write Report (10 days). Activity B = Review Report (5 days). With FS – 3 day lead: B can start 3 days before A finishes. Path duration = 10 + (–3) + 5 = 12 days instead of 15.

🔧 Construction Lead Example

Activity A: "Install electrical conduit" (14 days). Activity B: "Pull wire through conduit" (8 days). Relationship: FS – 4 days lead. Wire-pulling can begin on the already-installed sections 4 days before conduit installation is fully done. Path = 14 – 4 + 8 = 18 days instead of 22. Saves 4 days on the critical path!

What is Lag?

A Lag is a mandatory wait — a delay intentionally inserted between the predecessor finishing and the successor starting. Lag always adds time to a path.

Example: Activity A = Pour Concrete (3 days). Activity B = Strip Formwork. Relationship: FS + 5 day lag (concrete cure time). B cannot start until 5 days after A finishes. Path = 3 + 5 + duration of B.

Lag Type	Example	Effect on Path
FS + Lag	Paint walls; wait 2 days to dry; then hang art	Adds lag days to path
SS + Lag	B can start 3 days after A starts	Adds constraint; may affect CP
FF + Lag	B must finish 2 days after A finishes	May lengthen successor path
FS – Lead	B starts 3 days before A finishes	Shortens path (used in fast tracking)

Impact of Leads & Lags on the Critical Path

Lag on a CP activity lengthens the critical path → increases project duration
Lead on a CP activity shortens the critical path → reduces project duration
Lag on a non-critical activity may consume its float and make it critical
Always re-run forward/backward pass after adding leads or lags

📌 PMP Exam — Leads & Lags

Lag = wait time = adds to path duration
Lead = overlap = subtracts from path duration
Excessive leads create rework risk (like fast tracking)
Lags often represent physical constraints (curing, drying, regulatory waiting periods)

16. Near-Critical Paths & Schedule Risk NEW

Definition & Risk

A Near-Critical Path is a network path whose total float is very small (close to zero) — typically defined as paths with float ≤ 10–20% of project duration. These paths can easily become critical if any activity on them is delayed.

⚠️ Why Near-Critical Paths Matter: The PMP exam frequently tests whether PMs should monitor ONLY the critical path. The correct answer is NO — near-critical paths must also be actively monitored because a small delay converts them into a second (or replacement) critical path, potentially overriding your original CP focus.

💡 Near-Critical Path Scenario

Project has two paths: CP (A–C–D–E) = 20 days. Near-critical (A–B–D–E) = 18 days (float = 2). During execution, Activity B is delayed 3 days due to a vendor issue. Now Path A–B–D–E = 21 days → it becomes the NEW critical path! The original critical path is no longer critical. The PM must immediately shift focus to the formerly near-critical path.

Path Convergence Risk

Path Convergence occurs when multiple paths merge into a single activity (a merge point). This dramatically increases schedule risk at that activity — if ANY of the converging paths is delayed, the merge activity is delayed.

Example — Path Convergence: Activity D is the Integration milestone. Three paths converge at D: Path 1 (float=0), Path 2 (float=1), Path 3 (float=3). Even though only Path 1 is technically critical, ANY delay on Path 2 or 3 by more than 1 or 3 days respectively delays D. The PM should treat D as a high-risk milestone requiring extra monitoring of all three feeding paths.

Situation	Risk Level	PM Action
Single CP, no near-critical paths	Low–Medium	Focus on CP activities
Near-critical path ≤ 2 days float	High	Monitor both paths; consider pre-emptive crashing
Multiple paths converge at one activity	Very High	Identify merge point; buffer or crash feeding paths
Multiple critical paths exist	Highest	Manage all CPs simultaneously; risk register update

17. Critical Chain Method (CCM) vs CPM NEW

Critical Chain Method (CCM) was developed by Eliyahu Goldratt (Theory of Constraints) as an improvement over CPM. It addresses a key CPM weakness: individual activity padding hides true schedule risk.

The Core Problem CCM Solves

In CPM, people add hidden buffers to their individual activity estimates (Parkinson's Law — work expands to fill time). These buffers are then wasted because of the Student Syndrome (starting late because "I have plenty of time"). CCM removes this problem.

Feature	CPM	CCM
Focus	Activity sequence (logical dependencies)	Activity sequence + resource constraints
Duration estimates	Includes safety/padding per activity	Uses aggressive (50%) estimates; removes padding
Buffer management	Float on individual activities	Project Buffer (end) + Feeding Buffers (merge points)
Critical path	Longest logical path (CPM)	Longest resource-constrained path (Critical Chain)
Safety	Distributed across activities	Consolidated at buffer points
PMBOK reference	6.5 Develop Schedule	6.5 Develop Schedule (alternative T&T)

🔧 CCM Example

CPM estimate for Activity X = 10 days (includes 4 days of individual buffer). CCM removes the buffer: estimates X at 6 days. All removed buffers from all activities are consolidated into a Project Buffer at the end (e.g., 14 days). If a feeding path merges into the critical chain, a Feeding Buffer protects the critical chain from late non-critical deliveries. Result: same safety, more visible and managed buffer.

📌 PMP Exam — CCM Key Points

CCM = CPM + resource constraints + buffer management
Project Buffer protects the project end date
Feeding Buffers protect merge points
Resource Buffer = reminder alerts that a resource will soon be needed on the critical chain
If exam asks "which considers resources when determining the critical path?" → CCM

18. CPM + Earned Value Management (EVM) NEW

CPM tells you the schedule sequence; EVM tells you schedule performance. Together they give the PM a complete picture of where the project stands and whether the critical path is at risk.

Key EVM Metrics on the Critical Path

EVM Formulas (Schedule-Focused)

SV (Schedule Variance) = EV – PV    [Negative = Behind Schedule]
SPI (Schedule Performance Index) = EV / PV    [<1.0 = Behind, >1.0 = Ahead]
EAC (Estimate at Completion) = BAC / CPI    [Cost-focused]
ETC (Estimate to Complete) = EAC – AC

SPI Value	Meaning	CP Implication
SPI = 1.0	On schedule	CP is on track
SPI > 1.0 (e.g. 1.15)	Ahead of schedule	CP activities completing early — may allow float
0.8 ≤ SPI < 1.0	Slightly behind	CP activities slipping — monitor closely
SPI < 0.8	Significantly behind	Immediate compression action required on CP

Using EVM for CP Recovery Decisions

💡 EVM + CPM Decision Scenario

Week 6 of a 20-week project. Critical path activities show: PV = $80,000, EV = $64,000, AC = $70,000.

SV = EV – PV = $64K – $80K = –$16,000 (behind schedule)
SPI = EV / PV = 64/80 = 0.80 (doing only 80¢ of work per $1 planned)
CPI = EV / AC = 64/70 = 0.91 (also over budget)

PM Decision: SPI = 0.80 on critical path → project will be ~4 weeks late if nothing changes (20 weeks × 0.20 slip). Crashing is needed but CPI shows cost efficiency already low. Fast tracking is the better first step to recover schedule without additional spending.

📌 PMP Exam — EVM + CPM Integration

SV and SPI measure schedule performance but don't identify WHICH activities are late — that's what the CPM network shows
Use CPM to identify WHERE to act; use EVM to measure HOW MUCH recovery is needed
SPI approaching end of project loses reliability; CPM remains the authoritative schedule tool
Negative SV + critical path slip = high-urgency situation requiring immediate CP compression

19. Dependency & Constraint Types NEW

Hard Logic vs Soft Logic

Type	Also Called	Definition	Can be Changed?	Example
Mandatory	Hard Logic	Physically or contractually required	❌ No	Can't test software before it's coded
Discretionary	Soft Logic / Preferred Logic	Best practice choice; not physically required	✅ Yes (for fast tracking)	PM chooses to inspect before next phase
External	—	Depends on something outside the project	⚠️ Limited	Regulatory approval before construction
Internal	—	Depends on something within the project	✅ Often yes	Team A finishes design before Team B builds

Date Constraints on Activities

Schedule software allows PMs to impose date constraints on activities. These override the calculated ES/EF and LS/LF, and directly affect float and the critical path:

Constraint Type	Meaning	Impact
As Soon As Possible (ASAP)	Default — start at earliest calculated date	No impact (default behavior)
As Late As Possible (ALAP)	Delay start as long as possible without delaying project	Uses up float intentionally
Start No Earlier Than (SNET)	Activity cannot start before a given date	May create lag; can affect CP
Finish No Later Than (FNLT)	Activity must finish by a given date	Can create negative float if tight
Must Start On (MSO)	Fixed start date	Eliminates float; high risk
Must Finish On (MFO)	Fixed finish date	May cause negative float

📌 PMP Exam — Constraints

ASAP is the default in CPM (preferred — gives maximum scheduling flexibility)
Imposed date constraints that conflict with the calculated schedule create negative float
Mandatory dependencies are never changed for fast tracking — only discretionary ones can be overlapped
External dependencies (regulatory, permits, vendor deliveries) are often the most schedule-critical and uncontrollable

💡 Constraint Scenario — Highway Project

A lane closure permit from IDOT can only be used starting March 1 (regulatory constraint = external dependency). The CPM shows the paving activity could technically start February 10. The SNET constraint of March 1 creates 18 days of lag, potentially consuming all float on that path and making it critical. The PM must account for this in the baseline schedule and may need to crash preceding activities to avoid cascading delay.

20. What-If Scenario Analysis & Monte Carlo NEW

What-If Scenario Analysis

What-If Scenario Analysis evaluates how variations or disruptions affect the project schedule. The PM creates alternative scenarios by changing activity durations, adding delays, or removing dependencies — then observes the impact on the critical path.

Common What-If Questions:

"What if the concrete delivery is delayed 5 days?" → Does it impact the CP?
"What if we lose 2 inspectors for 1 week?" → Which paths are affected?
"What if we remove Activity X's dependency on Y?" → Does it shorten the CP?

Monte Carlo Simulation

Monte Carlo Simulation runs thousands of schedule simulations using probability distributions for activity durations. Instead of one deterministic answer (like CPM), it produces a probability distribution of project end dates.

Feature	CPM	Monte Carlo
Duration input	Single estimate	Probability distribution (min, most likely, max)
Output	One project end date	Probability curve (e.g., "80% chance done by Day X")
Critical Path	Fixed single path	Criticality Index — % of simulations an activity is on CP
Use case	Baseline planning	Risk analysis, contingency reserve calculation
PMBOK process	6.5 Develop Schedule	11.4 Perform Quantitative Risk Analysis

Criticality Index: In Monte Carlo, an activity might be on the critical path in only 60% of simulations. This means it's not always critical — but it's at significant risk. Activities with high criticality index AND high duration variability need the most attention.

📌 PMP Exam — Monte Carlo vs CPM

Monte Carlo = quantitative risk analysis; used to determine schedule contingency reserve
CPM = deterministic; Monte Carlo = probabilistic
If exam asks about "probability of completing by a date" → Monte Carlo
If exam asks about "which activities determine project duration" → CPM

21. CPM Across Industries NEW

CPM principles are universal but manifest differently across industries. Understanding these industry-specific applications helps on scenario-based PMP exam questions.

Industry	Typical CP Activities	Common Lags	Unique Challenges
🏗️ Heavy Construction (Bridge, Highway)	Foundation, structural steel, deck concrete, surfacing	Concrete cure (7–28 days), soil settlement	Weather delays, permit windows, utility conflicts, lane closure restrictions
💻 Software/IT	Architecture design, core development, integration, UAT	Environment setup, regulatory review	Scope creep, technical debt, sprint-to-release alignment
💊 Pharmaceutical/R&D	Trial phases, regulatory submissions, manufacturing scale-up	FDA review periods (months to years)	Regulatory uncertainty; trials can invalidate entire paths
🏭 Manufacturing	Tooling, first article, production line setup, QA	Material lead times, vendor certification	Supply chain disruptions; resource-constrained multi-project environments
🛥️ Shipbuilding/Aerospace	Hull/airframe, systems integration, testing campaigns	Classification society inspections	Extremely long lead items; safety-critical sequences

🏗️ Real Engineering Example — Bridge Rehab (IDOT/Tollway)

Critical path for a bascule bridge rehabilitation: Mobilize (3d) → Deck removal (10d) → Structural steel inspection (5d) → Steel repairs (14d) → Deck formwork (8d) → Concrete pour (3d) → Cure (14d) → Waterproofing (4d) → Overlay (5d) → Punch list (3d) = 69 days. Key lags: concrete cure (mandatory 14-day lag), steel inspection hold point (can't pour until passed). Near-critical: electrical/mechanical bascule system work path (65 days, only 4 days float). PM must closely track both paths and pre-order long-lead steel replacement items during mobilization.

22. Common PM Mistakes with CPM NEW

The PMP exam tests not just theory but practical judgment. Knowing what PMs do wrong — and the correct approach — is essential for scenario questions.

#	Common Mistake	Why It's Wrong	Correct Approach
1	Only monitoring the critical path	Near-critical paths can overtake the CP with a small delay	Monitor all paths; flag near-critical paths in risk register
2	Crashing non-critical activities first	Does nothing to reduce project duration	Always crash the cheapest CP activity first
3	Ignoring resource constraints in CPM	Paper schedule may be impossible to execute	Apply resource leveling; use CCM if resource-critical
4	Not updating the schedule after changes	Baseline becomes stale; float calculations wrong	Update schedule with every approved change; re-run CPM
5	Treating float as free time for the PM	Float belongs to the project/path, not one activity	Float consumed by one activity removes it from all activities on that path
6	Fast tracking mandatory dependencies	Physically impossible or contractually prohibited	Only fast track discretionary (soft logic) dependencies
7	Forgetting lags in forward/backward pass	Incorrect ES/EF/LS/LF; wrong critical path identified	Always include lags in duration calculations
8	Assuming one critical path is permanent	CP changes with delays, resource leveling, compression	Re-run CPM analysis regularly throughout execution
9	Compressing only to meet a date without cost/risk analysis	May cause cost overrun or quality issues	Analyze crash cost vs. penalty cost; evaluate fast track risk
10	Not communicating CP to the team	Team members don't know which activities cannot be late	Share critical path with team; highlight CP activities in schedule

🔥 Final Exam Reminders

Float is a path resource — one activity using float affects the entire path's float
The PM does NOT "own" float — it belongs to the project schedule
Resource leveling always comes after CPM analysis; it modifies (usually extends) the CP
When a scenario gives you multiple options to recover schedule → fast track first (no cost), then crash if needed
A project can finish early but NEVER faster than the critical path allows

14. My Study Notes

Your notes auto-save to this browser. Use this space for your personal CPM study notes.

✅ Saved!

🏗️ Critical Path Method (CPM)

Definition & Purpose

History & Context

Activities & Network Basics

Forward Pass & Backward Pass

Float / Slack

AON vs AOA

Activity Node Box Format

Dependency Types (Logical Relationships)

Step-by-Step Method

Worked Calculation Example

Paths through the Network:

Forward/Backward Pass Results:

Multiple Critical Paths

Crashing

Fast Tracking

What is Lead?

What is Lag?

Impact of Leads & Lags on the Critical Path

Definition & Risk

Path Convergence Risk

The Core Problem CCM Solves

Key EVM Metrics on the Critical Path

Using EVM for CP Recovery Decisions

Hard Logic vs Soft Logic

Date Constraints on Activities

What-If Scenario Analysis

Monte Carlo Simulation