Predictive Development Approach (Waterfall)
PMBOK v8 Definition
A predictive development approach is a project life cycle method in which the project scope, time, and cost are determined in the early phases of the life cycle. This approach is also commonly known as the waterfall method. The predictive approach defines how the project will be managed and executed, with detailed planning occurring upfront before execution begins. It is positioned on one end of the development approach spectrum, opposite the adaptive (agile) approach, with hybrid methods occupying the middle ground.
Why It Matters for the Exam
The predictive approach appears frequently on the PMI exam because it represents the traditional, plan-driven project management model that forms the foundation of PMBOK principles. Questions typically test your ability to identify when a predictive approach is appropriate, distinguish it from adaptive approaches, and recognize its key characteristics in scenario-based questions. Expect this concept in questions about project life cycle selection, development approach tailoring, and governance decisions.
Key Points to Remember (for the exam)
- Definition Core: Scope, time, and cost are determined in the early phases of the life cycle
- Spectrum Position: One end of the development approach spectrum (predictive → hybrid → adaptive)
- Planning Timing: Detailed planning occurs upfront before execution begins
- Change Management: Changes are controlled through formal change control processes
- Delivery Cadence: Single delivery at the end of the project life cycle
- Risk Detection: Risks and their impacts are detected later compared to adaptive approaches
- Best For: Projects with clear, stable requirements and well-understood technology
Typical PMI Exam Example
A project manager is assigned to construct a new office building. The client has provided detailed architectural blueprints, and local regulations are well-established. The project has a fixed budget and completion date. Which development approach is most appropriate for this project?
Answer: Predictive approach, because scope, time, and cost are determined upfront, and requirements are stable and well-defined.
PMI Exam Traps
-
Trap: Confusing predictive approach with "no changes allowed"
- Reality: Changes are managed through formal change control processes, not prohibited
-
Trap: Assuming predictive means no feedback until the end
- Reality: Consistent feedback is still important; it leads to detecting risks at an earlier stage
-
Trap: Thinking predictive and adaptive are mutually exclusive for all projects
- Reality: Hybrid approaches combine elements from both ends of the spectrum
-
Trap: Confusing "development approach" with "development phase of the project"
- Reality: Development approach is the method used to create and evolve the product; development phase is a specific stage within the project life cycle where creation and testing occur
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Project Life Cycle | Component of | The predictive approach defines how the project life cycle is structured and executed |
| Adaptive Approach | Opposes (opposite end of spectrum) | Know when to select predictive vs. adaptive based on requirements stability |
| Hybrid Approach | Complements (middle of spectrum) | Hybrid combines predictive and adaptive elements; know what "mix" means |
| Project Phases | Influences | Predictive projects often use sequential phases with clear phase gates |
| Delivery Cadence | Determined by | Predictive approach typically uses single delivery at end of project |
| Risk Management | Impacted by | Predictive detects risks later; adaptive detects risks earlier through consistent feedback |
Quick Review Questions
-
In which phase of the project life cycle are scope, time, and cost determined for a predictive development approach?
-
A project has highly uncertain requirements and rapidly changing technology. Is a predictive approach appropriate? Why or why not?
-
What is the difference between a "development approach" and a "development phase of the project"?
-
On the development approach spectrum, where does the predictive approach fall relative to adaptive and hybrid approaches?
-
How does the timing of risk detection differ between predictive and adaptive development approaches?
PMBOK v8 Reference
Section 4.2 - Project Development Approaches (Includes subsections on predictive, adaptive, and hybrid methods, and considerations for selecting a development approach)