Turn a vague, everyone-means-something-different idea of "done" into a shared, transparent commitment. Learn what the Definition of Done really is in Scrum, what belongs in a strong one, and how to build, enforce and strengthen it as a team.
Watch the free preview
Why "done" means something different to everyone — free to watch, no account needed.
What you'll learn
- Define the Definition of Done as the Scrum commitment for the Increment and explain the transparency it creates
- Distinguish the Definition of Done from acceptance criteria and the Definition of Ready
- Identify the quality dimensions a strong Definition of Done should cover
- Run a Definition of Done workshop that surfaces hidden, unstated quality assumptions
- Build a Team Definition of Done Canvas and a plan to strengthen it over a quarter
Syllabus
What "Done" Really Means
Why "done" means something different to everyoneFree preview
The Definition of Done as a Scrum commitment
What Goes Into a Strong Definition of Done
The dimensions of a strong Definition of Done
How a Definition of Done tightens over time
Applying It to Real IT Work
DoD versus acceptance criteria and Definition of Ready
Case study — two developers, two ideas of "tested"
Making It Stick
Building your Team Definition of Done Canvas
Traps and anti-patterns to avoid