Definition of Done at Scale

Definition

A Definition of Done is a shared agreement within a Scrum team about what "done" means for a work item—ensuring that everyone understands when work is truly complete. It consists of policies (how to test and validate) and checklists (required tasks reflecting organizational standards), and it varies by team context and maturity level.

In the Book

The Scrum Guide requires that when a Product Backlog item is described as "Done," everyone must understand what that means. The book shows this takes two forms: validation policies (e.g., "all defects found when testing a story must be fixed immediately," "acceptance tests must be satisfied") and task checklists (e.g., "code is checked in to repository," "build is successful," "code has been reviewed," "unit tests developed").

Critically, the Definition of Done is not static. Teams with little Scrum experience start with relatively simple definitions, then as they gain maturity and add automation, they evolve toward more sophisticated definitions that include Definition of Ready. The book also shows that Definition of Done varies among teams—an operations team may have a different DoD than an innovation team—but having common definitions at scale helps portfolio leaders and others understand what "shippable" means. Sprint-level DoD asks "what is potentially shippable?" while Release-level DoD asks "what does it mean to release your product?"

Why It Matters

Distributed teams naturally drift toward different understandings of completion—one team's "done" might be another's "in progress." An explicit, agreed Definition of Done converts this silent miscommunication into a single point of control. It surfaces quality expectations upfront, prevents rework, and makes it possible for portfolio leaders to reason about whether work is truly shippable. As a team matures and automates more, the Definition of Done becomes a mirror of their technical discipline.