Development Approach Principle: Tailoring Life Cycles for Project Success

PMBOK v8 Definition

The Development Approach principle guides how a project selects and applies the most appropriate life cycle model—predictive, adaptive, hybrid, iterative, or incremental—based on project characteristics, requirements certainty, and delivery needs. PMBOK v8 defines this as a core principle that integrates with project tailoring decisions, where the development approach "determines how the project's product, service, or result is developed, built, or delivered" and directly influences the project life cycle structure, phase relationships, and delivery frequency.

Why It Matters for the Exam

The Development Approach principle appears frequently in PMI exam questions about project life cycle selection, tailoring decisions, and understanding when to use predictive versus adaptive approaches. Questions typically present a scenario describing project uncertainty, requirement stability, or customer involvement, and ask which development approach best fits the situation. This concept also connects directly to the "Adopt a Holistic View" principle and the "Be an Accountable Leader" principle.

Key Points to Remember (for the exam)

• Three Main Approaches: Predictive (waterfall), Adaptive (agile), and Hybrid (combination of both)
• Adaptive Subtypes: Iterative development approach (refining through repetition), Incremental development approach (delivering in usable pieces), and Agile development approach (responding to change)
• Selection Drivers: Requirements certainty, ease of change, stakeholder influence, complexity, and resource availability
• Inverted Triangle Concept: Predictive approaches have high certainty and low ease of change; adaptive approaches have lower certainty but higher ease of change
• Hybrid Development Approach: Combines elements of predictive and adaptive approaches, often using predictive for planning and adaptive for execution
• Key Constraint Options: For adaptive approaches, constraints (scope, schedule, cost, quality) are more flexible than in predictive approaches
• Project Phases Relationship: Predictive uses sequential phases; adaptive uses iterative cycles with repeated feedback loops

Typical PMI Exam Example

A project involves developing a mobile application for a client who cannot define all requirements upfront but needs a working prototype every two weeks for user testing. The project team has experience with agile methods, and the technology is relatively new to the market. Which development approach is most appropriate? Answer: Adaptive development approach (specifically Agile), because requirements are uncertain, frequent delivery is needed, and the team has adaptive experience.

PMI Exam Traps

• Trap: Confusing "iterative" with "incremental"

  • Reality: Iterative improves through repeated cycles; incremental delivers usable pieces progressively

• Trap: Thinking hybrid means "all predictive" or "all adaptive"

  • Reality: Hybrid intentionally combines elements from both approaches based on project needs

• Trap: Assuming predictive is always better for complex projects

  • Reality: Complexity often requires adaptive approaches because requirements emerge during development

• Trap: Believing adaptive approaches have no planning

  • Reality: Adaptive approaches have continuous planning through iteration reviews and repeated feedback loops

Important PMI Connections

Quick Review Questions

1. A construction project has fully defined requirements, regulatory approvals needed upfront, and sequential handoffs between teams. Which development approach is most appropriate?

2. What is the key difference between an iterative development approach and an incremental development approach according to PMBOK v8?

3. When would a hybrid development approach be more appropriate than a purely predictive or purely adaptive approach?

4. How does the "inverted triangle concept" relate to constraint options for adaptive development approaches?

5. A software project faces high uncertainty about user needs but requires frequent stakeholder feedback. Which development approach should the project manager recommend?

PMBOK v8 Reference

Section 4.3 - Development Approach and Life Cycle Performance Domain Section 3.3 - Development Approach Principle (pages 59-67)