Orient and prepare
Recall how ties and dependencies make a project network more complex.
Practise this lesson
Three printable worksheets that build from foundations to mastery, or build your own from any module’s questions.
Think First
A project has two parallel paths from start to finish: Path 1 takes 10 days and Path 2 also takes 10 days. Both paths have zero float.
Before reading on, is this project easier or harder to manage than one with a single critical path? What happens if you try to crash one path by 2 days?
Learning Intentions
- Recognise and handle networks with multiple critical paths
- Understand dummy activities: what they are, when to use them, and how to draw them
- Complete forward and backward scans on networks with 7 or more activities
- Apply crashing logic when multiple critical paths exist
- Interpret complex CPA results in practical scheduling contexts
Key Terms
- Multiple critical paths
- When two or more distinct paths through the network have equal length (equal to the project duration), all with zero float.
- Dummy activity
- An activity with duration zero, shown as a dashed arrow, used to represent a precedence dependency between activities that share some (but not all) predecessors.
- Shared predecessor
- When activity C depends on both A and B, but D depends only on A. A dummy from the "after A" node to the "after A,B" node handles this correctly.
- Crashing (multiple paths)
- To reduce project duration when multiple critical paths exist, you must crash at least one activity on EVERY critical path simultaneously.
- 7+ activity networks
- Larger networks requiring systematic node labelling, careful scan progression, and complete float tables.