Hybrid Considerations Development

PMBOK v8 Definition

Hybrid approaches combine predictive and adaptive development approaches to create a tailored life cycle that best fits the project's unique characteristics. The selection of a hybrid approach is determined by evaluating variables related to deliverables, project attributes, and organizational factors, recognizing that most real-world projects fall somewhere on the spectrum between purely predictive and purely adaptive approaches.

Why It Matters for the Exam

Hybrid considerations appear frequently in PMI exam questions testing your ability to select the appropriate development approach based on project variables. Expect situational questions where you must identify when a hybrid approach is optimal—typically when different parts of the project have different levels of requirements certainty, scope stability, or innovation needs.

Key Points to Remember (for the exam)

• Spectrum of Approaches: Development approaches exist on a continuum from predictive → hybrid → adaptive, not as binary choices
• Deliverable Variables: Three key deliverable factors drive approach selection: degree of innovation, requirements certainty, and degree of scope stability
• Innovation Rule: When new or complex technological and/or business model innovation is needed → adaptive approach may be optimal
• Requirements Rule: When requirements are well known and straightforward to define → predictive approach may be optimal
• Scope Stability Rule: The less stable the scope, the more optimal it will be to apply an adaptive approach
• Hybrid Patterns: Two common hybrid patterns exist: (1) adaptive development followed by predictive rollout, and (2) adaptive and predictive approaches used simultaneously
• No One-Size-Fits-All: The development approach selection must consider deliverables, project characteristics, and organizational context together

Typical PMI Exam Example

A software company is developing a new mobile application with stable backend requirements but uncertain user interface features. The backend can be planned predictively, while the UI requires iterative feedback. What development approach should the project manager recommend? → A hybrid approach, using predictive methods for the backend and adaptive methods for the UI simultaneously.

PMI Exam Traps

• Trap: Assuming hybrid means "half predictive, half adaptive" → Reality: Hybrid approaches can use any combination, including sequential phases (adaptive then predictive) or simultaneous parallel streams
• Trap: Selecting predictive approach because requirements are "mostly known" → Reality: If scope is unstable or innovation is needed, adaptive or hybrid may still be optimal
• Trap: Thinking adaptive approaches have no planning → Reality: Adaptive approaches have continuous planning and re-planning throughout iterations
• Trap: Confusing "degree of innovation" with "project complexity" → Reality: Innovation specifically refers to new technological or business model innovation, not general complexity

Important PMI Connections

Quick Review Questions

1. When new or complex technological innovation is needed, which development approach may be optimal?

2. What are the three deliverable variables that influence development approach selection?

3. A project has stable scope for module A but uncertain requirements for module B. What approach should be selected?

4. True or False: Hybrid approaches always use 50% predictive and 50% adaptive methods.

5. If requirements are well known and straightforward to define, which approach may be optimal?

PMBOK v8 Reference

Section 4.2.3 - Hybrid Approaches Section 4.3 - Considerations for a Development Approach Selection Section 4.3.1 - Deliverables