6-7 minutes<\/p>\n
Definition of Done (DoD) is a list of requirements that a user story must adhere to for the team to call it complete. While the Acceptance Criteria of a User Story consist of set of Test Scenarios that are to be met to confirm that the software is working as expected.<\/p>\n
The difference between these two is that the DoD is common for all the User Stories whereas the Acceptance Criteria is applicable to specific User Story .Acceptance Criteria of each User Story will be different based on the requirements of that User Story. In other words, Both DoD and Acceptance Criteria must be met in order to complete the User Story.<\/p>\n
The Product Increment is not considered to be complete, unless both these two lists are done. Thus, we need to define two aspects of the Definition of Done (DOD) \u2013 Completion Criteria and Acceptance Criteria:<\/p>\n
Definition of Done vs Acceptance Criteria<\/p>\n
The definition of Done is structured as a list of items, each one used to validate a Story o r PBI, which exists to ensure that the Development Team agree about the quality of work they\u2019re attempting to produce. It serves as a checklist that is used to check each Product Backlog Item (aka PBI) or User Story for completeness. Items in the definition of \u201cDone\u201d are intended to be applicable to all items in the Product Backlog, not just a single User Story. It can be summarized as following:<\/p>\n
For example, in the software industry, teams may need to ask some of the following questions to come up with their DoD:<\/p>\n
User stories are one of the primary development artifacts for Agile development , but Scrum doesn\u2019t explicitly require either User Stories or Acceptance Criteria to be used. If a product backlog item is consider to be too big to be put into a sprint, will normally bebroken down into user story and subsequently into a set of tasks as shown in the Figure:<\/p>\n
Acceptance Criteria<\/p>\n
User Stories encapsulate Acceptance Criteria, thus we often see the definition of done and acceptance criteria co-existing in our scrum development process. User story provides the context of the functionality the team should deliver. The acceptance criteria gives guidance about the details of said functionality and how the customer will accept them. The two of them together provide the whole deliverable.<\/p>\n
Some of the Acceptance Criteria will be discovered in Ongoing Backlog Refinement events before the Sprint starts, and others will be discovered right after Sprint Planning when sit down to have a conversation about the user story in a small team. So Acceptance Criteria are attributes that are unique to the User Story or Product Backlog Item.<\/p>\n