Backlog Work Process: Prioritized Scope Management in Adaptive Projects

PMBOK v8 Definition

A 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. The backlog reflects the current project needs, including the product requirements and user stories, and contains a reprioritized plan for the remaining work. In agile projects, the WBS corresponds to the product backlog, where work items can be broken down into epics and user stories.

Why It Matters for the Exam

The backlog concept appears frequently in PMI exam questions about adaptive/agile project management, scope management, and iteration planning. It is tested in situational questions asking how to organize work in agile environments, how to prioritize features, and how to differentiate between backlog types. Expect 2-4 questions on backlog-related topics in the exam.

Key Points to Remember (for the exam)

• Definition: A backlog is an ordered list of work to be done, written as user stories, prioritized by the business
• Primary Purpose: Provides a strategic view of the project's scope and value, helping the team stay aligned toward a common goal
• Agile WBS Equivalent: The product backlog corresponds to the WBS in agile projects
• Three Backlog Types:
  • Product backlog: Overall scope and vision of the product (prepared by product owner)
  • Iteration backlog: Subset for the current iteration (selected user stories + tasks)
  • Release backlog: Subset for a specific release (may encompass multiple sprints/iterations)
• Key Benefit: Helps the project team be aligned and working toward a common goal
• Documentation Content: Includes milestones, responsible parties, resource needs, and acceptance criteria
• Dynamic Nature: The backlog is continuously reprioritized and reflects current project needs

Typical PMI Exam Example

A project team is using agile methodology to develop a new mobile application. The product owner has created a prioritized list of features written as user stories. The team selects the highest-priority stories for the next two-week iteration. What is this prioritized list called? Answer: Product backlog. What is the subset of work selected for the current iteration called? Answer: Iteration backlog.

PMI Exam Traps

• Trap: Confusing product backlog with iteration backlog

  • Reality: Product backlog = complete prioritized list of all features; iteration backlog = subset selected for current iteration only

• Trap: Thinking backlog is only for agile projects

  • Reality: Backlogs are specifically for adaptive or agile projects; traditional projects use WBS and scope baseline

• Trap: Assuming backlog items are fixed and unchanging

  • Reality: Backlog is continuously reprioritized and reflects current project needs

• Trap: Confusing backlog with requirements documentation

  • Reality: Backlog contains prioritized user stories; requirements documentation is a separate artifact in traditional projects

Important PMI Connections

Quick Review Questions

1. What are the three types of backlogs commonly used in adaptive and agile projects?

2. Who typically prepares the product backlog?

3. How does the product backlog relate to the WBS in agile projects?

4. What is the key benefit of the backlog process according to PMBOK v8?

5. What information does detailed backlog documentation include?

PMBOK v8 Reference

Section 2.2.2 - Scope Performance Domain (Backlog subsection) Section 2.2.3 - Examples of Backlog Application

This article is based exclusively on PMBOK v8 content provided in the RAG context. All definitions, concepts, and relationships are direct references from the source material.