Direct answer
Compare agile, predictive, and hybrid delivery using uncertainty, feedback, governance, release strategy, and change cost rather than relying on labels.
What to know
- Approach selection is a risk and learning decision.
- Predictive control can coexist with iterative technical work.
- Agile requires disciplined prioritization and feedback.
- Hybrid needs explicit interfaces between planning and delivery systems.
How to apply it
Create a one-page approach decision that records evidence, chosen cadence, governance points, artifact expectations, and conditions that trigger reassessment.
Worked example
A construction package may be predictive while design coordination uses weekly visual planning and short issue-resolution loops.
Common mistakes
- Choosing agile because requirements are late.
- Calling a project hybrid without defining how the parts connect.
- Assuming contracts prevent incremental feedback.
Exam and practice connection
Look for context clues before choosing an action: uncertainty, stakeholder access, approved baselines, and regulatory constraints.