hybrid approach
A blended way of working that mixes adaptive (agile) and predictive (plan-driven) practices, chosen to handle projects where requirements are uncertain or risky.
Key Points
- Combines agile/adaptive and predictive methods within one project or product lifecycle.
- Use predictive for stable, well-defined, or regulated work; use adaptive for areas with evolving or unclear needs.
- Integrates governance from both styles, such as stage gates with sprints, backlogs, and roadmaps.
- Success depends on clear roles, interfaces, and metrics so teams do not work at cross-purposes.
Example
A company builds a connected medical device. Hardware and compliance documentation follow a predictive plan with stage gates, while the mobile app and analytics are delivered in two-week sprints to respond to user feedback. The overall release plan ties both tracks together with integrated milestones.
PMP Example Question
A project has highly regulated components with fixed specifications, but customer-facing features are likely to change as feedback is gathered. Which approach should the project manager choose?
- Pure predictive approach
- Pure adaptive approach
- Hybrid approach
- Rolling wave planning only
Correct Answer: C — Hybrid approach
Explanation: A hybrid approach lets the team use predictive methods for regulated, stable work while applying adaptive practices to evolving features.
