May 19, 2026
6 min read
Core agile and Scrum reference
What Are Scrum Artefacts and Commitments?
A plain-English explanation of Scrum artefacts and commitments, what they are supposed to clarify, and why they matter more than memorizing the vocabulary.
Why Scrum uses artefacts and commitments
In Scrum, artefacts are the main things that make the work visible: the Product Backlog, the Sprint Backlog, and the Increment.
Each of those also has a matching commitment. The commitment gives the artefact sharper meaning, so the team is not just managing lists and tasks without a shared point.
Artefacts and commitments
Scrum artefacts and commitments matter because they make work, intent, and quality easier to see.
Artefacts
The artefacts make the work and progress visible to the team.
Product Backlog + Goal
Future direction and ordering.
Sprint Backlog + Goal
The plan and focus for the current sprint.
Increment + Done
The current state of completed usable work.
Practical clarity
The value is in clearer focus and quality standards, not in memorizing labels.
Why Scrum uses artefacts and commitments
Scrum tries to keep important things visible. If the work, the sprint plan, or the actual result stays fuzzy, teams end up talking past each other.
Artefacts exist to make those parts inspectable. Commitments exist so each artefact points toward a real intention instead of becoming passive documentation.
The three artefacts
The Product Backlog is the ordered list of possible work. The Sprint Backlog is the work the team is focusing on right now. The Increment is the usable result that exists by the end of the sprint.
Those three things are simple on purpose. They are meant to make the flow of work easier to understand, not harder.
- Product Backlog: what might come next.
- Sprint Backlog: what the team is trying to deliver in this sprint.
- Increment: what is actually finished and usable.
The matching commitments
Each Scrum artefact has a commitment attached to it so the team has a clearer reason behind the object it is looking at.
- Product Goal for the Product Backlog.
- Sprint Goal for the Sprint Backlog.
- Definition of Done for the Increment.
What the commitments are trying to prevent
Without commitments, artefacts can exist but still feel hollow. A backlog can be full of items with no real direction. A sprint backlog can be just a pile of tasks. An increment can be presented without a shared standard for what finished actually means.
The commitments are there to stop that drift.
Where teams usually get stuck
Teams often get stuck when they learn the terms but do not connect them back to decisions. That is when Scrum starts sounding more complicated than it really is.
The practical problem is usually not vocabulary. It is missing clarity around goals, scope, or completion standards.
- The Product Backlog has items but no clear direction.
- The Sprint Backlog lists work without a meaningful sprint goal.
- The Increment is shown in review, but no one agrees what done means.
Where to go next
If the Scrum terms feel clearer now and you want the practical version of how they connect, the docs hub is the best next step.
That is where the guides tie readiness, estimation, sprint planning, retrospectives, and Definition of Done back to real delivery work.
TL;DR
- Scrum has three artefacts: Product Backlog, Sprint Backlog, and Increment.
- Each artefact has a commitment: Product Goal, Sprint Goal, and Definition of Done.
- Artefacts make work visible; commitments make that visibility meaningful.
- These artefacts matter when they make work and intent clearer, not when teams memorize the vocabulary around them.