Hybrid Development Approach in Projects: Combining Predictive and Adaptive Methods

PMBOK v8 Definition

A hybrid development approach incorporates elements from both predictive and adaptive approaches within a single project. This approach is appropriate when there is uncertainty or risk around requirements, when deliverables can be modularized, or when different project teams develop different deliverables. At the project level, this combination represents a hybrid approach, though individual teams may only experience a predictive or adaptive development approach.

Why It Matters for the Exam

The hybrid approach appears frequently in PMI exam questions about development approach selection and tailoring. Exam questions test your understanding that most modern projects require a hybrid approach, and that hybrid exists on a spectrum (from primarily predictive with adaptive elements to primarily adaptive with predictive elements). Questions often appear in situational scenarios where you must identify which approach best fits a project with mixed requirements.

Key Points to Remember (for the exam)

• Definition: Hybrid approach combines predictive and adaptive elements within one project
• Three Levels of Hybrid: Level 1 (predictive dominant with adaptive elements), Level 2 (both contribute significantly), Level 3 (adaptive dominant with predictive elements)
• Common Application: Construction projects with IT integration (predictive for building, adaptive for computing capabilities)
• Tailoring Options for Processes: Elements can be Added, Modified, Removed, Blended, or Aligned
• Three Project Aspects to Tailor: Life cycle and development approach selection, Processes, and Engagement
• Key Driver: Most projects today require hybrid because relying solely on one approach is insufficient for modern project complexities
• Team Perspective: Individual teams may only experience one approach even though the project uses hybrid

Typical PMI Exam Example

A project involves building a new data center. The construction team uses predictive approaches for the physical building construction and finishing. The computing team uses an adaptive approach for understanding and establishing the computing capabilities required. At the project level, this is a hybrid approach, but each team experiences only their respective development approach.

PMI Exam Traps

• Trap: Thinking hybrid means every team uses both approaches

  • Reality: Individual teams may only experience predictive OR adaptive; the hybrid exists at the project level

• Trap: Assuming hybrid is only for large, complex projects

  • Reality: Hybrid is appropriate whenever deliverables can be modularized or when requirements have uncertainty

• Trap: Confusing hybrid with "no approach" or "random approach"

  • Reality: Hybrid is a deliberate combination with defined levels (1, 2, 3) on a spectrum

• Trap: Believing predictive and adaptive cannot coexist

  • Reality: They coexist naturally; a small adaptive element can exist within a primarily predictive project

Important PMI Connections

Quick Review Questions

1. A construction project involves building a smart building with complex IT systems. The building construction follows a fixed plan, while the IT systems require flexibility during development. What development approach is being used?

2. In a hybrid approach where predictive elements are the dominant contributor and adaptive elements reduce specific project pain points, what hybrid level is this?

3. A project manager is tailoring processes for a hybrid project. What are the five actions that can be taken on process elements during tailoring?

4. True or False: In a hybrid project, every team member must work with both predictive and adaptive approaches simultaneously.

5. A data center project has two teams: one building the physical structure and one developing computing capabilities. The construction team follows a predictive approach; the computing team follows an adaptive approach. At what level does the hybrid approach exist?

PMBOK v8 Reference

Section 3.3 - Tailoring Section 3.3.1 - Life Cycle and Development Approach Selection Section 3.3.2 - Processes