Defintion of Done

Defintion of Done image
The "definition of done" usually refers to a document representing a shared understanding of all the criteria that must be met for a product increment, like a bug fix, user story or a feature, to be considered complete and ready for release. The Scrum guide adds that the definition of done is a formal description of the state of the increment when it meets the quality measures required for the product.
Think of Done as all of the ingredients it takes for an Increment of product to be complete. The Definition of Done is the commitment by the Developers for the Increment, much like the Sprint Goal is the commitment by the Developers for the Sprint Backlog and the Product Goal is the commitment by the Product Owner for the Product Backlog. The Definition of Done includes all of the characteristics and standards an Increment needs to meet in order to be released.

The Scrum Guide says the Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. Once the Definition of Done is met, the Increment is Done and can be delivered.

The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed and what standards were met as part of the Increment. If a Product Backlog Item does not meet the Definition of Done, it cannot be released yet. Think of the Definition of Done as the standards set for the products delivered.

Sometimes the Definition of Done for an Increment includes the standards of the organization. In that case, all Scrum Teams must follow these standards as a minimum. They can elaborate on it with any other standards or characteristics that need to be met for the product. If there are not specific organizational standards, the Scrum Team must create a Definition of Done appropriate for the product.

Definition: The definition of done is a team's shared agreement on what must be true before a piece of work counts as complete. In agile teams, it usually covers development, testing and review, and can include specific activities such as completing performance testing within the sprint.

So what? If testing isn't part of done, it tends to slip to later sprints or the end of a release. Including activities like performance testing in the definition of done keeps quality work inside the sprint.

Examples: A team adding "performance tested against agreed response times" to its definition of done. A story that passes functional tests but stays open because performance testing hasn't been completed.

Explore MoT
Test Forward 2027 ยท Software Quality in the age of AI image
Tue, 19 Jan 2027
Test Forward is one afternoon at Station F with the QA and engineering people closing that gap in their own teams.
MoT Software Testing Essentials Certificate image
Boost your career in software testing with the MoT Software Testing Essentials Certificate. Learn essential skills, from basic testing techniques to advanced risk analysis, crafted by industry experts.
Into The Motaverse image
Into the MoTaverse is a podcast by Ministry of Testing, hosted by Rosie Sherry, exploring the people, insights, and systems shaping quality in modern software teams.
Subscribe to our newsletter