Development Approach: The Means to Create and Evolve Project Deliverables

PMBOK v8 Definition

A development approach is the means used to create and evolve a product, service, or result during the project life cycle. Note that the term "development approach" is separate from the term "development phase of the project." The development approach refers to the method used to create and evolve the product, service, or result during the project life cycle, such as predictive, adaptive, or hybrid methods. The development approach defines how the project will be managed and executed.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions about project tailoring and life cycle selection. Expect situational questions where you must choose the correct development approach based on project characteristics such as requirements certainty, degree of innovation, and scope stability. The exam tests your ability to distinguish between predictive, adaptive, and hybrid approaches and to understand that the project manager typically makes this choice in consultation with the project management team.

Key Points to Remember (for the exam)

• Three Main Approaches: Predictive (plan-driven), Adaptive (change-driven), and Hybrid (combination of both). These exist on a spectrum from predictive on one end to adaptive on the other.

• Key Differentiator: The development approach is about how you create and evolve the product, NOT about the development phase (which is a specific stage where creation and testing occur).

• Degree of Innovation: When new or complex technological and/or business model innovation is needed, an adaptive approach may be optimal.

• Requirements Certainty: When requirements are well known and straightforward to define, a predictive approach may be optimal.

• Scope Stability: The less stable the scope is, the more optimal it will be to apply an adaptive approach.

• Decision Maker: The choice of development approach is typically made by the project manager in consultation with the project management team.

• Consistent Feedback: Adaptive approaches enable consistent feedback, which leads to detecting risks and their impacts at an earlier stage.

Typical PMI Exam Example

A project involves developing a software product with highly uncertain requirements and rapidly changing technology. The project manager must decide which development approach to use. Based on the degree of innovation and scope instability, the optimal approach is adaptive.

PMI Exam Traps

• Trap: Confusing "development approach" with "development phase"

• Reality: Development approach is the method (predictive, adaptive, hybrid); development phase is a specific stage where creation and testing of deliverables occur.

• Trap: Assuming predictive is always best for any project

• Reality: Predictive is optimal only when requirements are well known and scope is stable; adaptive is better for innovation and uncertainty.

• Trap: Thinking hybrid is always the safest choice

• Reality: Hybrid is appropriate only when project characteristics justify combining elements of both predictive and adaptive approaches.

• Trap: Believing the project manager alone selects the development approach

• Reality: The choice is made by the project manager in consultation with the project management team.

Important PMI Connections

Quick Review Questions

1. What are the three commonly used development approaches described in PMBOK v8?

2. When is a predictive development approach considered optimal?

3. Who typically makes the choice of development approach for a project?

4. How does an adaptive development approach affect risk detection?

5. What is the key difference between "development approach" and "development phase"?

PMBOK v8 Reference

Section 4.2 - Project Development Approaches