In Scrum, the Definition of Done (DoD) is a shared understanding of what it means for a Product Backlog item to be considered complete. For example, for a Scrum team that is developing software, a Definition of Done might include things such as 'Complete code review' or 'all standard Regression scripts have passed' or even 'performance testing complete' or 'page loads in under .1 seconds'.
The benefits of a Definition of Done include:
Reduced Administrative Burden
By incorporating requirements that apply to most or all Product Backlog items—such as code reviews or regression testing—you ensure these critical steps are understood and completed without needing to spell them out repeatedly as part of every single Product Backlog item. Teams spend less time documenting routine steps and instead focus on the unique aspects of each Product Backlog item.
Increased Transparency
A clearly defined DoD ensures that everyone understands the level of work that has been done for each Product Backlog item shown at the Sprint Review. If the Definition of Done includes performance testing, for example, then any item that is shown at the Sprint Review has undergone performance testing.
Improved Consistency
Standardizing expectations through the DoD ensures consistent application of quality practices across all work.
Enhanced Collaboration
When expectations are clear, team members can collaborate more effectively, focusing on solving complex problems instead of clarifying process steps.
Who creates the Definition of Done?
Well, it depends. The short answer is the Scrum Team creates one if the organization does not already have an organization-wide Definition of Done. If there is an organization-wide Definition of Done, then the Scrum Team must adopt that as a minimum and can add additional criteria to their Definition of Done from there. For example, some organizations may have very high-level criteria in their Definition of Done, such as the requirement for all Scrum Teams to use software that is currently supported or requirements specifying what level of security checks must be performed on any new software development.
If there are several Scrum Teams working together to support a single Product, then they should share the same Definition of Done, just like they work from a single Product Backlog with a single Product Owner. The reason for this is to avoid confusion. For example, if one of the Scrum Teams conducted code reviews and the other didn't, it would be hard for the Product Owner to understand what they were looking at during the Sprint Review.
Conclusion
Your Definition of Done is more than a checklist—it’s a tool that fosters transparency, understanding, and accountability. By integrating recurring documentation requirements into your DoD, you simplify your process, allowing the team to focus on delivering value.
Smart documentation helps teams to maximize the work not done while ensuring the team and stakeholders remain aligned. A well-crafted DoD isn’t just a productivity booster—it’s a foundation for delivering high-quality increments every Sprint.
To learn more about Scrum, sign-up for Rebel Scrum's Applying Professional Scrum course or check out the Illustrated Scrum Myths book by Mary Iqbal.