Definition of Done

Zac,scrum

As a Scrum team, having a clear Definition of Done (DoD) is critical to delivering high-quality, working software that meets stakeholders’ expectations. A DoD defines the criteria that must be met for a product backlog item to be considered complete and ready for release. Let’s look at what a Definition of Done is and why it's important.

What is a Definition of Done?

A Definition of Done is a shared understanding of what constitutes a "done" product backlog item. It outlines the minimum set of activities that must be completed before an item can be considered finished and ready for release. The DoD should include activities such as testing, documentation, code reviews, and any other activities that are necessary to ensure the quality and completeness of a product backlog item.

Why is a Definition of Done important?

Having a clear Definition of Done helps to ensure that your team is aligned on what needs to be done to complete a product backlog item. It provides a shared understanding of what constitutes "done" work, reducing the risk of misunderstandings, and missed requirements. The DoD also helps set a standard of expectations for all backlog items.

How to create a Definition of Done

Creating a Definition of Done is a collaborative effort between the entire Scrum team, including the product owner, development team, and Scrum Master. Here are some key steps to creating a DoD for your Scrum team:

By working together to create a DoD, you can help to ensure that your Scrum team is delivering high-quality, working software that meets the expectations of stakeholders. Recently our Scrum team played a game to co-create a new Definition of Done. This is a fun and interactive way to get the whole team involved in the creation process.

Link to Card Game ↗ (opens in a new tab)