A Definition of Done (DoD) is a formal description of the state a piece of work must be in to be considered complete. It sets out the quality measures and conditions that must be met before a product increment is regarded as ‘done’.
A concept I resonate in when I work with teams and DoD is often illustrated by the knowledge iceberg: much of what we know is implicit or assumed, hidden beneath the surface and likely to vary from person to person. By defining ‘done’ explicitly, we bring this implicit knowledge into the open. This clarity ensures everyone has a shared understanding of what ‘done’ means.
The DoD serves as a broad, consistent checklist that applies to all Product Backlog Items (PBIs). It differs from Acceptance Criteria (AC), which define the specific conditions for an individual feature or backlog item to be accepted. While AC is granular and tailored, the DoD is a standard, organisation- or product-wide measure of completeness and quality.
Why is it helpful for the organisation?
A clear Definition of Done:
- Creates transparency — by making expectations explicit, reducing misunderstandings, and aligning team members, stakeholders, and leadership on what ‘done’ truly means.
- Supports smoother operations — by reducing the risk of work being handed over incomplete or with hidden gaps, helping the organisation run optimally.
- Drives consistency and quality — applying the same minimum standards to every backlog item ensures reliable, predictable outcomes.
- Builds trust and confidence — stakeholders can be assured that when the team says something is ‘done,’ it has met all agreed standards, reducing surprises later.