Practice knowledge base
Definition of Done (DoD)
The Definition of Done sets common conditions for work readiness, so the team shares a consistent understanding of quality, checks, and when a task is complete.
Documentation sections
What it is
The Definition of Done, or DoD, is a concise list of conditions that must be met for a piece of work to be considered complete. The team pre-defines the necessary checks, documentation, approvals, and corrections required for a finished outcome. This practice reduces disputes over task status and helps prevent the release of work with known critical defects. It is most beneficial in environments where the team regularly delivers results to clients, users, or collaborating departments.
When it helps
- Tasks are closed inconsistently, leading to team disputes over what 'done' truly means.
- Deliverables frequently return for rework after acceptance or handover to collaborating teams.
- Critical checks are remembered late in the process, when corrections are more costly.
- The team loses pride in the product due to minor defects and unfinished loose ends.
How to start
- 1 Gather examples of recent tasks that were considered complete but later returned for rework.
- 2 Select 5-7 mandatory readiness conditions: checks, quality standards, documentation, approvals, and absence of critical defects.
- 3 Appoint an owner for DoD updates to ensure the list remains current following process changes.
- 4 Document the DoD alongside work tasks where the team actually plans and closes work.
- 5 Test one new task against the list and remove any items that do not contribute to the decision of readiness.
Expected effect
The team gains a common completion criterion, reducing time spent on repeated approvals. For management, it becomes easier to discern when work is truly complete versus when a task is formally closed but carries a risk of rework.
Common pitfalls
- The list becomes excessively long, leading the team to stop using it in daily work.
- The DoD is conflated with specific task requirements, even though some criteria should be general for the type of work.
- Readiness conditions are defined by a single manager without discussion with those who perform and accept the work.
- The team fails to update the DoD following changes in the product, tools, or quality control rules.
Further reading
- Scrum Guide, Definition of Done and Increment sections
- Book: Jeff Sutherland, Scrum: The Art of Doing Twice the Work in Half the Time
- Book: Gojko Adzic, Specification by Example
FAQ
Who should own the Definition of Done?
Typically, the process owner or team lead helps keep the list current, but the readiness conditions are agreed upon by the team in collaboration with those who accept the outcome.
Is a separate DoD required for each task?
No. The DoD describes general readiness conditions for a type of work. For a specific task, acceptance criteria can be added if the deliverable has unique requirements.
Can one start without an agile process?
Yes. The practice functions as a simple work checklist: agree on what must be checked before closing a task, and use this list during acceptance.
How can one determine if the DoD is effective?
Observe whether there are fewer reworks, disputed closures, and overlooked checks. If the list does not influence decisions, it should be simplified or clarified.