# Product Backlog

An emergent, ordered list of work that may improve a product and serves as the Scrum Team’s single source of planned work.

- Type: artifact
- Domain: Delivery & agility
- Level: Foundational
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/product-backlog/>)

## What it means

A Product Backlog is the Scrum artifact that holds an evolving, ordered view of what is needed to improve a product. It contains Product Backlog Items at different levels of detail and is ordered by the Product Owner; unlike a fixed requirements specification, it changes as the team learns.

## Why it matters

It makes product work and ordering decisions visible while allowing detail to emerge close to execution. A healthy backlog connects near-term choices to the Product Goal without pretending every future item is equally understood or committed.

## When to use it

Use it when a Scrum Team needs one transparent source of product work. Other delivery approaches may use different planning artifacts, and a backlog is unnecessary when it becomes a duplicate ticket store with no role in decisions.

## How it works

1. Anchor the backlog to a clear Product Goal and product boundary.
2. Capture candidate work as Product Backlog Items with enough context to support ordering.
3. Order items using value, risk, dependencies, learning, and other relevant evidence.
4. Refine nearer items into smaller, clearer work while leaving distant items appropriately coarse.
5. Select work during Sprint Planning and update the backlog as evidence and priorities change.

## A practical example

A payroll team keeps compliance changes, setup improvements, defects, and experiments in one Product Backlog. It orders an urgent tax-rule update first, then refines onboarding items that support the current Product Goal rather than maintaining separate competing lists.

## Where it breaks

A backlog does not supply strategy, prove value, or guarantee delivery. Excessive detail creates inventory and false certainty, while treating order as a permanent promise prevents adaptation. Large multi-team products may need careful product boundaries and coordination.

## Common mistakes

- Using the backlog as an unfiltered repository for every request.
- Treating item order as a committed release schedule.
- Refining distant work in detail before the team needs it.
- Maintaining separate stakeholder lists that compete with the Product Backlog.

## Sources

1. [The 2020 Scrum Guide](<https://scrumguides.org/scrum-guide.html>) — Scrum Guides · Official framework guide
2. [Introduction to Sprint Planning](<https://www.scrum.org/resources/introduction-sprint-planning>) — Scrum.org · Professional learning resource

## Related topics

- [Product Backlog Item](<https://wiki.soroush.uk/topic/product-backlog-item/>)
- [Backlog Refinement](<https://wiki.soroush.uk/topic/backlog-refinement/>)
- [Product Goal](<https://wiki.soroush.uk/topic/product-goal/>)
