What is a Definition of Done?
A Definition of Done (DoD) is an agreed checklist that a piece of work must satisfy before the team calls it finished. It applies to every task, story, or feature in the same way, so "done" means the same thing for everyone. A typical DoD covers code review, tests, documentation, and a successful deploy to a target environment.
The point is to remove the gap between "it works on my machine" and "it is ready for users". Without a shared definition, one developer's done is another's half-built feature, and the difference surfaces later as bugs, rework, and missed handovers.
In plain words
Think of a Definition of Done like the checklist a pilot runs before takeoff. The plane might look ready, but it only leaves the gate once every item is ticked. The DoD is that checklist for your team's work, so nobody declares a task finished while a step is still open.
Why it matters
- Shared meaning. Everyone agrees what finished looks like, so handovers between developers, QA, and product stop breaking.
- Fewer surprises later. Tests, reviews, and docs happen as part of the work, not as a rushed afterthought before release.
- Honest progress. A task is either done or not. There is no "90 percent done" that quietly hides the hard 10 percent.
- Easier estimates. When the bar for done is stable, the team's velocity actually means something.
Common pitfalls
- Confusing it with acceptance criteria. Acceptance criteria describe what a specific feature must do. The DoD is the quality bar that applies to all work, every time.
- A list nobody checks. A DoD on a wiki page that the team ignores is decoration. Tie it to the steps you already run, ideally automated in CI.
- Making it so strict that work never ships. Start with a few items the team can hit consistently, then raise the bar as habits form.
- Never revisiting it. As tooling and standards change, review the DoD so it stays realistic and useful.
Related articles:
- What is CI/CD? - The automation that lets you enforce parts of your Definition of Done.
- What are DORA metrics? - How to measure delivery once your team agrees on what done means.
- What is technical debt? - What accumulates when "done" quietly skips the hard parts.
Want to stay one step ahead?
Don't miss our best insights. No spam, just practical analyses, invitations to exclusive events, and podcast summaries delivered straight to your inbox.