Agile Approaches Plotted by Life Cycle Coverage and Guidance Detail

PMBOK v8 Definition

"Breadth of Life Cycle Coverage" and "Depth of Guidance Detail" are the two dimensions used to plot and compare agile approaches in PMBOK v8. Breadth refers to how much of the project life cycle an agile method covers (from project initiation through delivery), while Depth refers to the level of prescriptive detail and procedural guidance the method provides to teams. This framework helps practitioners select appropriate agile methods based on project needs, ranging from single-team methods like Scrum (narrow breadth, moderate depth) to scaled approaches like SAFe® (broad breadth, high depth).

Why It Matters for the Exam

The PMI exam frequently tests your ability to distinguish between agile methods based on their scope (breadth) and prescriptiveness (depth). Questions appear in the "Adaptive Approaches" domain, often asking you to identify which agile method is appropriate for a given project scenario—particularly when requirements are not fully defined up front and where partial deliveries and changes are expected during the project. Understanding this plotting helps you avoid confusion between team-level methods (Scrum, XP) and enterprise-scale frameworks (SAFe®, LeSS).

Key Points to Remember (for the exam)

Two Dimensions: Breadth (life cycle coverage) and Depth (guidance detail) are the ONLY two axes used to plot agile approaches in PMBOK v8
Team Methods (Narrow Breadth): Scrum, XP, Kanban, Crystal—designed for single teams, covering only the development portion of the project life cycle
Scaled Approaches (Broad Breadth): SAFe®, LeSS, Scrum of Scrums—cover multiple teams and extend across the entire project life cycle from definition to delivery
Depth Spectrum: Methods range from minimal guidance (Lean, Kanban) to highly prescriptive (XP, SAFe®)
Adaptive Life Cycle Fit: These approaches are specifically appropriate for "development projects, where requirements are not fully defined up front and where partial deliveries and changes are expected during the project"
New Product Development: Adaptive approaches are also appropriate for projects where final features are refined based on market needs (e.g., new mobile app or web service development)
Digital Projects: Digital projects are specifically cited as appropriate contexts for adaptive development approaches

Typical PMI Exam Example

A project manager is leading a new mobile app development project where requirements will be refined based on market feedback. The organization has 3 co-located teams working on different features. Which agile approach plotted with narrow breadth and moderate depth would best fit this scenario?

Answer: Scrum (team method, narrow breadth, moderate depth guidance)

PMI Exam Traps

Trap: Confusing "Breadth" with team size
- Reality: Breadth refers to life cycle coverage (how much of the project from start to finish), NOT the number of team members
Trap: Assuming all agile methods have the same depth of guidance
- Reality: Depth varies significantly—Lean and Kanban provide minimal guidance, while XP and SAFe® provide highly detailed procedural guidance
Trap: Thinking Scrum is a scaled approach
- Reality: Scrum is a team method with narrow breadth; Scrum of Scrums is the scaled approach for coordinating multiple Scrum teams
Trap: Confusing adaptive approaches with predictive planning
- Reality: Adaptive approaches are specifically for projects where requirements are NOT fully defined up front and changes are expected

Important PMI Connections

Related Concept	Relationship Type	Exam Attention Point
Adaptive Life Cycle	Complementary	Adaptive approaches use iterative/adaptive life cycles; breadth determines how much of the life cycle is covered
Product Backlog	Input to	In agile projects, backlog decomposition (epics, features, user stories) corresponds to scope structure development
Agile Release Planning	Output from	Release planning (3-6 months) determines iteration count and is tied to breadth of life cycle coverage
Single Team vs. Scaled	Distinction	Team methods (narrow breadth) vs. scaled approaches (broad breadth) is a key exam distinction
Digital Projects	Application Context	Digital projects are explicitly cited as appropriate for adaptive approaches in PMBOK v8

Quick Review Questions

What are the two dimensions used to plot agile approaches in PMBOK v8?
Which agile method would you recommend for a single-team project with minimal prescriptive guidance needs?
How does SAFe® differ from Scrum in terms of breadth of life cycle coverage?
For what type of project are adaptive approaches specifically recommended according to PMBOK v8?
What is the difference between "Scrum" and "Scrum of Scrums" in the breadth-depth plotting?

PMBOK v8 Reference

Section 4 – Project Life Cycles
Figure 4-7. Agile Approaches Plotted by Breadth and Depth
Pages 64-65 (The Standard for Project Management)