Skip to main content

[VLOG] What is The Definition of Done & How Is It Different than Acceptance Criteria

February 15, 2020

Hello awesome people. How was your week? In today's vlog I would like to talk about one of the most important aspects of Scrum, that is the Definition of "Done". Whenever I went into companies who complained that either Scrum failed because the quality of the product is worse or Scrum did not make their company much more agile, I have found one of the most common reasons is ... there isn't technical excellence in their product's Definition of "Done". Even worse, some companies do not even have a Definition of "Done" made transparent.

It seems many companies these days who want to be agile are much more focused in doing the Scrum mechanics and neglect this most important aspect of Scrum. The Scrum Guide itself says that the purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current Definition of "Done".  So how can many companies missed the Definition of "Done"? One of the reasons I found is because people think that Definition of "Done" is the same as Acceptance Criteria. So in today's vlog, I show you what the Definition of "Done" looks like. Many of my future vlogs is going to refer to this vlog as the Definition of "Done" - the center aspect of Scrum. So make sure you don't miss this one. And don't forget to share it to the world so more people can focus more on quality than outputs/velocity.





What did you think about this post?