Hybrid Approach
An approach that blends practices from agile and non-agile methods, using two or more elements, while the final delivery follows a non-agile (predictive) model.
Key Points
- Combines agile techniques (e.g., sprints, Kanban) with predictive planning and controls.
- Governance and final release are non-agile, often using phase gates and fixed baselines.
- Useful when compliance, contracts, or hardware constraints demand a predictive final handoff.
- Provides adaptability within components while maintaining a traditional overall delivery approach.
Example
A medical device project plans scope, budget, and regulatory milestones using a predictive, stage-gate process. The embedded software is developed in Scrum sprints for rapid feedback and testing, but the product is released only after full verification and validation at the end.
PMP Example Question
A project team builds the UI in two-week sprints but follows a fixed scope baseline, phase-gate approvals, and one final release after full system testing. Which delivery approach best describes this project?
- Agile approach
- Predictive (waterfall) approach
- Hybrid approach
- Iterative approach
Correct Answer: C — Hybrid approach
Explanation: Agile techniques are used within the work, but the overall governance and final delivery are predictive, which is characteristic of a hybrid approach with a non-agile end result.