Definition of Done: Your quality compass for every delivery

In Scrum, everything revolves around delivering value in short, manageable steps. But how do you prevent accumulating pieces of 'almost-done' work that are ultimately unusable? That's precisely why the Definition of Done (DoD) was introduced. The DoD is a set of criteria that clearly define when a backlog item is truly finished, ensuring your Increment always meets the desired quality standards.

‍

What is the Definition of Done?

The Definition of Done is an explicit list of conditions that a completed item must minimally meet. These conditions can be technical in nature—think code quality, test requirements, or documentation—but can also include functional aspects and UX. The goal is to prevent ambiguity about the word ‘done’: if something doesn't meet all criteria, it's not yet finished.

‍

Why is it important?

A clearly defined Definition of Done prevents you from unconsciously accumulating technical debt or demonstrating 'half-finished' work to stakeholders. It ensures that your Increment is truly usable during the Sprint Review and no longer requires unexpected adjustments. This enhances the reliability of your work process, both for the team and for stakeholders.

‍

How do you create a Definition of Done?

At Spark Academy, we recommend creating the Definition of Done as a team and reviewing it regularly. You can start by:

1. Brainstorm: Have all team members write down what they consider essential for something to be called 'done'. Think of testing, peer review, documentation, and performance checks.
2. Cluster and prioritize: Group the most relevant criteria and determine which are crucial for each release.
3. Make it concrete: Keep the criteria specific and measurable. 'Code must be clean' is vague, whereas 'Peer review by a colleague and no critical warnings in the pipeline' is very clear.
4. Monitor and evaluate: Regularly evaluate the Definition of Done. As the team matures or adopts new technology, new criteria may be added.

‍

Role of the Development Team

The Development Team is largely responsible for establishing and adhering to the Definition of Done, as they are the ones performing the work. The Product Owner can contribute ideas regarding acceptance criteria, but the technical and process-related requirements are primarily determined by the Development Team. The Scrum Master facilitates the process, helps the team not to underestimate or forget the DoD, and emphasizes its importance during the Retrospective.

‍

With a clear Definition of Done, every team member knows exactly what is needed to truly complete work. This creates clarity, improves the quality of the Increment, and prevents surprises during the Sprint Review. Establishing and maintaining the DoD is a collaborative effort, with the entire team continuously raising the bar for quality.

‍