← Back to glossary

Commitments

Definition of Done

Official Commitment

A shared description of what it means for work to be complete.

Plain English explanation

The Definition of Done is the team’s shared checklist for quality and completeness. It tells everyone when work is truly finished and usable.

Why it matters

Without a clear Definition of Done, people may disagree about whether work is complete. It protects quality and makes progress transparent.

How it works

An Increment must meet the Definition of Done before it can be considered complete. If work does not meet it, it is not part of the Increment.

Example

A team’s Definition of Done might include code reviewed, tested, accessible, documented, and deployed to a test environment.

Common myths

Definition of Done is not the same as acceptance criteria. Acceptance criteria describe a specific item; Definition of Done describes the quality standard for all completed work.

Key points

  • Defines shared quality expectations
  • Applies to completed work
  • Makes progress transparent
  • Protects against unfinished work

Official source

Based on Scrum Guide 2020.

Visit official Scrum Guide