Definition of done — the team's quality standard captured in a living checklist.
A definition of done built collaboratively on a whiteboard is owned by the team — not handed down by the Scrum Master. BoardSnap captures the team's quality standard in a shareable checklist the moment they create it.
Why scrum masters love this workflow
The definition of done is the Scrum team's quality standard — the shared understanding of what 'done' actually means. When it's built by the team on a whiteboard, through genuine debate about what quality looks like for their work, it sticks. When it's handed down as a template, it gets ignored.
BoardSnap captures the team-built DoD in a structured checklist. Snap the DoD whiteboard and get a categorized checklist: code quality items, testing requirements, documentation expectations, deployment requirements. That checklist goes into the team room, the sprint planning template, and every story card. It's the team's quality commitment — visible and searchable.
The exact flow
- Facilitate the DoD session through team discussion
Ask: 'What does it mean for this type of work to be truly done?' Let the team generate the criteria. Write each criterion on the board as it's proposed.
- Categorize the criteria on the board
Group criteria into categories: Code Quality, Testing, Documentation, Deployment, Review. Categories make the DoD navigable and complete.
- Debate and refine each criterion
Vague criteria ('properly tested') get refined until they're specific ('unit test coverage above 80%, integration tests for each acceptance criterion'). Specificity is what makes the DoD usable.
- Vote on the final DoD
Every team member confirms agreement with the DoD before it's final. The team's physical vote — hand raise or written name on the board — creates commitment.
- Snap and post everywhere
The BoardSnap summary is the DoD checklist. Post it in the team room, add it to your sprint planning template, and reference it at every sprint review.
What you'll get out of it
- Team-built DoD with specific, behavioral criteria — not a generic template
- Categories make the DoD navigable for different types of work
- Team commitment captured with their written names on the board
- DoD evolution tracked as the team matures and raises their quality standard
- Ready to post the same day the session happens
Frequently asked
How often should the definition of done be revised?
Revisit the DoD when the team's quality standard should evolve — typically every three to six months, or when the team identifies a quality issue that the current DoD doesn't prevent. Use a retrospective to surface DoD gaps.
Should the DoD be the same for all story types?
A core DoD applies to all stories. Some teams add a supplemental DoD for specific story types — API changes, UI work, data migrations. Keep the core DoD short and focused on universals.
Can BoardSnap help me track DoD compliance across sprints?
Not automatically. Use the DoD checklist in your sprint review to assess compliance. When a story is marked done without meeting the DoD, note it in the retro board — it's an impediment to the team's quality standard.
Scrum Masters: try this on your next definition of done.
Three taps. Action items in your hand before the room clears.