The Project Team Determines Scope from Prioritized Backlog

PMBOK v8 Definition

In adaptive and hybrid life cycles, the project team determines the scope they can achieve based on the prioritized backlog, estimates the work involved, and works collaboratively throughout the iteration to develop the scope. The backlog is an ordered list of work to be done, often written as user stories, and prioritized by the business to manage and organize an adaptive or agile project's work. This approach is part of the Planning Performance Domain, where scope refinement occurs through several different iterations rather than being fully defined upfront.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions about adaptive and hybrid life cycles, particularly in scenarios asking how agile teams manage scope versus traditional predictive approaches. Questions test your understanding that in adaptive projects, scope is progressively elaborated through iterations based on backlog prioritization, not defined completely at the start. You will see this in situational questions about scope management, iteration planning, and the differences between predictive and adaptive planning.

Key Points to Remember (for the exam)

• Core Definition: The project team determines achievable scope from the prioritized backlog, estimates work, and collaborates throughout the iteration to develop scope.

• Backlog Nature: A backlog is an ordered list of work (often user stories) prioritized by the business to manage adaptive project work.

• Scope Refinement: In adaptive projects, scope is refined through different iterations rather than fully defined upfront with a scope baseline.

• Release Backlog: The release backlog helps organize work to be delivered at the end of a release cycle, which may encompass multiple sprints or iterations.

• Basis of Estimates: Supporting documentation that outlines assumptions, constraints, levels of detail, ranges, and confidence levels used in establishing project estimates.

• Tailoring Challenge: Hybrid approaches are more challenging because overall expectations have a scope baseline, schedule baseline, and cost baseline, while subteams work in iterations on backlog user stories.

• Product Goals Focus: Rather than delivering all user stories on the backlog, the team focuses on main product goals to satisfy customer expectations.

Typical PMI Exam Example

A software development project uses an adaptive life cycle. During iteration planning, the product owner presents the prioritized backlog. The development team reviews the highest-priority user stories, estimates the effort required, and commits to delivering the scope they can realistically complete within the two-week iteration. The team collaborates daily to develop the scope, adjusting as needed while maintaining focus on the iteration goal.

PMI Exam Traps

• Trap: Confusing backlog with a complete scope baseline

• Reality: Backlog is an ordered, prioritized list that evolves; scope baseline is fixed and used in predictive projects

• Trap: Thinking all user stories on the backlog must be delivered

• Reality: The team focuses on main product goals to satisfy customer expectations, not necessarily all backlog items

• Trap: Assuming adaptive projects have no scope management

• Reality: Scope is managed through backlog refinement and prioritization across iterations

• Trap: Confusing release backlog with product backlog

• Reality: Release backlog organizes work for a specific release cycle (multiple sprints); product backlog contains all potential work

Important PMI Connections

Quick Review Questions

1. What is the primary mechanism for determining scope in an adaptive project life cycle?

2. How does the project team determine what scope they can achieve during an iteration?

3. What is the difference between a product backlog and a release backlog?

4. In a hybrid project, why might tailoring be more challenging for scope management?

5. What does the basis of estimates documentation typically include?

PMBOK v8 Reference

Section 2.2.3.1 - Examples (Planning Performance Domain) Section on Develop Scope Structure (Planning Performance Domain) Section on Monitor and Control Scope (Planning Performance Domain) Section on Backlog definition (Planning Performance Domain)