Product Backlog
An emergent, ordered list of everything known to be needed in the product, owned and ordered by the Product Owner.
What it means
The Product Backlog is the single source of work for the Scrum Team. It is never complete; it evolves as the product and its environment evolve, capturing requirements, fixes, and improvements as backlog items.
Each item can carry a description, order, estimate, and value. Higher-ordered items are usually clearer and more detailed than lower-ordered ones, a practice sometimes called progressive refinement.
Common mistakes
The Product Goal lives as a commitment attached to the Product Backlog, giving it a long-term objective beyond any single Sprint. Refinement is the ongoing activity of adding detail, estimates, and order to backlog items.
Example
A Product Owner keeps 40 items in the Product Backlog, with the top eight refined and ready for the next Sprint Planning session.
Example: ordering items by value, risk and learning
The Product Owner decides the order of the Product Backlog. Value is usually central, but risk and learning can justify moving an item up. Consider four items for a new booking app.
- Card payment at checkout. High value and needed before launch, so it sits near the top.
- Integration with a partner calendar API the team has never used. Moderate value but high technical risk, so a small slice moves up early to expose problems while there is time to react.
- Test two onboarding flows with ten real users. Low build effort and high learning, placed early because the result may change what the team builds next.
- Dark mode. Requested by some users but low value right now, so it stays lower and may be refined later.
An emergent artifact
The Scrum Guide describes the Product Backlog as emergent. It is never complete at the start. After each Sprint Review, after user feedback or after a market change, items are added, split, reordered or removed.
In the example above, if the onboarding test shows users abandon the flow, the Product Owner might add items to fix it and move dark mode further down. That change is the backlog doing its job, not a failure of planning.
Product Backlog versus Sprint Backlog
The Product Backlog covers the whole product and is owned by the Product Owner. The Sprint Backlog covers one Sprint. It holds the Sprint Goal, the Product Backlog items selected for the Sprint and the Developers' plan for delivering them. The Developers own the Sprint Backlog and update it throughout the Sprint.
