Backlog Management: The Adaptive Change Control Technique

PMBOK v8 Definition

Backlog management is primarily used in adaptive approaches to maintain the list of backlog items to be worked on during a project. It refers to the process by which the owner of the backlog, commonly a product owner, assists in keeping the backlog up to date. In adaptive approaches, backlog management is the technique used to manage changes. The list of backlog items is ranked in order of business value or importance to the customer and sized by the development team so that the highest value items are selected and delivered in the next development cycle.

Why It Matters for the Exam

This concept appears frequently in questions about adaptive/agile project management, specifically in situations testing your understanding of how changes are managed in iterative environments. PMI exam questions often present scenarios where a product owner is reprioritizing work or refining requirements, and you must identify the correct technique as backlog management or backlog refinement. Expect these questions in the "Adaptive Approaches" and "Change Management" domains.

Key Points to Remember (for the exam)

• Primary Purpose: Backlog management is the technique used to manage changes in adaptive approaches.
• Backlog Owner: The product owner (not the project manager) is responsible for keeping the backlog up to date.
• Ranking Criteria: Items are ranked by business value or importance to the customer.
• Sizing Responsibility: The development team sizes the backlog items.
• Distinction: Product backlog = complete list of desired features and changes. Sprint backlog = subset selected for a specific iteration.
• Dependencies Considered: Dependencies and constraints can impact the order of new items and changes in the backlog.
• Backlog Refinement: This is the progressive elaboration and reprioritization of the backlog to identify work for an upcoming iteration.

Typical PMI Exam Example

A software project uses an adaptive approach. The product owner receives a new feature request from a key stakeholder. The development team has already committed to the current iteration's work. What should the product owner do FIRST?

Answer: Add the new feature to the product backlog, rank it by business value relative to existing items, and consider dependencies before reprioritizing for the next iteration.

PMI Exam Traps

• Trap: Confusing the product owner's role with the project manager's role in backlog management.

  • Reality: The product owner manages the backlog; the project manager facilitates the process but does not own the backlog.

• Trap: Assuming backlog management is only for adding new items.

  • Reality: Backlog management includes ranking, sizing, removing, and reprioritizing items, as well as managing dependencies.

• Trap: Confusing backlog management with backlog refinement.

  • Reality: Backlog management is the overall technique for managing changes. Backlog refinement is a specific technique within it, focused on progressive elaboration and reprioritization for upcoming iterations.

• Trap: Thinking the product backlog and sprint backlog are the same.

  • Reality: The product backlog contains the complete list; the sprint backlog is only the subset selected for delivery in a specific iteration.

Important PMI Connections

Quick Review Questions

1. In an adaptive project, who is responsible for keeping the product backlog up to date?
2. What is the primary criterion for ranking items in the product backlog?
3. What is the difference between a product backlog and a sprint backlog?
4. What is backlog refinement, and how does it relate to backlog management?
5. In adaptive approaches, what technique is used to manage changes?

PMBOK v8 Reference

Section 4.6 - Backlog Management (Definitions section) and related content on adaptive approaches throughout the PMBOK v8 Guide.

This article is optimized for PMI exam preparation. Focus on memorizing the distinctions between backlog types and the product owner's role.