Creating a Definition of Done: How do you truly know when work is finished?

What exactly is a Definition of Done?

The Definition of Done (DoD) is a set of criteria that determines when an item (for example, a user story or task) is truly 'done'. This goes much further than 'it works': it can also include quality, documentation, testing, and any design or security checks. This prevents ambiguity and discussion at the end of the sprint. In principle, a DoD should be specific to each product or team type and be regularly evaluated.

‍

Good examples of Definition of Done

• Software development: All unit tests passed, functional tests completed, code reviewed by at least one colleague, no critical bugs open, release notes updated.
• Marketing campaign: Content checked for spelling and tone of voice, legal review conducted, landing page live, measurable KPIs set.
• Physical product: Prototype meets all safety standards, basic testing by end-users completed, manual or instructions available, feedback processed.

‍

Common problems with an unclear DoD

• Half-finished work: Items appear complete, but lack documentation, test coverage, or stakeholder feedback.
• Unexpected delays: At the end of the sprint, you discover that additional work still needs to be done.
• Lack of agreement: If the team doesn't have a shared DoD, discussions arise about whether something is truly done.

‍

How do you create a clear DoD with your team?

1. Brainstorm: Have each team member write down what they consider crucial to call work 'done' (e.g., testing, review, acceptance criteria, etc.).
2. Group and prioritize: See which points are duplicates or overlap, and determine what is truly minimally required.
3. Make it specific: “The code must be clean” is vague. “Peer review by at least one colleague, no critical warnings in the pipeline” is clear.
4. Monitor and evaluate: Check each sprint whether the Definition of Done is still up-to-date, and adjust where necessary.

‍

How do you ensure that the team truly uses the DoD?

• Make it visual: Display the DoD prominently (or put it in your digital scrum board).
• Integrate into your process: Discuss the DoD during every user story refinement and refer to it during the review.
• Involve everyone: The Product Owner also needs to know what the DoD entails to avoid surprises.
• Test it in practice: Have each team member check if the item meets the DoD before it moves to ‘Done’.

‍

Conclusion

A clear Definition of Done helps your team confidently say: “This item is truly done.” By collaboratively defining criteria, preventing conflicts or misunderstandings, and regularly evaluating, the DoD becomes a powerful tool. Not only does it ensure your Increment meets the right quality standards, but it also prevents unpleasant surprises at the end of the sprint.

‍