Agile Methods: Single Team vs. Larger-Scale Distinctions

PMBOK v8 Definition

The Standard for Project Management distinguishes between agile methods designed for a single team versus those designed for larger-scale purposes. Methods vary in breadth of coverage (how much of the project or product life cycle the approach covers) and depth of coverage (how detailed or prescriptive the guidance is). A method is a systematic way of doing something, typically involving a series of steps or procedures designed to achieve a specific outcome, providing structured approaches to problem-solving or task completion.

Why It Matters for the Exam

This distinction frequently appears in PMI exam questions testing your ability to select appropriate agile approaches based on project scale and organizational complexity. Questions typically present scenarios where you must determine whether a single-team agile method or a scaled agile framework is most appropriate, often combined with tailoring considerations.

Key Points to Remember (for the exam)

Single-Team vs. Larger-Scale: Agile methods are distinguished by whether they are designed for a single team or larger-scale purposes—this is the primary classification tested on the exam.
Breadth vs. Depth of Coverage: Breadth refers to how much of the project or product life cycle the approach covers; depth refers to how detailed or prescriptive the guidance is. These dimensions help you evaluate method suitability.
Method Definition: A method is a systematic way of doing something, involving a series of steps or procedures designed to achieve a specific outcome—not just a collection of practices.
Methods vs. Tool Kits: There is a meaningful difference between larger-scale methods and larger-scale tool kits. Methods provide structured approaches; tool kits offer collections of practices.
Roles Sharing PM Responsibilities: In agile environments, functions like product owner, product manager, scrum master, agile coach, agile manager, agile delivery manager, team lead, development team, or project team may share project management responsibilities usually performed by project managers.
Common Confusion: Confusing method scope (single-team vs. scaled) with method formality (prescriptive vs. flexible)—these are separate dimensions.

Typical PMI Exam Example

A project manager is selecting an agile approach for a program involving 12 teams working on interconnected product features. The PMI exam tests whether you recognize this requires a larger-scale agile method rather than a single-team approach like basic Scrum. The correct answer emphasizes distinguishing single-team from larger-scale methods.

PMI Exam Traps

Trap: Assuming "agile" means only single-team methods like Scrum. Reality: Agile includes methods designed for larger-scale purposes; the distinction is explicitly tested.
Trap: Confusing breadth of coverage with depth of coverage. Reality: Breadth = life cycle scope; depth = level of prescription. Both are separate evaluation criteria.
Trap: Thinking methods and tool kits are interchangeable terms. Reality: Methods are systematic step-by-step approaches; tool kits are collections—this distinction matters in exam scenarios.
Trap: Assuming only the project manager performs project management tasks in agile. Reality: Multiple roles (product owner, scrum master, agile coach, team lead, development team) may share project management responsibilities.

Important PMI Connections

Related Concept	Relationship Type	Exam Attention Point
Tailoring Considerations	Applies to method selection	Tailoring must consider project scale (single-team vs. larger-scale) when choosing agile methods
Project Management Principles	Foundation for method selection	Principles guide behavior but are not prescriptive; methods provide structure
Value Delivery System	Context for method application	Method selection depends on how the project fits into the broader value delivery system
Agile/Adaptive Environments	Environment where methods are applied	Roles sharing PM responsibilities is a key characteristic of agile environments

Quick Review Questions

When selecting an agile method for a project with 15 teams, what is the primary distinction you must consider?
What is the difference between breadth of coverage and depth of coverage in agile methods?
According to PMBOK v8, what defines a "method" as distinct from a tool kit?
Which roles in agile environments may share project management responsibilities typically performed by project managers?
How does the distinction between single-team and larger-scale agile methods affect method selection?

PMBOK v8 Reference

Section 64 - The Standard for Project Management (Agile Methods: Single Team vs. Larger-Scale Distinctions)