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.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/product-backlog/
01What 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.[1][2]
02Why 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.
03When 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.
04How it works
- Anchor the backlog to a clear Product Goal and product boundary.
- Capture candidate work as Product Backlog Items with enough context to support ordering.
- Order items using value, risk, dependencies, learning, and other relevant evidence.
- Refine nearer items into smaller, clearer work while leaving distant items appropriately coarse.
- Select work during Sprint Planning and update the backlog as evidence and priorities change.
05A 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.
06Where 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.
07Sources
- The 2020 Scrum GuideScrum Guides · Official framework guideThe 2020 Scrum Guide
- Introduction to Sprint PlanningScrum.org · Professional learning resourceIntroduction to Sprint Planning