Product User Stories: Backlog Types and Prioritization 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. The types of backlogs commonly used in adaptive and agile projects include the product backlog, iteration backlog, and release backlog.

Why It Matters for the Exam

The concept of product user stories and backlogs appears frequently in PMI exam questions related to adaptive/agile project management and scope management. Questions typically test your ability to distinguish between backlog types, understand their ownership, and recognize how user stories are prioritized and refined throughout the project life cycle.

Key Points to Remember (for the exam)

• Product Backlog: Usually prepared by the product owner; includes requirements, features, epic user stories, and user stories representing the overall scope and vision of the product.
• Iteration Backlog: A subset of the product backlog containing selected user stories and required tasks to complete committed work during the current iteration.
• Release Backlog: A subset of the product backlog including items planned for a specific release; helps organize work to be delivered at the end of a release cycle, which may encompass multiple sprints or iterations.
• WBS Correspondence: In agile projects, the WBS corresponds to the product backlog, where work items can be broken down into epics and user stories.
• Prioritization: The business prioritizes the backlog to manage and organize the adaptive or agile project’s work.
• Dynamic Nature: The backlog is continuously reprioritized and reflects current project needs throughout the project life cycle.
• Common Format: User stories are the standard format for writing backlog items in adaptive projects.

Typical PMI Exam Example

A project manager is working on an adaptive software development project. The product owner has created a prioritized list of features, epic user stories, and user stories that represent the overall vision of the product. During the current sprint, the team selects a subset of these items to complete. Which type of backlog contains the items selected for this specific iteration?

Answer: Iteration backlog

PMI Exam Traps

• Trap: Confusing the product backlog with the iteration backlog

  • Reality: The product backlog contains ALL known work (overall scope and vision); the iteration backlog is only the subset selected for one iteration.

• Trap: Thinking the project manager owns the product backlog

  • Reality: The product owner is responsible for preparing and maintaining the product backlog.

• Trap: Assuming the backlog is static once created

  • Reality: The backlog is continuously reprioritized and reflects current project needs; it contains a reprioritized plan for remaining work.

• Trap: Confusing the release backlog with the iteration backlog

  • Reality: The release backlog covers multiple sprints/iterations for a specific release; the iteration backlog covers only one iteration.

Important PMI Connections

Quick Review Questions

1. In an adaptive project, who is usually responsible for preparing the product backlog?

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

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

4. What types of items are typically included in a product backlog?

5. A release backlog encompasses work for how many sprints or iterations?

PMBOK v8 Reference

Section 2.2.2 - Scope Performance Domain (Backlog definition and types) Section 2.2.3 - Adaptive and Hybrid Approaches (Backlog in different project environments)

This article is based exclusively on PMBOK v8 content as provided in the RAG context.