artifactDelivery & agility

Definition of Done

A shared quality standard that defines when an increment is complete and usable.

Download Markdown (.md)

01What it means

The Definition of Done is a formal description of the quality state an increment must reach to count as complete. It is a team or organizational standard applied consistently, unlike acceptance criteria that describe one item’s specific behavior.[1][2]

One shared quality boundary for every usable increment An increment is done only when the team's complete quality standard is satisfied
Integrated
Works with the current product increment
Verified
Required tests and reviews have passed
Usable
Delivers coherent behavior, not partial hidden work
Accessible + secure
Applicable quality and risk obligations satisfied
Operationally ready
Deployable, observable, supportable, and recoverable
Documented
Necessary product and technical knowledge updated

The Definition of Done applies across increments and is distinct from item-specific acceptance criteria or a readiness checklist.

02Why it matters

A visible completion standard prevents unfinished work from being presented as value and makes progress, quality, and tradeoffs more transparent.

03When to use it

Use it for Scrum increments and adapt the content to the product’s risks, users, and regulatory context. Do not use it to conceal unresolved product decisions or to replace item-specific criteria.

04How it works

  1. Identify product and organizational quality obligations.
  2. Agree on observable completion conditions.
  3. Apply the standard to every increment.
  4. Inspect evidence such as tests, accessibility, security, and operability.
  5. Improve the standard when learning or risk changes.

05A practical example

Example

A health app’s Definition of Done includes tested behavior, accessibility review, privacy checks, monitoring, support notes, and a deployable increment; a passing unit test alone is insufficient.

06Where it breaks

A DoD cannot prove customer value and may become bureaucratic or too weak; some release decisions remain separate from technical completion.

Common mistakes

  • Confusing it with acceptance criteria.
  • Allowing exceptions without visible risk ownership.
  • Counting partially complete work as done.

07Sources

  1. The 2020 Scrum GuideScrum Guides · Official framework guideThe 2020 Scrum Guide
  2. The Definition of DoneScrum.org · Professional framework guidanceThe Definition of Done
View saved topics

Start typing to search titles, definitions, categories, and frameworks.