Definition of Done

The shared quality bar every piece of work must meet before anyone can call it done.

2 min read · Beginner

In 30 seconds

One checklist that applies to every item the team delivers.
Work that doesn't meet it isn't done and isn't shown as done.
It's the commitment attached to the Increment.

Try it

Our Definition of Done

An example

Code reviewed by at least one other developer
Automated tests written and passing
Merged to main and deployed to a test environment
No known critical bugs
User-facing help updated if needed

Yours will differ; it should reflect what "releasable" means for your product.

Done vs acceptance criteria

Acceptance criteria are specific to one story. The Definition of Done applies to all of them. A story is complete only when it meets both.

Raising the bar over time

Teams often start with a modest definition and add items as their automation and skills improve. The Sprint Retrospective is the natural place to agree a stronger one. A weak definition is a major source of technical debt.

Myth vs reality

Myth · Done means the developer is finished.

Reality · Done means releasable, including review and testing.

Myth · Each story can have its own definition.

Reality · That's acceptance criteria; the Definition of Done is shared.

Myth · It's set once and never changes.

Reality · It should grow stricter as the team matures.

The AI angle

Add explicit items for AI-generated work: reviewed and understood by a human, tests checked against the spec, and no sensitive data shared outside policy.

AI and the Definition of Done →

FAQ

Who creates the Definition of Done?

The Scrum team, or the organization if it has a standard all teams must meet.

What if several teams work on one product?

They share one Definition of Done for that product.

Where should it be kept?

Somewhere visible, like the team board or wiki front page.