Quality and requirements
What is the Definition of Done? Definition and examples
Also: DoD
In short
The Definition of Done is a shared checklist every piece of a team's work must meet before it counts as finished. It applies equally to all tasks, for example reviewed, tested and documented. Acceptance criteria, by contrast, apply to a single task only.
Why it matters: The Definition of Done turns “done” into a promise everyone can rely on.
Definition of Done
Applies to every task of the team
Acceptance criteria
Apply to one single task
Why does Definition of Done matter for your company?
Without a shared definition, “done” means “code written” to engineering, “tested” to QA and “at the customer” to sales. That gap creates rework and false commitments. A Definition of Done closes it with a short, binding list.
When AI agents work alongside the team, the same list applies to them. An agent readily reports “done” as soon as its part runs. With a Definition of Done you check work by people and agents against the same rules.
Example: Done, but not with the customer
A team reports a new export feature as done in the leadership meeting. Sales promises it to two customers. Then it turns out: it is not documented, not approved and not yet shipped.
The team agrees on a Definition of Done: reviewed, documented, shipped. From then on “done” means the same to everyone, and commitments to customers rest on the real state.
3 common mistakes to avoid
Lists that are too long
Nobody reads a Definition of Done with twenty items. Keep it short and drop what is never checked.
Confusing it with acceptance criteria
Acceptance criteria describe what one specific task must achieve. The Definition of Done applies to every task.
Making exceptions the rule
Skipping items under time pressure only pushes the work back. Exceptions need a deliberate decision.
Step by step
- 1
Agree on it together
Engineering, QA and product agree on a few items.
- 2
Keep it short
Only what applies to every task and can be checked.
- 3
Make it visible
The list sits where the work happens, for example in every task template.
- 4
Review it regularly
Does the list still fit? Add what is missing and drop what nobody needs.
Read on in the PM Lab
Articles that go deeper.
Related terms
- Acceptance criteria →Acceptance criteria are testable conditions a piece of work must meet to count as done.
- Requirement →A requirement describes what a product or system must do and why, from the point of view of those who use it.
- Human in the Loop →Human in the loop means a person reviews and approves an AI process at defined points before it continues.