Agile teams employ short statements that serve as indicators of what “done” means for a specific user story. That is, Acceptance Criteria define desired behavior and determine whether a work item has been successfully developed. Acceptance Criteria work in conjunction with the Definition of Done, in that Acceptance Criteria are user-story-specific, while the Definition of Done is global. To cite a more formal definition of Acceptance Criteria, from IEEE 610: “The external quality characteristics specified by the product owner (or a proxy for the PO) from a business or stakeholder perspective.”
Acceptance Criteria Video
Acceptance Criteria Podcasts
Acceptance Criteria Example
Authored by Philip Rogers
Adaption by Karl Smith
Photo by Austin Chan on Unsplash
Agile World Resources are provided as free resources to anyone seeking to learn more and are shared under a creative commons attribution license. This means if you use a resource elsewhere you must name Agile World Publishing as the source, who the author is, and the photo creator (if used).