Definition of Dumb - by Adam Ard - Rethinking Software

Scrum's Definition of Done (DoD) is a convenient way for Scrum advocates to punt on resolving any real issues with their process.

If anyone complains that Scrum produces poor results, they have their ready response: The DoD should prevent this; if the work doesn't fit the DoD, it should be rejected; developers are simply not following the process.

Despite the inefficiencies and frustrations Scrum piles on developers, poor results are "impossible." Why? Because the Scrum Master has defined them away—binding programmers to their unholy oath of compliance. 1

The Scrum Guide defines the Definition of Done as a shared understanding of what it means for a product increment to be complete—a quality standard ensuring all increments are potentially shippable or releasable. In other words, “nothing ships unless it’s perfect.” Easier said than done.

Good ideas, but unless your process builds them into daily workflows—through TDD, pair programming, or literate programming—they’re just bolt-ons, band-aids to stop the bleeding.

Leave a Comment