Product Backlog: Requirements, Features, Epics, and User Stories for Scope Definition

PMBOK v8 Definition

The product backlog is a prioritized 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. It includes requirements, features, epic user stories, and user stories, representing the overall scope and vision of the product. This artifact is usually prepared by the product owner and reflects the current project needs, containing a reprioritized plan for the remaining work.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions about agile scope management and work decomposition. You will encounter it in questions testing your understanding of how adaptive projects define, organize, and prioritize scope—particularly in scenarios asking you to identify the correct artifact for managing evolving requirements.

Key Points to Remember (for the exam)

• Primary Artifact: The product backlog is the single source of work for adaptive/agile projects, replacing the traditional scope baseline.
• Contents: Includes requirements, features, epic user stories, and user stories—representing the overall scope and vision.
• Owner: Usually prepared and managed by the product owner, who prioritizes items based on business value.
• Dynamic Nature: The backlog reflects current project needs and contains a reprioritized plan for remaining work—it is never "frozen."
• Three Types: Product backlog (overall scope), iteration backlog (subset for current iteration), and release backlog (subset for a specific release).
• WBS Equivalent: In agile projects, the WBS corresponds to the product backlog, where work items are broken down into epics and user stories.
• Prioritization Basis: Items are prioritized by the business to manage and organize work, factoring in business goals, dependencies, impediments, and resource availability.

Typical PMI Exam Example

A project team is using an adaptive approach to develop a mobile application. The product owner has created a list containing features, epic user stories, and detailed user stories that represent the full scope of the product. During sprint planning, the team selects a subset of these items to complete in the upcoming two-week iteration. What is the name of the artifact containing the full list?

Answer: Product backlog

PMI Exam Traps

• Trap: Confusing product backlog with iteration backlog

• Reality: Product backlog contains ALL known work (scope and vision); iteration backlog is only the subset selected for the current iteration.

• Trap: Thinking the product backlog is fixed once created

• Reality: The backlog is continuously reprioritized and updated as project needs change—it reflects current needs, not a frozen plan.

• Trap: Assuming user stories are the only items in a product backlog

• Reality: The product backlog includes requirements, features, epic user stories, AND user stories—multiple levels of granularity.

• Trap: Confusing release backlog with product backlog

• Reality: Release backlog is a subset of the product backlog for a specific release; product backlog covers the entire product vision.

Important PMI Connections

Quick Review Questions

1. In an adaptive project, what artifact contains requirements, features, epic user stories, and user stories representing the overall scope and vision of the product?

2. Who is typically responsible for preparing and prioritizing the product backlog?

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

4. In agile projects, what traditional scope management artifact does the product backlog correspond to?

5. What factors are considered when prioritizing items in the product backlog?

PMBOK v8 Reference

Section 2.2.2 - Adaptive Planning and Scope Definition (Product Backlog discussion) Section 5.1 - Product Vision, Roadmap, Release Planning, and Iteration Planning