Definition of Done
Each Scrum Team has its own Definition of Done or consistent acceptance criteria across all User Stories. A Definition of Done drives the quality of work and is used to assess when a User Story has been completed. For an hour-long deep dive into this topic, please see our webinar Getting to Done (subscription required).
Upon completion you will:
- Be able to articulate what a Definition of Done is
- Create a Definition of Done for your Team(s)
- Know why its important to have a Definition of Done
Definition of Done Overview:
In software, a Definition of Done may be: “Done means coded to standards, reviewed, implemented with unit Test-Driven Development (TDD), tested with 100 percent test automation, integrated and documented.”
In a services context, it might look something like this: "Done means every task under the User Story has been completed and any work created is attached to the User Story so the Product Owner can review it and make sure it meets his or her expectations."
At Scrum Inc., a business services organization, this can include word documents, excels sheets, presentation decks, e-mails or any number of other work produced. In order for the Product Owner to accept the story these elements need to be attached to the User Story for it to be called done.
The Definition of Done ensures everyone on the Team knows exactly what is expected of everything the Team delivers. It ensures transparency and quality fit for the purpose of the product and organization. As Jeff points out in video, getting stories done can double a Teams Velocity. The slides delineate how to get stories both Ready and Done.
View Class Slides:
Learn Scrum Remotely From Those Who Helped Create It.
Our online courses are live, highly interactive and taught by leading experts. Earn an industry-recognized credential while positioning yourself, your team and your organization to succeed in today’s complex business climate.