Figure Approaches: Development Life Cycle Selection for Exam

PMBOK v8 Definition

Figure Approaches in PMBOK v8 refer to the visual representations of development approaches across a spectrum, ranging from predictive (waterfall) to adaptive (agile) life cycles. These figures illustrate how variables like cost, scope, and time are impacted differently depending on the approach selected, and show the constraint options available for adaptive approaches, including fixed time, fixed scope, or fixed budget.

Why It Matters for the Exam

Development approach selection is frequently tested on the PMI exam because it directly influences how the project is planned, executed, and controlled. Expect situational questions where you must identify the appropriate approach based on project characteristics, and questions asking you to recognize which constraints are typically fixed in adaptive versus predictive environments.

Key Points to Remember (for the exam)

Spectrum of Approaches: Development approaches exist on a continuum from predictive to adaptive, with hybrid approaches in between—there is no single "correct" approach for all projects
Variable Impact Over Time: Cost of changes and risk increase exponentially over time in predictive approaches, while adaptive approaches keep these variables more constant throughout the project
Constraint Options for Adaptive: In adaptive approaches, the project team typically fixes time and cost while allowing scope to vary, unlike predictive where scope is fixed
Predictive Life Cycle: Characterized by sequential phases (requirements, design, build, test, deploy) with detailed planning upfront
Adaptive Life Cycle: Iterative and incremental delivery with evolving requirements and frequent feedback loops
Hybrid Approaches: Can be used simultaneously (adaptive component within predictive) or sequentially (adaptive development followed by predictive rollout)
Common Confusion: Many candidates confuse "incremental delivery" within a predictive life cycle with a fully adaptive approach—incremental delivery can exist in predictive projects

Typical PMI Exam Example

A project manager is leading a software development project with clearly defined regulatory requirements but uncertain user interface preferences. The team needs to deliver core compliance features on a fixed date while iterating on the user experience. Which development approach combination would the PMBOK v8 recommend?

Answer: A largely predictive approach with an adaptive component (Figure 4-10), where the compliance requirements follow a predictive life cycle and the UI development uses adaptive methods.

PMI Exam Traps

Trap: Confusing "predictive with incremental delivery" (Figure 4-5) with fully adaptive approaches
Reality: Predictive with incremental delivery still plans the entire scope upfront but delivers in batches; adaptive approaches evolve scope continuously
Trap: Believing adaptive approaches have no planning
Reality: Adaptive approaches plan iteratively—just-in-time planning rather than upfront detailed planning
Trap: Assuming hybrid means 50% predictive and 50% adaptive
Reality: Hybrid can be predominantly predictive with an adaptive component (Figure 4-10) or predominantly adaptive with a predictive component (Figure 4-11)
Trap: Thinking all projects must use one approach exclusively
Reality: PMBOK v8 explicitly shows approaches can be used simultaneously (Figure 4-9) or sequentially (Figure 4-8)

Important PMI Connections

Related Concept	Relationship Type	Exam Attention Point
Project Boundaries (Figure 4-12)	Defines scope of approach	Approach selection determines how boundaries are managed
Focus Area Interactions (Figure 4-13)	Implementation context	Predictive approaches have different focus area interactions than adaptive
Project Management Mindset (Figure 3-1)	Foundation for approach selection	Mindset principles (holistic view, value focus) guide approach choice
Quality Embedding (Figure 3-4)	Affected by approach	Adaptive approaches embed quality continuously; predictive uses phase-gate reviews

Quick Review Questions

According to Figure 4-1, how does the impact of variables (cost of changes, stakeholder influence, risk) change over time in a predictive approach compared to an adaptive approach?
In an adaptive development approach, which three constraints are typically considered flexible versus fixed, according to Figure 4-3?
A project uses adaptive development for the first six months followed by a predictive rollout for deployment. Which PMBOK v8 figure illustrates this approach?
What is the key difference between Figure 4-4 (Sample Predictive Life Cycle) and Figure 4-5 (Sample Predictive Life Cycle With Incremental Delivery)?
When a project simultaneously uses adaptive methods for one component and predictive methods for another (Figure 4-9), what is this approach called?

PMBOK v8 Reference

Section 4 – Development Approach and Life Cycle Performance Domain Figures 4-1 through 4-13, specifically:

Figure 4-1: Impact of Variables Over Time
Figure 4-2: The Spectrum of Development Approaches
Figure 4-3: Constraint Options for Adaptive Approaches
Figure 4-4: Sample Predictive Life Cycle
Figure 4-5: Sample Predictive Life Cycle With an Incremental Delivery
Figure 4-6: Life Cycle With an Adaptive Development Approach
Figure 4-8: Adaptive Development Followed by a Predictive Rollout
Figure 4-9: A Hybrid of Adaptive and Predictive Approaches Used Simultaneously
Figure 4-10: A Largely Predictive Approach With an Adaptive Component
Figure 4-11: A Largely Adaptive Approach With a Predictive Component