Hybrid Approach
A Hybrid Approach combines elements of predictive (waterfall) and adaptive (agile) methods within a single project, tailoring practices to fit the project's specific needs and constraints.
Explanation
Not every project is fully agile or fully predictive. Hybrid approaches allow teams to use the best practices from both worlds based on project characteristics. For example, a project might use predictive planning for hardware components with long lead times while using agile sprints for software development. Or a team might use waterfall for regulatory documentation while iteratively developing the product.
PMI acknowledges that most real-world projects use some form of hybrid approach. The PMBOK 7th Edition and the PMI Agile Practice Guide both emphasize tailoring the development approach to the project. The key is to match the approach to the level of uncertainty, complexity, and stakeholder needs.
Common hybrid patterns include agile development with predictive planning (using agile within sprints but maintaining a waterfall-like project plan), waterfall with agile reviews (using traditional phases but adding iterative feedback loops), and parallel approaches (different project components using different methodologies simultaneously).
Key Points
- •Combines predictive and adaptive methods within one project
- •Tailored to project needs, uncertainty, and constraints
- •PMI recognizes hybrid as the reality for most projects
- •Common in regulated industries and projects with mixed predictability
Exam Tip
The PMP exam heavily tests hybrid approaches. When a question describes a project mixing agile and predictive elements, look for answers about tailoring the approach to the situation.
Frequently Asked Questions
Related Topics
Agile Manifesto
The Agile Manifesto is a foundational document published in 2001 that establishes four core values and twelve principles for agile software development, emphasizing individuals, working software, customer collaboration, and responding to change.
Scrum Framework
Scrum is a lightweight agile framework that uses fixed-length iterations called sprints, defined roles, events, and artifacts to help teams deliver complex products incrementally and iteratively.
SAFe (Scaled Agile Framework)
The Scaled Agile Framework (SAFe) is a set of organization and workflow patterns intended to guide enterprises in scaling lean and agile practices across multiple teams, programs, and portfolios.
Kanban
Kanban is a lean method for managing and improving work across systems that emphasizes visualizing the workflow, limiting work in progress, managing flow, and making process policies explicit.
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.