Acceptance Criteria and INVEST
Level 4 Β· Stories, sizing and tracking
How acceptance criteria say when a story is done. How six INVEST letters check a story. What a ready check adds before a sprint.
Course contentsLesson 13 of 19
Level 1 Β· What agile is
Level 2 Β· Scrum
Level 3 Β· Kanban
Level 4 Β· Stories, sizing and tracking
Level 5 Β· Other methods and scale
After this lesson you can
- Write acceptance criteria for a story
- Check a story against INVEST
- Decide when a story is ready to start
11 mincovers 3 glossary entries
Worth reading first: User Stories and Epics
How to tell a good story from a vague one
Acceptance criteria are the checks one user story must pass to be accepted. Each one can pass or fail. For save my basket, one might say a saved basket is still there after 7 days. Another might say saving takes one tap. A story usually has 3 to 6 of them, written before the work starts.
Many teams write them in a set form: given, when, then. Given I have 3 items in my basket, when I close the app, then the 3 items are there when I open it again. The form makes people say the starting point, the action and the result.
Acceptance criteria belong to one story. The Definition of Done is one list for all work, like tested and reviewed. A story is only finished when it meets both. It needs its own checks, and the team's shared ones.
INVEST is a six-letter check for a good story. Independent: it can be built in any order. Negotiable: the details are open to talk. Valuable: a user gains from it. Estimable: it can be sized. Small: it fits in a sprint. Testable: it can be checked.
A story that fails a letter needs work before a sprint. A story that cannot be tested has no acceptance criteria yet. One that cannot be sized may need a spike. One that is not small needs splitting.
Some teams add a Definition of Ready. It is a checklist for when a story may enter a sprint, such as it has acceptance criteria, it is sized and nothing blocks it. It is not part of the Scrum Guide, but many teams find it saves time at planning.
The common mistake is a Definition of Ready so strict that nothing passes, and work stops. Keep it short. The aim is to avoid starting a story nobody understands, not to write the whole thing up front.
Worked example
Lucy's story fails the T
Lucy's team has a story: as a user, I want the search to be better. It fails testable, because nobody can say when it is better.
They rewrite it with 3 criteria. One says a search for a book title shows that book in the top 3 results. Now it can pass or fail, and it is ready for the next sprint.
The words for this lesson3
Check yourself
Is a story's own checklist the same as the team's done list?
Finished this lesson?
Marking it complete also marks its 3 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.