Product backlog
Definition
The product backlog is the single, ordered list of all work a product team might do — including features, bug fixes, technical improvements, and experiments — owned and prioritized by the Product Owner based on business value.
In Scrum, the product backlog is the primary artifact that drives what the team builds. Every piece of potential work lives here, and the Product Owner is solely responsible for its order. The top items are ready to pull into a sprint; items lower in the backlog are progressively less defined.
What goes in the product backlog:
- User stories (features told from the user's perspective)
- Bug fixes
- Technical debt and refactoring tasks
- Spike stories (research or investigation tasks)
- Infrastructure improvements
- Compliance or regulatory requirements
Key properties of a healthy backlog:
- Ordered — not just prioritized into tiers, but sequenced. Item 1 has higher value than item 2.
- Estimated — at least the top 20–30 items have size estimates.
- Visible — the entire team and relevant stakeholders can see it.
- Emergent — it changes constantly as the team learns and the market shifts.
The product backlog is never "done." As long as the product exists, new items will be discovered and added. The Product Owner's job is to keep the top of the backlog refined and ready — a task accomplished through regular backlog refinement sessions.
The product backlog is distinct from the sprint backlog. The product backlog contains everything the team might ever do. The sprint backlog contains only the items selected for the current sprint, plus the tasks needed to deliver them.
Many teams manage the product backlog in tools like Jira, Linear, or Notion. But the conversations that shape it — priority discussions, dependency mapping, user research synthesis — often happen on a whiteboard first.
Examples
- A 200-item Jira backlog where the top 15 items have story point estimates and acceptance criteria
- Product Owner reorders top ten items after a customer discovery call reveals a new pain point
- Technical debt story added after an engineer flags a scaling risk during a sprint review
- Spike story added to investigate feasibility of a new API integration before committing to the feature
- Quarterly backlog pruning session where stale items from six months ago get archived or deleted
Snap a product backlog. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.