What is a product backlog?
A product backlog is a prioritised list of all known requirements, ideas and tasks for a product, which the product owner maintains and regularly re-prioritises.
DEFINITION
The product backlog is the central steering instrument in Scrum. It is an ordered list: at the top are the most important and best-defined requirements. Further down it becomes coarser and less detailed. The product owner is responsible for ensuring the backlog always reflects current value and priorities. The backlog is alive. It grows, shrinks and changes constantly through new knowledge, stakeholder feedback or changing requirements. In sprint planning the team selects the top entries from the backlog. A good backlog is not a wish list but a clear ranking: what creates the most value? What must be done now? What can wait? Maintaining the backlog — backlog refinement — is a continuous task of the product owner, often together with the team.
CONNECTIONS
Leadership
The product owner rarely delegates backlog maintenance entirely to the team. Good backlog prioritisation requires leadership strength: saying no to features that do not contribute to the goal, even when stakeholders demand them.
Artificial Intelligence
Large language models can generate backlog entries, cluster similar requirements and suggest priorities. This accelerates refinement and improves entry quality.
Project Management
The product backlog is the agile equivalent of the work breakdown structure: both list all tasks to be done, but differ in prioritisation logic, level of detail and mutability.
KEY POINTS
- The product backlog is the prioritised list of all requirements for a product.
- The product owner maintains and prioritises the backlog.
- Entries at the top are concrete and immediately actionable; lower down they are coarser and less urgent.
- The backlog is alive and changes with new knowledge and feedback.
- In sprint planning the team selects from the top backlog entries.
EXAMPLE
A team develops an employee app. The product backlog contains 60 entries: at the top the login function and displaying shift schedules, further down vague ideas like “gamification” and “AI recommendations”. The product owner sorts by value and urgency. In the first sprint only the three most important items are implemented. After the sprint review, new feedback from management shifts priorities. The backlog is adjusted immediately.
MISCONCEPTIONS
Is the product backlog a complete list of all tasks the team will ever complete?
No. The backlog is a living prioritisation list. It contains what is currently known but will never be complete. New items are added, old ones drop out.
Must every backlog entry be fully specified before the sprint?
No. Concrete specification is only needed for entries that will be implemented next. Further down it can remain coarser.