Identifying Acceptance criteria dor features

Last post 10:46 am October 31, 2019 by Olivier Ledru

3 replies

02:47 am October 31, 2019

What are some activities I can do with my PO to help in identifying a feature's acceptance criteria? We are currently refining some features for the next PI, but struggling to come up with proper AC.

Ian Mitchell

05:22 am October 31, 2019

Product Backlog refinement sessions that include the whole Development Team. They are the ones who will have to meet any acceptance criteria which are identified.

Thomas Owens

10:10 am October 31, 2019

To just expand a little on what Ian Mitchell said, if you have a Development Team that is reasonably familiar with the product or service and the domain, the questions they ask when refining the Product Backlog Item can often guide what needs to be clarified, which could perhaps be Acceptance Criteria. Consider that Scrum doesn't mandate a specific format for Product Backlog Items - stories and acceptance criteria are only one such representation.

Olivier Ledru

10:46 am October 31, 2019

We are currently refining some features

Who is "We" ?

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.