Methods Designed for Larger-Scale Purposes in Agile
PMBOK v8 Definition
The PMBOK v8 makes a critical distinction between agile methods designed for a single team versus those designed for larger-scale purposes. Methods designed for larger-scale purposes provide structured approaches to problem-solving or task completion across multiple teams. A method is defined as a systematic way of doing something, typically involving a series of steps or procedures designed to achieve a specific outcome. There is also a meaningful difference between larger-scale methods and larger-scale tool kits, where methods offer more prescriptive guidance and structured approaches.
Why It Matters for the Exam
This concept appears frequently in PMI exam questions about tailoring development approaches and selecting the appropriate life cycle for complex, multi-team projects. Questions typically test your ability to distinguish between team-level agile methods (like Scrum, XP) and scaled agile methods (like SAFe®, LeSS, Scrum of Scrums), and to understand how breadth and depth of coverage differ across approaches.
Key Points to Remember (for the exam)
-
Two Key Distinctions: Agile methods are distinguished by (1) single-team vs. larger-scale purpose, and (2) breadth of coverage (how much of the project or product life cycle the approach covers) vs. depth of coverage (how detailed or prescriptive the guidance is).
-
Scaled Methods Examples: SAFe®, LeSS, and Scrum of Scrums are explicitly identified as larger-scale methods in PMBOK v8 Figure 4-7.
-
Team Methods Examples: Scrum, XP, Kanban, FDD, Crystal, DSDM, and Agile UP are identified as team-level methods.
-
Method vs. Tool Kit: A method is a systematic way of doing something with steps/procedures; a tool kit is less prescriptive. This distinction is tested on the exam.
-
Breadth vs. Depth Trade-off: Methods with greater breadth cover more of the project life cycle but may offer less detailed guidance; methods with greater depth provide more prescriptive guidance but may cover less of the life cycle.
-
Life Cycle Flexibility: When selecting methods, the project life cycle should be flexible enough to meet or exceed project objectives while protecting and enhancing the project's value proposition.
-
Organizational Variables: Organizational structure, culture, capability, project team size, and location influence the choice of development approach, including whether to use scaled methods.
Typical PMI Exam Example
A large organization is implementing a complex software system across five teams in three locations. Requirements are not fully defined up front, and partial deliveries are expected. The project manager needs a structured approach that coordinates multiple teams while maintaining alignment with the overall product vision. Which type of approach should be selected?
Answer: A larger-scale agile method (such as SAFe® or LeSS), because these methods are designed for multi-team coordination and provide structured approaches for scaling agile practices.
PMI Exam Traps
-
Trap: Confusing "method" with "tool kit" → Reality: Methods provide systematic steps/procedures; tool kits are less prescriptive frameworks.
-
Trap: Assuming Scrum is always a scaled method → Reality: Scrum is designed for a single team; scaled versions (Scrum of Scrums, LeSS) exist for larger purposes.
-
Trap: Thinking breadth and depth are the same → Reality: Breadth covers how much of the life cycle is addressed; depth covers how detailed/prescriptive the guidance is.
-
Trap: Believing all agile methods work equally well at scale → Reality: Some methods (SAFe®, LeSS) are specifically designed for larger-scale purposes; team methods may not provide sufficient coordination mechanisms.
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Development Approach Selection | Decision input | Scaled methods are selected when organizational complexity, team size, and interdependencies require multi-team coordination |
| Project Life Cycle | Determines method choice | Adaptive life cycles with iterations and feedback loops are compatible with scaled methods; breadth of coverage affects life cycle selection |
| Organizational Structure | Influences method choice | Matrix or projectized structures with large teams may require scaled methods; culture and capability affect implementation success |
| Product Development | Application area | Scaled methods are appropriate for digital projects and new product development where requirements evolve and partial deliveries are expected |
Quick Review Questions
-
What is the difference between a larger-scale method and a larger-scale tool kit according to PMBOK v8?
-
Which agile methods are explicitly identified as scaled approaches in PMBOK v8 Figure 4-7?
-
What factors should a project manager consider when deciding between a single-team agile method and a larger-scale agile method?
-
How do breadth of coverage and depth of coverage differ in the context of agile methods?
-
What organizational variables influence the choice of development approach, particularly when considering scaled methods?
PMBOK v8 Reference
Section 4 – Project Life Cycles (Figure 4-7: Agile Approaches Plotted by Breadth and Depth; related text on methods designed for larger-scale purposes)