Backlog Management: The Process of Keeping the Product Backlog Updated

PMBOK v8 Definition

Backlog management refers to the process by which the owner of the backlog, commonly a product owner, assists in keeping the backlog up to date during a project. 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.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions about adaptive and agile project management, particularly in questions testing your understanding of scope management and change control in iterative environments. You will encounter it in situational questions where the product owner must reprioritize work or when distinguishing between different types of backlogs.

Key Points to Remember (for the exam)

• Definition: Backlog management is the ongoing process of keeping the backlog up to date, performed primarily by the product owner.
• Product Backlog: Contains the complete list of desired features and changes for the product, including requirements, features, epic user stories, and user stories.
• Sprint/Iteration Backlog: A subset of the product backlog containing selected user stories and required tasks for the current iteration only.
• Release Backlog: A subset of the product backlog that includes items planned for a specific release, which may encompass multiple sprints or iterations.
• Prioritization: The backlog is prioritized by the business to manage and organize work in adaptive or agile projects.
• Common Confusion: Distinguishing between product backlog (full scope) versus sprint backlog (current iteration work) is frequently tested.
• Change Management: In adaptive approaches, backlog management is the technique used to manage changes.

Typical PMI Exam Example

A product owner receives new feature requests from stakeholders during the third sprint of a six-sprint project. According to PMBOK v8, how should the product owner handle these requests? The correct answer is to add them to the product backlog, reprioritize the backlog based on business value, and include them in future sprints if they become the highest priority items.

PMI Exam Traps

• Trap: Confusing product backlog with sprint backlog

  • Reality: Product backlog contains ALL desired features; sprint backlog contains ONLY items selected for the current iteration.

• Trap: Thinking the project manager manages the backlog

  • Reality: The product owner (backlog owner) is responsible for keeping the backlog up to date.

• Trap: Believing backlog items cannot change once the project starts

  • Reality: Backlog management is the technique used to manage changes in adaptive approaches; items are continuously reprioritized.

• Trap: Confusing release backlog with product backlog

  • Reality: Release backlog is a subset for a specific release cycle, while product backlog represents the overall scope and vision.

Important PMI Connections

Quick Review Questions

1. Who is primarily responsible for keeping the backlog up to date during an adaptive project?

2. What is the difference between a product backlog and an iteration backlog?

3. In adaptive approaches, what technique is used to manage changes to project scope?

4. What types of items are typically included in a product backlog according to PMBOK v8?

5. How does a release backlog differ from a sprint backlog in terms of time horizon?

PMBOK v8 Reference

Section 2.4.2 - Project Documents (Backlog subsection) and Section 4.6 - Adaptive Environments (Backlog Management)