Scrum Artifacts: Product Backlog
You'll learn what the product backlog is and how it serves as Scrum's single source of truth for planned work.
What Is the Product Backlog?
The product backlog is an ordered list of everything that might be needed in the product—features, enhancements, bug fixes, technical improvements, and more. Think of it as a dynamic wish list that represents all known work for the product, ranked by priority.
Unlike a fixed requirements document, the product backlog is a living artifact: it evolves continuously as the team learns more about user needs, market conditions, and technical constraints.
Key Characteristics
Ownership: The Product Owner maintains and prioritizes the backlog. They decide what goes in, what comes out, and—critically—what order items appear in.
Ordering: Items at the top are more refined, detailed, and urgent. Lower items can remain vague until they move up in priority. The team typically works on top items first during sprints.
Evolution: The backlog never stops changing. New insights, feedback from working software, and changing business goals all shape it. Items get added, removed, re-prioritized, split, or merged regularly.
Transparency: Everyone on the Scrum team and stakeholders can see the backlog. This visibility enables shared understanding of what's planned and why.
Analogy
Imagine a restaurant kitchen's order queue. Orders near the front are fully specified ("medium-rare steak, no salt"), while future orders might just say "dinner special." The chef (Product Owner) keeps reordering based on table priority, ingredient availability, and customer feedback.
Key Takeaway: The product backlog is the Product Owner's prioritized, evolving list of all planned work—the single source of truth for what the team might build next.