Skip to content
BENIBIX Learn

User Story

Business📋 Agile DeliveryUser Stories

Also known as Agile User Story, Agile Story

A short note of one thing a user wants, and why. The details come from talking.

Think of it like

It is like a note to a cook. It says who the meal is for, what they want and why.

Example

Emma's team writes: as a shopper, I want to save my cart, so that I can buy later. They agree on two acceptance criteria and build it in four days.

Why it matters

It keeps the team talking about what users need, not only about features. The why part helps them pick the simplest way to get there.

Definition

A user story is a short note about one thing a user wants. It is written from the user's side, in plain words. The usual form is: as a kind of user, I want something, so that I get a gain. The card is kept short on purpose. The details come from talking with the team and from the acceptance criteria. A story should be small enough to finish in one sprint.

Example code

text
As a shopper,
I want to save my cart,
so that I can come back and buy later.
Three parts: who wants it, what they want, and how it helps them.
The front says who, what and why. The back holds the checks that say when the story is done.

Common mistake

Writing the whole spec on the card. A story is a promise to talk, and the details belong in the talk and the acceptance criteria.

Key takeaways

  1. 1
    Who, what, why. Name the user, the need and the gain.
  2. 2
    Card, talk, confirm. A short card, a talk, then the checks.
  3. 3
    Fits one sprint. Split it if it cannot finish in one.

Compare

Learn it properly