Definition of Done in Agile: What It Is and How to Build One That Sticks

The definition of done (DoD) is a shared, team-wide checklist that every user story must pass before it can be considered complete. It is not optional and it does not vary by story — that is what makes it valuable.

Why the definition of done exists

Without a shared definition, "done" means different things to different people. A developer considers a story done when the code works locally. A tester considers it done when no tests break. A Product Owner considers it done when the behavior matches the acceptance criteria. A release manager considers it done when it is deployed.

The DoD replaces implicit assumptions with explicit, agreed standards. This reduces rework, prevents technical debt accumulation, and makes sprint reviews predictable.

What a good definition of done includes

Code reviewed by at least one other developer
Unit tests written and passing
No new lint errors or type errors
Feature tested against acceptance criteria by developer
QA sign-off (if team has a QA function)
Deployed to staging environment
Product Owner has accepted the story
Documentation updated if behavior changed

Start with what your team can honestly commit to. A five-item DoD that is always followed beats a twelve-item DoD that is ignored under pressure.

How to write your first definition of done

Run a short workshop in your next retrospective. Ask: "What does every story need to truly be done?" List every suggestion, then vote on which items are non-negotiable. Start with that list.

Involve the whole team. If developers write the DoD alone, QA and POs may not buy in. If the PO writes it alone, developers may find it unrealistic.

Enforcing the definition of done

The Scrum Master owns the process, not the outcomes. In sprint planning, review the DoD when stories are accepted. In the sprint review, any story that does not meet the DoD does not get demonstrated — it moves back to the backlog.

This policy feels strict at first. It becomes normal quickly, and sprint reviews become more honest.

Evolving the definition of done

The DoD should get stricter over time as the team matures. After a few sprints, add automated integration tests. Later, add performance benchmarks or accessibility checks. Revisit it every quarter in the retrospective.

Use our free definition of done generator to create a starting DoD for your team type.