Scrum uses three artifacts to track progress and ensure transparency. Each artifact has a specific commitment to ensure quality and focus.
1The Emergent Backlog
The Product Backlog is never complete. As long as a product exists, its backlog exists. It changes as the product, and the environment in which it will be used, changes.
2The Actionable Plan
The Sprint Backlog isn't static. It is updated throughout the Sprint as more is learned. It must have enough detail that the Developers can inspect their progress in the Daily Scrum.
3The Step Forward
An Increment is produced the moment a Product Backlog item meets the Definition of Done. Multiple Increments may be created within a Sprint, and they are all presented at the Sprint Review.
4Step-by-Step Breakdown
Artifacts in Scrum represent work or value. They are designed to maximize transparency of key information so that everybody has the same understanding.
The Product Backlog is the 'Source of Truth'. It's an emergent, ordered list of what is needed to improve the product. Its commitment is the Product Goal.
The Sprint Backlog is the 'Now'. It contains the Sprint Goal (Why), the set of items (What), and an actionable plan (How). Its commitment is the Sprint Goal.
The Increment is the 'Value'. It is a concrete step toward the Product Goal. Its commitment is the Definition of Done (DoD).
What is the 'Commitment' associated with the Product Backlog?
- →The Sprint Goal
- →The Product Goal
- →The Definition of Done
- →The Sprint Backlog
Which artifact is the Developers' plan for the Sprint?
- →Product Backlog
- →Increment
- →Sprint Backlog
- →Product Goal
Level Up 🚀
Advanced cheat sheets, SEO tricks, and interview prep for this topic.
Browser Support
Fully supported.
Fully supported.
Fully supported.
Fully supported.
Accessibility (A11y)
1Keep the Backlog Legible to Non-Engineers
A Product Backlog written entirely in engineering shorthand excludes stakeholders and even some Developers from understanding what 'done' means for an item. Write backlog items so a plain-language reader understands the outcome.
// Wrong backlog item
'Refactor checkout service auth middleware.'
// Right backlog item
'Fix the bug causing 1 in 20 checkouts to fail login verification.'SEO Implications
- 1
Definition-Style Queries Are High Volume
Searches like 'product backlog vs sprint backlog' or 'what is the definition of done in scrum' are extremely common, definition-style queries. Clearly distinguishing the three artifacts and their three commitments (Product Goal, Sprint Goal, Definition of Done) helps the page match these comparison searches.
Best Practices
Keep the Product Backlog Ordered, Not Just Long
An unordered pile of backlog items isn't an artifact of transparency, it's a to-do list. The order itself should communicate priority so anyone can see what's next without asking.
Update the Sprint Backlog Daily
The Sprint Backlog should reflect what's actually left to do, adjusted as the Developers learn more - not a static plan frozen at Sprint Planning.
Frequent Bugs
A Product Backlog Item is marked 'Done' even though it doesn't meet the team's Definition of Done (e.g., missing tests or documentation), which quietly erodes the meaning of an Increment.
Make the Definition of Done a visible, checked list at the point of calling something 'Done' - never let a single Developer or PM waive it silently to hit a date.
Real-World Examples
Spotting a Backlog That Isn't a Real Source of Truth
Two different documents both claim to be the roadmap: a spreadsheet the sales team references and a board the engineers use, and they've drifted out of sync.
Problem: Sales spreadsheet says feature X ships in March. Product Backlog has it unranked.
Fix: Designate the Product Backlog as the single ordered source of truth; the spreadsheet becomes a read-only export.