What is it?
The Definition of Done (DoD) is a short, verifiable list of conditions a backlog item must meet before it counts as delivered. In Scrum, the Definition of Done describes the quality the increment must meet. We use those quality agreements for the delivery of backlog items as well.
Two layers
- General, for every backlog item. Tested, reviewed by a second person, checked against security and compliance, documented, deployed to production and transferable.
- Specific to each backlog item. What this backlog item must be able to do. In Scrum these are called acceptance criteria.
Why it matters
With a fixed price, the Definition of Done is the yardstick for delivery. We know what we have to deliver, you know what you get. Without a Definition of Done, "done" is an opinion.
Example
An integration between accounting and CRM:
- General: tested, errors are logged, there is operations documentation.
- Specific: new customers appear in both systems within five minutes, and duplicate customers are reported.
Per type of agreement
- Blue, fixed price: the Definition of Done is fully fixed in advance.
- Green, fixed budget: the business judges whether the result is usable.
- Yellow, timebox: done is the end of the timebox, with an analysis, prototype or advice.
What to watch out for
- Make every condition verifiable: "fast" is not a criterion, "within 2 seconds" is.
- Keep the list short.
- Do not adjust the general list per backlog item.
Would you like advice on the Definition of Done? Request a free advice conversation.
Updated on