Definition of Done v/s Acceptance Criteria

One of the most common questions asked by Scrum-Agile practitioners and the the question which also receives the most varied set of answers is this:

What’s the difference between acceptance criteria and the Definition of Done (DoD) ?

The simple answer is this:

Acceptance criteria are specific to a particular product backlog item. Something becomes an acceptance criteria if it is so vital that the Product Owner will reject the item if it does not fulfill any of the criteria.

 

The Definition of Done, on the other hand, is universal. A Definition of Done includes things that nearly all product backlog items need to comply with.
 

An Example

Here’s an example of how I'm using a Definition of Done and Acceptance Criteria if I were to create a podcast on this topic.  

The acceptance criteria for the podcast would be:

 

• Explanation of Acceptance Criteria

• Explanation of Definition of Done

• Explanation of the difference between the two

But for the podcast to be complete I also need to meet my Definition of Done which could be :
 

• Quick introduction at the Start 

• The video should be as short as possible to respect viewers’ time

• There should be a reminder for viewers to click the like button and subscribe 

• There should be a cover image for the podcast when over 1 minute

• There should be a short description for the podcast

• There should be links to other useful reference material

The Definition of Done may be applicable for all podcasts that I may create in future.

 

Who writes acceptance criteria?

The Product Owner writes the acceptance criteria. After all, the product owner is the one who understand the needs of the customer. The Acceptance criteria for a User story should reflect what he or she believes is important for the customer.
 

This does not mean the Product Owner has to document a lengthy list of tests. Instead, the Development team can create specific test cases from the higher-level acceptance criteria.
 

Who writes the Definition of Done?

The definition of done should be created and agreed upon by the Entire Scrum team—Developers, Product Owner, and Scrum Master or coach. And that definition can and should evolve and improve over time.
 

This group arrives at the definition of done through a shared understanding of what it means to create a high-quality, shippable product in their context.
 

Adding Acceptance criteria to user stories and adhering to a Definition of Done will help your team succeed with agile

Coach Ram

Credit: Mike Cohn