Backlog
An ordered list of everything needed in a product.
Detailed Explanation
The backlog is a prioritized list of features, enhancements, bug fixes, and technical work. In Scrum, the Product Backlog is owned by the Product Owner and serves as the single source of truth for what the team will work on.
Items at the top are refined and sprint-ready, while lower items may be less defined. This progressive refinement is known as backlog grooming. The backlog is a living document that evolves as the team learns more about the product and its users.
A well-maintained backlog is crucial for effective sprint planning. Without it, teams waste time debating priorities. It also provides transparency to stakeholders about upcoming work and the trade-offs being made.
Key Points
- Owned and prioritized by the Product Owner
- Items ordered by business value, risk, and priority
- Top items are refined and ready for sprint planning
- Continuously evolving — never considered 'complete'
- Includes user stories, bugs, technical debt, and spikes
- Regular refinement sessions keep it healthy
Practical Example
A SaaS company maintains a product backlog with 150 items. The Product Owner ranks 'Add SSO authentication' at the top because enterprise clients demand it. During weekly refinement, the team breaks the SSO story into smaller items and estimates each at 5, 8, and 3 story points respectively.
Tips for Learning and Applying
Refine the backlog weekly — do not let it become a graveyard of old ideas
Use story points or T-shirt sizing for consistent estimation
Keep the top 2-3 sprints worth of items well-refined
Archive items untouched for more than 3 months
Want to Master These Concepts?
Our courses cover all these terms in depth with practical examples and exercises.