Skip to content
BENIBIX Learn

Definition of Done

Level 2 Β· Scrum

What makes work count as finished in Scrum. How the Definition of Done turns work into an Increment, and why half-done work never goes to the review.

Course contentsLesson 9 of 19

After this lesson you can

  • Say what an Increment is
  • Write a Definition of Done
  • Decide what happens to work that misses it

10 mincovers 2 glossary entries

Worth reading first: Sprint Review vs Retrospective

When work counts as done

The Definition of Done is the shared list of checks all work must pass to count as finished. It might say tested, reviewed by a second person and written up in the help pages. Work that passes becomes part of an Increment. Work that does not pass cannot be shown at the Sprint Review or released.

An Increment is a usable step toward the Product Goal. Each one adds to the ones before, and they all have to work together. A sprint can make more than one Increment. A team can also release one before the sprint ends. The point is that it works, not that it is finished on paper.

In the guide, the Definition of Done is the commitment of the Increment. It is what makes the word done mean the same thing to everyone. Without it, one person's done means coded, and another's means tested and live.

If the company has its own standard, every team follows it at the least. If not, the Scrum Team writes its own. When a few teams work on one product, they share one Definition of Done. That way their work fits together.

Work that misses the Definition of Done at the end of a sprint does not count. It goes back to the Product Backlog to be planned again. It is not shown at the review as nearly there, because nearly there is often weeks from done.

The list should get stricter over time. A new team might start with tested and reviewed. Later it adds runs on phones, meets the speed target and is checked for screen readers. Each line added is one less surprise after release.

The common mistake is lowering the bar at the end of a sprint to make the numbers look good. Work that was not tested but counted as done comes back as bugs. Those take longer to fix than the tests would have taken.

The Definition of Done is the gate on the way out of the sprint. Only work that passes it joins the Increment.

Worked example

Jack's 9 items become 7

Jack's team ends a sprint with 9 items coded. Their Definition of Done says tested, reviewed and running on the live test site.

Two items have not been reviewed yet. So 7 items join the Increment and are shown at the review. The other 2 go back to the Product Backlog.

The words for this lesson2

Check yourself

An item is coded but not tested, and the Definition of Done says tested. What happens at the end of the sprint?

Finished this lesson?

Marking it complete also marks its 2 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.