Backlog Items Development: Selection and Prioritization for Iterations

PMBOK v8 Definition

Backlog items development refers to the process where a subset of items is selected for delivery in a specific iteration. 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. Dependencies and constraints are also taken into account, which could impact the order of new items and changes in the backlog.

Why It Matters for the Exam

This concept appears frequently in agile and adaptive project management questions on the PMI exam. You will see it in situational questions about prioritization, iteration planning, and change management. The exam tests your ability to distinguish between product backlog and sprint backlog, and to understand how backlog refinement enables progressive elaboration in adaptive environments.

Key Points to Remember (for the exam)

• Backlog Types: Two main backlogs exist—Product backlog (complete list of desired features and changes for the product) and Sprint/Iteration backlog (subset of items selected for delivery in a specific iteration).

• Ranking Criteria: Items are ranked by business value or importance to the customer, then sized by the development team to ensure highest-value items are delivered first.

• Backlog Owner: The product owner assists in keeping the backlog up to date and manages the prioritization process.

• Backlog Refinement: This is the progressive elaboration of backlog content and reprioritization to identify work for an upcoming iteration. It involves constantly reviewing, revising, ranking, and editing the product backlog.

• Dependencies and Constraints: These must be considered when ordering backlog items, as they can impact the sequence of delivery.

• User Stories: Backlog items are often written as user stories, reflecting current project needs including product requirements.

• Dynamic Nature: The backlog is a dynamic, prioritized list that reflects current project needs and contains a reprioritized plan for remaining work.

Typical PMI Exam Example

A project manager in an adaptive software development project has a product backlog with 50 user stories. The product owner ranks them by business value, and the development team estimates effort. For the upcoming two-week iteration, the team selects the top 5 highest-value items that can be completed within the sprint. This is an example of backlog items development for an iteration.

PMI Exam Traps

• Trap: Confusing product backlog with sprint backlog

• Reality: Product backlog contains ALL desired features; sprint backlog contains ONLY items selected for a specific iteration

• Trap: Thinking backlog items are developed in order of arrival

• Reality: Items are ranked by business value, not chronological order

• Trap: Assuming the project manager prioritizes the backlog

• Reality: The product owner is responsible for keeping the backlog up to date and managing prioritization

• Trap: Believing backlog refinement happens only once

• Reality: Backlog refinement is a continuous process of reviewing, revising, and reprioritizing throughout the project

Important PMI Connections

Quick Review Questions

1. Who is responsible for keeping the product backlog up to date in adaptive approaches?

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

3. What criteria are used to rank backlog items for selection in an iteration?

4. What is the purpose of backlog refinement meetings?

5. What factors, besides business value, can impact the order of backlog items?

PMBOK v8 Reference

Section 2.4.2 - Adaptive Approaches and Backlog Management (as provided in the PMBOK v8 RAG context)