Acceptance Criteria are used to ensure that a feature (or User Story) the team is building meets the needs of the End User. The common practice is for team members to collaborate on writing a series of examples that demonstrate the expected behaviours of a feature.
Example Mapping: Your Secret Weapon for Effective Acceptance Criteria
Scrum By Example – Waiting Too Long to Create Acceptance Criteria
Scrum By Example – The Team Collaborate on Acceptance Criteria
Definition of Done vs. User Stories vs. Acceptance Criteria
Lifecycle of a User Story
Resource Links:
- 7 Tips for Writing Acceptance Criteria with Examples
- Example Mapping (Draft.io)
- Example Mapping (Inside Product)
- Introducing Example Mapping
- User Stories And Acceptance Criteria In The House
See Also:
Behaviour Driven Development
Definition of Done
User Stories
Mark Levison has been helping Scrum teams and organizations with Agile, Scrum and Kanban style approaches since 2001. From certified scrum master training to custom Agile courses, he has helped well over 8,000 individuals, earning him respect and top rated reviews as one of the pioneers within the industry, as well as a raft of certifications from the ScrumAlliance. Mark has been a speaker at various Agile Conferences for more than 20 years, and is a published Scrum author with eBooks as well as articles on InfoQ.com, ScrumAlliance.org an AgileAlliance.org.
*Thank you for visiting the World's Largest Opinionated Agile Reference Library. This content is created and the links are curated through the lens of Agile Pain Relief Consulting's view of what is effective in the practice of Scrum and Agile. We don't accept submissions and emails to that effect are marked as spam. Book listings may use affiliate links that could result in a small commission received by us if you purchase, but they do not affect the price at all. From experience, this won't amount to anything more than a cup of coffee in a year.« Back to Glossary Index