Acceptance criteria
Acceptance criteria state verifiable outcomes used to assess whether a requirement meets its intended need.
Acceptance criteria are verifiable outcomes used to assess whether a requirement meets its intended need. They make a general wish such as “easy ordering” concrete for implementation and review.
For a fictional portal, one criterion is: selecting two cartons of B-6 displays 12 units and 36 EUR net goods value. The relevant master data defines six units and 18 EUR per carton. Another criterion can specify what remains visible without ERP acknowledgement.
A criterion states the required outcome. A test case adds the prerequisites and steps used to check it. Criteria should be understood before acceptance and include important failure cases. An attractive interface alone does not prove they are met.
Sources
Related terms
- Product discoveryInvestigating needs, constraints and risky assumptions before settling on a product solution.
- Product OwnerThe person accountable in Scrum for product value, the Product Goal and effective backlog management.
- Definition of DoneThe shared description of the quality conditions a completed product Increment must meet.
- User storyA short description of a user role, a need and the goal behind it.
- Product BacklogThe ordered, continually evolving collection of improvements needed for a product.
- ScrumA framework for working together incrementally on complex product challenges.
Articles on this topic
Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.