Skip to content
BENIBIX Learn

Acceptance Criteria

Business📋 Agile DeliveryUser Stories

Also known as Conditions of Satisfaction, Story Acceptance Criteria

The checks one user story must pass to be accepted. Each one can pass or fail.

Think of it like

It is like a list from a parent. A tidy room means bed made, toys away and floor clear.

Example

For the story save my cart, Emma's team writes two criteria. A saved cart is still there after log-out. A saved cart empties after 30 days.

Why it matters

They settle what done means for this one story before work starts. Testers can turn each line into a test.

Definition

Acceptance criteria are the checks one user story must pass to be accepted. They are written before the work starts, often by the Product Owner with the team. Each one is a plain check that can pass or fail. Many teams write them as Given, When, Then, a form from behaviour-driven development. Each story has its own list. The Definition of Done is one list for all work.

Example code

text
Given I have 2 items in my cart
When I log out and log back in
Then I still see the same 2 items
One criterion in the Given, When, Then form. It reads like a test anyone can run.
The criteria sit on the back of the card. When every box is ticked, the story is accepted.

Common mistake

Writing how to build it instead of what must be true. Criteria describe results a user can see, not the code.

Key takeaways

  1. 1
    One story each. Every story gets its own list.
  2. 2
    Pass or fail. Each line is a clear yes or no.
  3. 3
    Agreed up front. Written before the work begins.

Compare

Learn it properly