Skip to main content

What's the difference between "Definition of Done/Ready" & Acceptance Criteria in a Feature or in a User Story

Last post 08:38 pm June 6, 2024 by Thomas Owens
2 replies
11:22 am June 6, 2024

Hello 

I am new to Scrum and Jira, i am looking to become a Scrum Master

In the company i work for the Scrum team that regularly talk about "Definition of Done/Ready"  

Question What is the difference between the Acceptance Criteria in a Feature or in a User Story   compared to a "Definition of Ready/Done"

Regards

Rice 

 


07:34 pm June 6, 2024

Scrum doesn't mention a Definition of Ready, just a Definition of Done, but it does talk about a ready state. Once the Developers understand that work can be Done in a Sprint, it is deemed ready for consideration in Sprint Planning. Acceptance criteria may help with this.

Product Backlog refinement is the art and science of making work ready. The question in Sprint Planning should never be "can we do this work?" The Developers know they can. The question is "Should we? Should we do this work in order to meet a good and meaningful Sprint Goal?"


08:38 pm June 6, 2024

In Scrum, there is no such thing as a Definition of Ready. Product Backlog Items "are deemed ready for selection in a Sprint Planning event" when the Scrum Team asserts that there is enough clarity and enough decomposition to complete the Item within 1 Sprint.

In my experience, though, some teams do find comfort in enumerating a Definition of Ready to help guide them in refinement. Although it can be helpful in some cases, it can also become overly restrictive or prescriptive and can lead to a team spending too much time refining and delaying starting work, which delays finishing work and getting feedback to evolve the product.

User Stories and Acceptance Criteria aren't a part of Scrum, either. User Stories come from Extreme Programming. Some teams do find it helpful to use user stories as a way to structure Product Backlog Items, but it isn't mandatory. Acceptance Criteria align with the idea of "Confirmation" from user story cards, which outline the criteria that must be fulfilled to achieve customer value.

There is a close relationship between Scrum's Definition of Done and Acceptance Criteria. The Definition of Done is a set of criteria that is applicable to all Product Backlog Items so that the team and the stakeholders understand the state of the product after the team says a Product Backlog Item is done. Acceptance Criteria serve a similar purpose, but are specific to a given user story (or Product Backlog Item).


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.