Predictive Development Approach: Early Project Planning and Stability

PMBOK v8 Definition

The predictive development approach is a project lifecycle method where needs, quality requirements, and risks can be well defined in the early phases and are expected to remain relatively stable. This approach allows the project team to capture reliable certainty early in the project and to perform much of the planning up front. It is optimal for projects or phases where the cost of iterating far exceeds its value, such as the build phase of many construction projects or projects in heavily regulated environments like healthcare.

Why It Matters for the Exam

This concept frequently appears in PMI exam questions about development approach selection, lifecycle determination, and tailoring. You will see it in situational questions asking which approach is best for a given project environment, particularly when requirements are clear, stable, and regulatory constraints exist.

Key Points to Remember (for the exam)

• Primary Characteristic: Requirements are well-defined early and remain relatively stable throughout the project
• Optimal Use Case: Projects where cost of iteration exceeds value (e.g., construction build phases)
• Regulatory Fit: Heavily regulated environments (healthcare, pharmaceuticals, medical devices) often require predictive approaches with phase gates
• Planning Timing: Most planning is performed up front, before execution begins
• Risk Profile: Enables early capture of reliable certainty; risks are identified and analyzed early
• Key Differentiator: Contrasts with adaptive/iterative approaches where requirements emerge and evolve
• Phase Gates: Often required by regulators to assess progress and approve continuation (e.g., drug development)

Typical PMI Exam Example

A pharmaceutical company is developing a new drug treatment. The regulatory agency requires phase gates to assess whether sufficient promise has been demonstrated before allowing further development. The project team has clearly defined requirements and stable quality standards. Which development approach should the team use?

Answer: Predictive approach, because requirements are stable, regulatory oversight demands phase gates, and the cost of iterating (repeating clinical trials) far exceeds its value.

PMI Exam Traps

• Trap: Confusing predictive with "waterfall" as a rigid, inflexible model

  • Reality: Predictive approach is about early certainty and up-front planning, not necessarily waterfall; it can include phase gates and reviews

• Trap: Assuming predictive means no iteration at all

  • Reality: Predictive approach is optimal when cost of iteration exceeds value; some iteration may still occur in early phases (e.g., requirements definition)

• Trap: Thinking predictive is always the best approach

  • Reality: Predictive is only optimal when requirements are stable and well-defined; adaptive approaches are better when uncertainty is high

• Trap: Confusing predictive with "all planning done once"

  • Reality: Risk identification is iterative even in predictive projects; the approach allows continuous identification and assessment as more information becomes available

Important PMI Connections

Quick Review Questions

1. In which type of project environment is a predictive development approach considered optimal?
2. Why is risk identification considered an iterative process even in predictive projects?
3. What is the relationship between regulatory requirements and the predictive approach?
4. How does a predictive approach differ from an adaptive approach regarding when planning occurs?
5. When would the cost of iterating far exceed its value, making a predictive approach optimal?

PMBOK v8 Reference

Section 2.7 - Risk Performance Domain (specifically the context describing predictive development approach characteristics and the Risk performance domain processes including Plan Risk Management, Perform Risk Analysis, Plan Risk Responses, and Implement Risk Responses)