Step 1 of 10
Writing user stories: how this workshop works
In this workshop you practise writing user stories with examples from real work: the "As a / I want / so that" template, the INVEST checklist, acceptance criteria and splitting a big story. Every step has an exercise where you build, check or split a story and see at once whether it holds up.
A user story is a short description of something a person wants to do with a product, written from their point of view. Teams use stories to plan work in small pieces that each give someone something useful. Press the button below to watch a vague request become a story, and then a set of small, checkable slices.
In this lesson you'll:
- turn a request into a story with a real role, goal and benefit;
- test a story against the six INVEST qualities and fix the one it breaks;
- write acceptance criteria and Given/When/Then scenarios a tester could run;
- split a story that is too big into thin slices that each work on their own.
It takes about 70 minutes. The examples come from three products: a support team's shared inbox, an expense-claims app and an HR portal.