Scrum guide · Artifacts and practices
Scrum Artifacts: Product Backlog, Sprint Backlog and Increment
Scrum's three artifacts represent work or value. Each is designed to maximise transparency, and each has a commitment that gives focus and a way to measure progress.
Key takeaways
- Scrum has three artifacts, each with a commitment.
- Product Goal, Sprint Goal and Definition of Done give focus.
- Transparency is the purpose of every artifact.
The three artifacts and their commitments
| Artifact | Commitment | Owned by | What it is |
|---|---|---|---|
| Product Backlog | Product Goal | Product Owner | An emergent, ordered list of what is needed to improve the product |
| Sprint Backlog | Sprint Goal | Developers | The Sprint Goal, selected items and the plan to deliver them |
| Increment | Definition of Done | Scrum Team | A concrete, usable stepping stone towards the Product Goal |
Product Backlog
- The single source of work for the Scrum Team.
- Items at the top are clearer and more detailed than those lower down.
- Refinement breaks items down and adds detail, description, order and size.
- The Product Goal describes a future state of the product and is the long-term objective the team plans against.
Keeping artifacts transparent
- Make all backlogs visible to everyone who needs them.
- Keep the Product Backlog ordered, not just a pile of ideas.
- Update the Sprint Backlog daily.
- Never call work done unless it meets the Definition of Done.
Other useful (non-official) artifacts
Many teams also use burndown and burnup charts, a product roadmap, a release plan and a team working agreement. These are helpful but are not Scrum artifacts. See Scrum metrics.
Free templates for this topic
Frequently asked questions
How many Scrum artifacts are there?
Three: the Product Backlog, the Sprint Backlog and the Increment.
Is the Definition of Done a Scrum artifact?
It is the commitment attached to the Increment, not a separate artifact.
What are the three Scrum artifacts?
The Product Backlog, the Sprint Backlog and the Increment.
What are the commitments attached to the Scrum artifacts?
Each artifact has one: the Product Goal for the Product Backlog, the Sprint Goal for the Sprint Backlog and the Definition of Done for the Increment. They were introduced in the 2020 Scrum Guide.
How does the Product Goal relate to the Scrum artifacts?
It is the commitment for the Product Backlog: a future state of the product that serves as a target for the Scrum Team. The team must fulfil or abandon one Product Goal before taking on the next.
Which Scrum artifact does the Product Owner own?
The Product Backlog. The Product Owner is accountable for it, though others can contribute items. See the Product Backlog.
Which Scrum artifact do the Developers own?
The Sprint Backlog. It is their plan for the Sprint. See Sprint Backlog.
Is a burndown chart a Scrum artifact?
No. Burndown and burnup charts are popular practices but are not part of the Scrum Guide's three artifacts.
How does the Definition of Done apply to the Scrum artifacts?
It is the commitment for the Increment: a formal description of the state of the Increment when it meets the quality measures required for the product. If an organisational standard exists, the Scrum Team must follow it as a minimum.
Is a product roadmap a Scrum artifact?
No. Many Scrum teams use roadmaps to communicate direction, but the Scrum Guide does not define one.
Do multiple Scrum Teams share the same Scrum artifacts?
Teams working on the same product share one Product Backlog and one Product Goal, and they must share a Definition of Done. Each team has its own Sprint Backlog.