Acceptance Criteria in Scrum: Meaning, Examples and Best Practices
Acceptance Criteria are conditions that describe what a Product Backlog Item should achieve or satisfy.
They help the Product Owner, Developers and other relevant people develop a shared understanding of what is expected.
Why Are Acceptance Criteria Useful?
A User Story may explain the user's need, but it may not contain enough detail to understand the expected behavior.
Acceptance Criteria add useful clarity without turning the Product Backlog Item into a large specification.
- Clarify expectations.
- Reduce misunderstandings.
- Support productive conversations.
- Help Developers understand expected behavior.
- Provide a basis for checking the result.
Simple Example
As a customer, I want to reset my password so that I can regain access to my account.
Possible Acceptance Criteria
- The customer can request a password reset using their registered email address.
- A password-reset link is sent to the registered email.
- The link expires after the defined period.
- The customer can create a new password using the link.
- The customer receives confirmation after the password is successfully changed.
Acceptance Criteria vs Definition of Done
These two concepts are related but they are not the same.
Common Format
Acceptance Criteria can be written in different formats. One commonly used approach is:
When an action occurs
Then a specific result should occur
Example
When the customer selects "Pay Now"
Then the order should be successfully created
Good Acceptance Criteria
Useful criteria should be:
- Clear
- Understandable
- Relevant to the Product Backlog Item
- Specific enough to remove major ambiguity
- Focused on expected behavior or outcome
Common Mistakes
Who Creates Acceptance Criteria?
There is no mandatory Scrum rule requiring one specific person to write Acceptance Criteria.
They are best developed collaboratively so that the Product Owner and Developers have a shared understanding of the expected outcome.
What Is the Scrum Master's Role?
The Scrum Master can help the team improve how Product Backlog Items are understood and refined.
The Scrum Master should encourage collaboration rather than becoming the person who writes every Acceptance Criterion.
Acceptance Criteria help answer: "What should this particular item achieve?"
Definition of Done answers: "What quality standard must the Increment meet?"
Key Takeaway
Acceptance Criteria are a practical technique for creating shared understanding around Product Backlog Items.
Keep them clear and useful. Avoid turning them into unnecessary documentation.