What is the Definition of Done in Scrum?

The Definition of Done (DoD) is a formal description of the state a Product Backlog item must reach before it can be included in the Increment. It's created by the Scrum Team and represents the minimum quality standard for all work. If an item doesn't meet the DoD, it's not Done — it goes back to the backlog.

Who creates the Definition of Done?

The Scrum Team creates it collaboratively. If the organization has existing engineering standards, the DoD must include at least those. The Scrum Team can make their DoD stricter than the organizational baseline, but never looser.

What should be in a Definition of Done?

Typical DoD items: code reviewed by at least one peer, unit tests written and passing, acceptance criteria met, deployed to staging/test environment, no new known bugs introduced, documentation updated. The specific items depend on your product, team, and tech stack.

What's the difference between Definition of Done and acceptance criteria?

Acceptance criteria are specific to one backlog item — they define what that particular feature must do to be considered complete. The Definition of Done applies to every item and defines the quality standard that all items must meet before they can be considered Done.

Can the Definition of Done change over time?

Yes — and it should. As the team matures and the product grows, the DoD often becomes stricter. Adding automated tests, performance benchmarks, or accessibility checks to the DoD over time is a sign of improving quality standards.

Quality7 min read

What is Definition of Done in Scrum?

Definition of Done is the answer to 'who gets to say it's finished?' If the answer varies between team members, you don't have a DoD — you have a gap that will surface at the worst possible moment, usually in a Sprint Review when something half-finished is presented as complete.

Definition of Done — definition

The Definition of Done is a formal, shared agreement that describes what state a backlog item must be in before it can be considered truly complete and included in the Increment. It applies equally to every item, every sprint. It's not a checklist that varies by developer or item type — it's the team's minimum quality bar, written down and respected by all.

Example Definition of Done

There's no universal DoD — it depends on your product, tech stack, and team maturity. This is a reasonable starting point for a software team:

✓Code reviewed by at least one team member

✓Unit tests written and all passing

✓Acceptance criteria met and verified

✓No new bugs introduced (regression check passed)

✓Deployed to staging environment

✓Product Owner has accepted the item

✓Documentation updated if user-facing behavior changed

Note: this is an example. Your DoD should reflect your team's actual quality standards — not a template.

Definition of Done vs Acceptance Criteria

Aspect

Definition of Done

Acceptance Criteria

Scope

Every backlog item

One specific item

Created by

The Scrum Team

Product Owner (with team)

Changes when?

Evolves over time

Per item, before sprint

Answers

'Did we meet quality standards?'

'Does this item do what was asked?'

Frequently asked questions

What happens when an item doesn't meet the Definition of Done?

It doesn't become part of the Increment. The work returns to the Product Backlog, where the Product Owner re-evaluates its priority. It shouldn't be presented in Sprint Review as Done — that's misleading to stakeholders.

Should the Definition of Done be public?

Yes. The DoD should be visible to the whole organization — stakeholders, management, and the Scrum Team. Transparency about quality standards reduces surprises and misaligned expectations.

Test your Scrum knowledge

The Scrum Quiz includes questions on DoD, acceptance criteria, and Increment quality.

Take Scrum Quiz →