Definition of done
Also known as Done criteria, Completion policy
Definition
A definition of done is an explicit policy for the conditions a work item must satisfy before it is considered complete. It can include implementation, review, testing, documentation, security, and release requirements.
Finished means more than coded
A definition of done prevents unfinished work from being counted as complete merely because implementation ended. The policy should describe the quality and operational conditions required for the item to leave the workflow. It may differ by class of service or risk level.
A concrete example
An illustrative team considers a feature done only after review, automated checks, accessibility verification, and production release. A pull request merged into the default branch is therefore an intermediate event, not the finish point. Reporting merge as completion would overstate delivered work under this policy.
Keep it usable
Make criteria observable and review them when incidents or rework reveal a gap. Avoid a checklist so broad that every item waits for an unrelated ceremony. The policy should protect quality without making small changes carry unnecessary process.
Limitations
A definition of done cannot guarantee customer value or defect-free operation. It is a shared boundary, not proof that every risk has disappeared. Explain exceptions rather than silently weakening the rule.
How this relates to Weave
Weave can help teams examine delivery and review signals that occur around completion, but it cannot decide whether a change meets a team's definition of done. Keep the policy explicit in the delivery system and use analytics to test whether the outcome is understood and repeatable.
Explore Engineering intelligence