Acceptance Criteria

Acceptance criteria are short statements that help the team make sure they've finished a task the way the user wants. It's like a checklist to confirm their work.

These criteria are simple and straightforward. They either pass or fail, and typically they're written from the user's point of view. For example, they might say, "The user can see prices on the item report."

Having acceptance criteria is also useful because they can show if a story is too big or complicated. If there are too many criteria, it might mean the story needs to be broken down into smaller parts.

It is important to note that acceptance criteria are specific to individual stories, while the Definition of Done applies universally to all stories.

Resources

Acceptance Criteria is covered in the Adaptive Agility Fundamentals class as part of the Story Lifecycle

This Scrum Alliance article explains what acceptance criteria are, their purpose, how to create them, and give examples of good and bad acceptance criteria.