Definition of Done

What is the definition of done?

The "definition of done" refers to an agreed-upon list of criteria that must be met before a user story or project can be considered done.

One of the biggest challenges to completing a project is lacking a clear, unanimous idea for when it's done. Agreeing on the answers to common questions that come up in project management, like "Is it ready for testing?", "Is it ready for launch?", and "Can we start selling it?" make it critical to have a definition for doneness that the whole team can agree on.

Creating your definition of done

An invaluable resource for creating (and using) your definition of done is a reference list. Your company may have its own version of this, but it will generally include items or criteria that various teams expect to be completed before a release or product is “ready” for users.

Keep in mind that some of the items on the reference list may have their own definition of done or acceptance criteria. One example of this is when your reference list includes a formal review by stakeholders. When something like this happens, you’ll have to incorporate their standards into your own.

Here is a quick 3-step guide to defining your definition of done:

1. Identify which teams have work that needs to be completed on the project
2. Determine which major activities or tasks those teams need to complete 
3. Review with your team to ensure there is agreement on the definition of done

Who owns the definition of done?

The definition of done can be the responsibility of a scrum master or an engineering leader (an engineering manager, for example). As a majority of the requirements are technical in nature, these roles tend to have more stakes in the game. It's important to note though that it is a team effort, so including product, quality, engineering, and project management is ideal for collaborating, creating, and accepting a definition of done.

Definition of done vs. acceptance criteria

Acceptance criteria are typically associated with the non-functional requirements (NFRs) that a definition of done houses. Another key difference is that definition of done applies generically to a release, whereas acceptance criteria relate directly to a user story. 

For product teams, it's a good idea to get involved in the conversation around definition of done. conversation. Make sure the acceptance criteria as a whole are met ensures your product meets your users' expectations and will be readily accepted by customers.