Understanding and Applying the Scrum Framework · Topic 5 of 5
Artifacts, Commitments and the Definition of Done
The three Scrum artifacts and their commitments: Product Backlog and Product Goal, Sprint Backlog and Sprint Goal, Increment and the Definition of Done.
- 4 min
- Includes a diagram
- Product Backlog: Product Goal. Sprint Backlog: Sprint Goal. Increment: Definition of Done.
- One Product Goal at a time; fulfil or abandon before the next.
- Refinement is ongoing; Developers size items.
What it is
Scrum's artifacts represent work or value. They are designed to maximize transparency of key information. Each artifact contains a commitment that ensures it provides information that enhances transparency and focus against which progress can be measured.
How it works
The three artifacts and their commitments
| Artifact | What it is | Commitment |
|---|---|---|
| Product Backlog | An emergent, ordered list of what is needed to improve the product; the single source of work undertaken by the Scrum Team | Product Goal: a future state of the product, the long-term objective for the Scrum Team |
| Sprint Backlog | The Sprint Goal (why), the selected Product Backlog items (what) and an actionable plan (how); a plan by and for the Developers | Sprint Goal: the single objective for the Sprint |
| Increment | A concrete stepping stone toward the Product Goal | Definition of Done |
Product Backlog and Product Goal
- The Product Goal is in the Product Backlog; the rest of the Product Backlog emerges to define what will fulfil it.
- The Scrum Team must fulfil (or abandon) one Product Goal before taking on the next.
- Product Backlog refinement is the ongoing act of breaking down and further defining items into smaller, more precise items. The Developers who will be doing the work are responsible for the sizing; the Product Owner may influence them by helping them understand and select trade-offs.
- Items that can be Done within one Sprint are deemed ready for selection at Sprint Planning.
Sprint Backlog and Sprint Goal
- The Sprint Backlog is a highly visible, real-time picture of the work the Developers plan to accomplish, updated throughout the Sprint as more is learned.
- The Sprint Goal creates coherence and focus, and gives flexibility on the exact work needed to achieve it.
- If the work turns out to be different than expected, the Developers collaborate with the Product Owner to negotiate the scope of the Sprint Backlog without affecting the Sprint Goal.
Increment
- Each Increment is additive to all prior Increments and thoroughly verified, ensuring they work together.
- It must be usable. Multiple Increments may be created within a Sprint.
- The sum of the Increments is presented at the Sprint Review, but an Increment may be delivered to stakeholders before the end of the Sprint.
- Work cannot be considered part of an Increment unless it meets the Definition of Done.
The Definition of Done
- A formal description of the state of the Increment when it meets the quality measures required for the product.
- When an item meets the Definition of Done, an Increment is born.
- If an item does not meet it, it cannot be released or even presented at the Sprint Review; it returns to the Product Backlog for future consideration.
- If the organization has a Definition of Done as a standard, all Scrum Teams must follow it as a minimum; otherwise the Scrum Team must create one appropriate for the product.
- Multiple Scrum Teams working on the same product must mutually define and comply with the same Definition of Done.
Unfinished items at the end of a Sprint do not roll over automatically. They go back to the Product Backlog, where the Product Owner orders them.
How the exam asks about this
- "What is the commitment for the Increment?" The Definition of Done.
- "Who sizes Product Backlog items?" The Developers who will do the work.
- "An item is not Done at the end of the Sprint. What happens?" It returns to the Product Backlog.
What to remember for the exam
- Product Backlog: Product Goal. Sprint Backlog: Sprint Goal. Increment: Definition of Done.
- One Product Goal at a time; fulfil or abandon before the next.
- Refinement is ongoing; Developers size items.
- An Increment must be usable and may be released before the Sprint ends.
- Work that is not Done is not part of an Increment and cannot be shown at the Sprint Review.
Lowering the Definition of Done to finish more items reduces quality, which breaks the Scrum Guide rule that quality does not decrease during the Sprint.
Common mistakes
Calling the Sprint Backlog the Product Owner's plan. It is by and for the Developers.
Presenting undone work at the Sprint Review. It must meet the Definition of Done.
Thinking only one Increment can exist per Sprint. Several can be created.
Check yourself
What is the commitment for the Product Backlog?
The Product Goal.
What happens to a Product Backlog item that does not meet the Definition of Done at the end of the Sprint?
It cannot be released or presented at the Sprint Review; it returns to the Product Backlog.
When several Scrum Teams work on the same product, what must they share about Done?
They must mutually define and comply with the same Definition of Done.
Topic 5 of 5 in Understanding and Applying the Scrum Framework
Test yourself on Understanding and Applying the Scrum Framework
The full Scrum.org PSM I question bank has 811 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Scrum.org. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.