Definition of Done

The Definition of Done (DoD) is a formal description containing an agreed-upon set of criteria that a product increment must satisfy to be considered complete. It ensures that all work meets a consistent quality standard before it’s delivered. According to the Scrum Guide, “the moment a Product Backlog item meets the Definition of Done, an Increment is born.”

Why it’s important:

• Clarity: The DoD provides a clear, shared understanding of what it means for work to be “done,” which eliminates confusion within the team and with stakeholders.
• Quality Assurance: It ensures that all necessary work (such as testing, documentation, and code review) has been completed to guarantee the increment is ready for use.
• Transparency and alignment: The DoD creates transparency and alignment across the team, as everyone understands the quality expectations and what it takes to get a Product Backlog Item across the finish line.
• Continuous Delivery: In Scrum, “only an Increment that meets the Definition of Done can be released.” This makes the DoD crucial for maintaining the regular delivery of working software.

Example Criteria in a Definition of Done:

• Code has been written and reviewed.
• All tests (unit, integration, acceptance) have passed.
• Documentation has been updated.
• Deployment steps are complete or prepared.

The Scrum Guide also emphasizes that “if a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review.” This ensures that no incomplete work gets prematurely integrated, maintaining high standards and avoiding technical debt.
The Definition of Done is a commitment to the Product Increment.

The Scrum Guide also highlights what a team should consider its minimum standard in larger organizations and what happens if multiple teams work on the same product.

“If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.”

“The Developers are required to conform to the Definition of Done. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done.”