Study guides / CAPM: Certified Associate in Project Management / When to use a predictive approach
When to use a predictive approach
CAPM: Certified Associate in Project Management · quick review
When plan-driven (waterfall) delivery is the right choice, and what it looks like: detailed planning up front, sequential phases and formal change control.
The rules
- Predictive fits when requirements are clear and stable, the technology is known, the cost of late change is high, and regulation or contracts demand detailed plans (construction, manufacturing, many government projects).
- Scope, schedule and cost are planned in detail early and baselined; progress is measured against the baselines.
- Work moves through sequential phases, often with phase gates; the customer typically sees the full result near the end.
- Changes go through formal change control; the aim is to limit change, not welcome it.
- Predictive teams often work from a WBS, a network schedule and earned value reporting.
Common traps
- Predictive doesn't mean no changes; it means changes are controlled formally.
- Uncertain or evolving requirements are the main signal against a predictive approach.
How it's tested
Choosing an approach for a described project, and recognizing predictive practices.
Practise it
The full lesson, worked examples and practice questions are in Tickmark, where every answer choice is explained.
Open the full lesson