Intro to Git — Snapshots, Branches & Sharing
WorkshopyOfficial10 stepsQuiz9 interactiveDiagram
gitversion controlbeginners
User story writing workshop with examples: build stories from the template, check them with INVEST, write acceptance criteria and split big stories.

WorkshopyOfficial
78 lessons · used by 2 teachers
Sign in to copy it to your workspace. It’s free.
10 steps · 2 quizzes · open any step, or read it here
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.
Interactive · From a vague request to small, checkable slices — try it in the lesson
In this lesson you'll:
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.
A user story is not a specification. Kent Beck introduced stories in Extreme Programming in the late 1990s, and in 2001 Ron Jeffries described their three parts as the 3 Cs:
The card is small on purpose. If you try to fit every detail onto it, nobody has the conversation, and the team builds what the card says instead of what the user needs.
Try it: the notes below all belong to one support inbox story. Sort each one into Card, Conversation or Confirmation.
Interactive · Sort the notes: Card, Conversation or Confirmation — try it in the lesson
Takeaway: the written story is the smallest part. Most of the value is in the conversation and the agreed checks.
The most common way to write the card is:
As a [role], I want to [goal], so that [benefit].
The format came from a team at the London company Connextra around 2001, and it spread because each part answers a question the team needs answered:
Try it: for each product, read what the team heard and build the story from the parts. A wrong part tells you what is wrong with it.
Interactive · Build a user story from its parts — try it in the lesson
Takeaway: who, what and why. If the "so that" just repeats the goal, you don't yet know why anyone wants it.
In 2003 Bill Wake proposed INVEST, a checklist for a good story. Mike Cohn's book User Stories Applied (2004) spread it widely. A good story is:
| Letter | Quality | The question to ask |
|---|---|---|
| I | Independent | Can it be built in any order? |
| N | Negotiable | Is there room to agree the details together? |
| V | Valuable | Does a user or customer get something from it? |
| E | Estimable | Can the team say roughly how big it is? |
| S | Small | Does it fit comfortably in one sprint? |
| T | Testable | Can we check when it is done? |
INVEST is a checklist, not a score. A story that fails one letter usually tells you what to do next: merge it, split it, ask a question, or write the test.
Try it: go through the six letters. Each one shows an expense-claims story that breaks it and the same need rewritten.
Interactive · The six INVEST qualities, broken and fixed — try it in the lesson
Takeaway: most broken stories fail on V, S or T: technical tasks dressed as stories, stories that are really epics, and wishes nobody can test.
Now check stories the way a team does in backlog refinement. Each story below breaks one INVEST quality more clearly than the others. Find it, then read how a team would fix it.
Try it: pick the letter for each of the six stories. Use Hint if you're stuck.
Interactive · Find which INVEST quality each story breaks — try it in the lesson
Takeaway: naming the letter turns "this story is bad" into a fix everyone can agree on.
Four quick questions before acceptance criteria.
Question 1. What do the 3 Cs of a user story stand for?
Question 2. In "As a support agent, I want to see a customer's earlier tickets next to a new email, so that I don't ask them to repeat themselves", which part is the benefit?
Question 3. Which story breaks the V in INVEST?
Question 4. What does Negotiable mean in INVEST?
Acceptance criteria are the Confirmation part, written down. They are short rules the story must meet. A good criterion is:
Write them before the team starts building, in the conversation. Three to six criteria per story is common. If you need many more, the story is probably too big, and the criteria show you where to split it.
Try it: the story below has four criteria (the amounts are illustrative). Change the claim and make each rule fire. Look at which rule decides first when two could apply.
Interactive · Acceptance criteria for an expense claim — try it in the lesson
Takeaway: each criterion is a test you could run by hand. If you can't imagine running it, rewrite it.
Some criteria are easier to agree on as an example. Given / When / Then comes from behaviour-driven development (BDD), which Dan North and Chris Matts shaped in the mid-2000s:
Scenario: enough days left
Given the employee has 10 leave days left this year
When they request 3 days in March
Then the request shows as Pending, and their manager is told
Each scenario checks one behaviour. Write the usual case first, then one scenario for each rule that can say no. The most common mistakes are an action hidden in Given, a result in When, and a Then nobody can check ("it works").
Try it: build the three scenarios for an HR portal story. Each wrong choice says which part it belongs to.
Interactive · Build Given, When, Then scenarios — try it in the lesson
Takeaway: a state, one action, a visible result. A scenario a tester can run as written is a scenario that ends arguments.
A story too big for one sprint is often called an epic. Don't split it by the layers of the system (database, API, screen): no layer on its own lets anyone do anything. Split it vertically, so that each slice cuts through every layer and gives a user something to try. Three ways work for most stories:
Other common splits: the happy path before the errors, one user role before the others, a simple version before the faster or prettier one.
Try it: split the HR portal epic each way, then press "By layer" to see why that split doesn't work.
Interactive · Split a big story three ways, and one way not to — try it in the lesson
Takeaway: every slice should be something a user could try and tell you whether it helps.
Here is a support inbox epic and eight ideas for how to split it. Half are vertical slices. The other half are layers, phases or tasks dressed up as stories.
Try it: keep the four slices an agent could use on their own, drop the other four, then choose which slice to build first.
Interactive · Keep the vertical slices of a support inbox epic — try it in the lesson
Takeaway: build the thinnest slice that works end to end first. The others build on it.
Each exercise is one decision you make when you write or review a story. Check your answer; a wrong one tells you why.
Six questions on the whole workshop.
Question 1. In a Given/When/Then scenario, what goes in When?
Question 2. Which split of "Agents handle customer emails in a shared inbox" is a vertical slice?
Question 3. What are acceptance criteria for?
Question 4. Who proposed the INVEST checklist, in 2003?
Question 5. Which are signs that a story is too big? (pick all)
Question 6. An epic is split into slices. Which slice should usually be built first?
Workshopy shares this lesson under CC BY 4.0. Anyone may use and change it, with credit to you. Anyone can learn it here, free. A copy in your workspace is yours to change and run live; your students never need an account.
Version 1Current
· First published
Copies are made from the current version. A copy you already have doesn’t change.
WorkshopyOfficial10 stepsQuiz9 interactiveDiagram
gitversion controlbeginners
WorkshopyOfficial16 steps2 quizzes15 interactiveDiagram
workshopyproduct touronboarding
WorkshopyOfficial10 steps2 quizzes10 interactive
data-literacystatisticsmean and median
WorkshopyOfficial10 steps2 quizzes9 interactive
managementokrgoal setting
WorkshopyOfficial10 steps2 quizzes9 interactive
managementproject managementcritical path
WorkshopyOfficial10 steps2 quizzes9 interactive
managementtime managementeisenhower matrix
Comments
No comments yet. Be the first to say how it went.