In Scrum, the Definition of Done (DoD) plays a critical role in ensuring quality and transparency. But who defines this important concept? And what does it even mean? Let’s break it down.
What is a Definition of Done?
A Definition of Done is a shared understanding among the Scrum team of what constitutes a finished Product Backlog item. It defines the criteria that must be met for any work to be considered complete. Think of it as a quality checklist for every item on the Product Backlog, ensuring that everyone knows what "done" really means.
Why Do We Need a Definition of Done?
Imagine two Scrum teams at the Scrum Cookie Company. Sheila and Bob are the Scrum Masters for their respective teams. Both teams work together to fulfill cookie orders from the Product Backlog. Sample items from the Product Backlog include delivering 200 cookies for a wedding and 300 sugar cookies for a family reunion.
However, there’s a problem: tension is brewing at the Scrum Cookie Company. Bob’s team follows a rigorous process. They ensure that each batch of cookies is baked according to the recipe, cooked for the right amount of time, boxed up, priced, and, finally, they clean the kitchen before considering each Product Backlog item done. Sheila’s team, however, doesn’t clean up the kitchen after baking.
This inconsistency causes confusion and frustration. To solve this, the Scrum Cookie Company introduces an organizational Definition of Done: once the cookies are baked, the kitchen must be cleaned before the Product Backlog item can be closed.
Sheila and Bob meet to discuss this new standard, and while they adopt the organizational DoD, they also agree that their teams will box and price every batch of cookies before closing their respective Product Backlog items. They add this to the Definition of Done for their Product.
This example shows how a Definition of Done sets a common understanding of the work needed to complete each Product Backlog item. It also demonstrates the importance of alignment across teams.
Who Creates the Definition of Done?
1. The Organization: If there is an existing organizational Definition of Done, all Scrum teams within that organization must adopt it as a minimum standard. In our Scrum Cookie Company example, the organization decided that every team must clean the kitchen after baking cookies. This sets a baseline for what "done" means across all teams.
2. The Scrum Team: Each Scrum team has the autonomy to refine and expand upon the organizational Definition of Done. However, they cannot remove any criteria set by the organization. For example, Sheila and Bob’s teams added additional steps to box and price the cookies before considering the work done.
3. Collaboration Among Teams: When multiple Scrum teams work together on the same product, they must share the same Definition of Done to ensure consistency. This avoids situations where one team’s work isn’t up to the same standards as another's, leading to potential problems down the line.
Benefits of a Definition of Done
- Instills Quality: By adhering to the Definition of Done, teams ensure that they consistently deliver high-quality increments.
- Increases Transparency: A clear DoD provides visibility for both the Scrum team and stakeholders, ensuring everyone understands when a Product Backlog item is genuinely complete.
- Improves Planning: With a shared understanding of what "done" means, teams can better plan their work and avoid misunderstandings or incomplete deliveries.
In short, a Definition of Done is essential for any Scrum team, providing clear guidelines that enhance quality, transparency, and collaboration. It is defined by the organization at the highest level, with each Scrum team able to refine it further to meet their specific needs—ensuring that work is truly "done" and ready to deliver value.
To learn more about Scrum and what it's like to be on a Scrum team, signup for Rebel Scrum's Applying Professional Scrum course.
Are you excited about Scrum? Join us at this year's Scrum Day conference in Madison, Wisconsin. Scrum Day 2024 is all about Delivering Products With Value—it’s not about ticket counts, it’s about making sure you’re delivering the right things.
Comments