What are Acceptance Criteria?
What you'll learn: How to define concrete, testable conditions that determine when a user story is truly "done."
The Core Idea
Acceptance criteria are the specific, measurable conditions that a user story must satisfy before it can be marked as complete. Think of them as a checklist that both developers and stakeholders agree on upfront—if all boxes are checked, the feature is accepted; if not, more work is needed.
Imagine you're ordering a custom pizza. Your order (the user story) might be "As a customer, I want a large pepperoni pizza so I can feed my family." But what makes that order complete? The acceptance criteria spell it out:
- Pizza must be large (14 inches)
- Pizza must have pepperoni topping
- Crust must be baked until golden
- Pizza must be delivered within 30 minutes
Without these criteria, "done" becomes subjective. One person might think any size with pepperoni works; another might expect extra cheese. Acceptance criteria remove that ambiguity.
Why They Matter
Acceptance criteria bridge the gap between the high-level user story and actual implementation. They:
- Define scope boundaries – what's in and what's out
- Enable testability – QA knows exactly what to verify
- Prevent scope creep – new requests become new stories
- Align expectations – everyone agrees on "done" before work starts
The best acceptance criteria are written in plain language, from the user's perspective, and can be verified objectively. They're typically written with the user story during requirements gathering, often refined during stakeholder interviews or workshops.
Key Takeaway: Acceptance criteria turn vague user stories into concrete, testable requirements that define exactly when a feature is complete and ready for acceptance.