Acceptance Criteria define how a particular feature could be used from an end user’s perspective.

1. Each Product Item Backlog must hast at least 1 acceptance criteria
2. Acceptance Criteria are written before implementation
3. Each acceptance criterion is independently testable
4. Acceptance criteria must have a clear Pass / Fail result.
5. It focuses on the end result.
6. Include functional as well as non-functional criteria - when relevant.
7. Team members write acceptance criteria and the Product Owner verifies it. It confirms the PO and the team have a shared understanding of the user story.