In my early days with scrum, I came across the concept of "Definition of Done" or DoD and "Acceptance Criteria", in the beginning, I thought both are the same and its just synonyms, but later on, I discovered that they have some differences, can you name some you know? Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
There isn't a major difference, and maybe my colleagues here can elaborate more but here is how I understand it:
Acceptance criteria are story specific requirements that must be met for the story to be completed. Acceptance criteria are often added during backlog refinement or during the sprint planning meeting.
The definition of done is a list of things that need to be completed for any story to be considered done. It covers what the team feels is necessary to consider any story done.
...
3 replies by Mohammed Derbashi, Mohua Ghosh, and Nicole Ramos
Feb 19, 2018 2:23 AM
Mohammed Derbashi
...
That's exactly what I discovered ... thanks Rami
Jan 07, 2021 6:46 AM
Nicole Ramos
...
I fully agree
Jan 23, 2021 11:16 PM
Mohua Ghosh
...
I totally agree both Acceptance Criteria and Definition of Done are completely different.The responses seem to have addressed it fully.
Saving Changes...
Clemens BauerCEO| Think3 Consulting GmbHGraz, Austria
This article [1] states out that the "Definiton of Done" is more a general way of knowing something of the sprint is done. While the acceptance criteria is defined for each story. Telling what must be met in order to complete story.
There isn't a major difference, and maybe my colleagues here can elaborate more but here is how I understand it:
Acceptance criteria are story specific requirements that must be met for the story to be completed. Acceptance criteria are often added during backlog refinement or during the sprint planning meeting.
The definition of done is a list of things that need to be completed for any story to be considered done. It covers what the team feels is necessary to consider any story done.
That's exactly what I discovered ... thanks Rami Saving Changes...
Acceptance criteria is generally 'Business case' focussed. It is functional in nature (An exception could be technical spikes). For example, if you are designing a login scree, the acceptance criteria can be that the user should be able to login and see the landing screen upon giving successful credentials'. It is defined by the Product Owner for each story.
DoD is more process related. For example, it answers when you consider the login screen story done? Is it when the Dev is complete, or when stand-alone testing is complete or when there are zero open defects?
DoD is generally decided by the scrum team and is kept consistent for all stories and across sprints. Saving Changes...
Adding to Rami's comments, it is my understanding that the DoD pertains to all backlog items as a whole, therefore all stories are tested against that DoD. But Acceptance Criteria could be created for a group or stories or even one story at a time. Further, an Acceptance Criteria may fail and yet the feature still passes and potentially be released. Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Abhinav makes a great distinction for recognizing the AC is business-centric and to validate to user-story meets all criteria. DoD is agreed to by the team and encompasses all stories. Saving Changes...
DoD is team-specific whereas AC's are work item (e.g. stories, use cases) specific. ACs can be used as the starting point for test cases whereas DoD covers aspects of "doneness" that go beyond the functioning of a particular work item.
DoD is usually defined before sprinting begins and will be updated periodically based on review feedback and other inputs whereas ACs are progressively elaborated through the lifecycle of a work item and should be well defined before the team has committed to completing it within a given sprint.
DoD should include a statement that the ACs are met for all stories. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Acceptance Criteria is composed by two main components (mostly forgotten): 1-the criteria. 2-the process to meet the criteria. Saving Changes...
Ramanna GurubelliPM III| Independent ConsultantCanberra, Act, Australia
Acceptance Criteria is defined to ensure quality of the user story and the product ultimately. The acceptance criteria informs test planning and design. In other words, it defines what the success should like when the user story is delivered. For example, the acceptance criteria for a 'Login' screen could include verfication/validation for UI/UX of the screen, input field validations, success/failure messages, etc.
On the other hand, definition of done (DoD) defines the criteria for completion of a stage gate in the software development process. For example, DoD for completion of analysis and design stage could include completion of UI/UX design, solution design, database design, infrastructure design, etc. Saving Changes...
Community Champion
