Skip to content
PMPCAPM

Product Backlog

The Product Backlog is an emergent, ordered list of everything that might be needed in the product, serving as the single source of requirements for any changes to be made.

Share:

Explanation

The Product Backlog is a living artifact that is never complete. As the product and its environment evolve, so does the backlog. It contains features, enhancements, bug fixes, technical debt items, and anything else the team might work on. The Product Owner is responsible for its content, availability, and ordering.

Items at the top of the backlog are more refined, with clear descriptions, acceptance criteria, and estimates. Items lower in the backlog are larger and less defined. This approach, called progressive elaboration or backlog refinement, ensures the team invests detail only in items that are likely to be worked on soon.

The Product Goal is the commitment associated with the Product Backlog. It describes a future state of the product that serves as a target for the Scrum Team to plan against. The Product Backlog emerges in service of the Product Goal.

Key Points

  • Single source of truth for all work the team might do
  • Ordered by the Product Owner based on value, risk, and dependencies
  • Top items are refined with clear acceptance criteria; bottom items are less detailed
  • The Product Goal is the commitment associated with the Product Backlog

Exam Tip

The Product Backlog is never frozen or baselined. It continuously evolves. If an answer suggests locking the backlog, it is incorrect in an agile context.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Burndown Chart

A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Sprint Review

The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.

Sprint Backlog

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.

Timeboxing

Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Part of

Agile & Hybrid

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.