# User Story

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

**Field:** Business & Startups  
**Category:** Agile Delivery  
**Also known as:** Agile User Story, Agile Story

## Think of it like

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

## 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

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.

## 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.

## 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.

## 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.

## Three principles

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

## Related terms

- [Epic](https://learn.benibix.com/term/business/epic)
- [Acceptance Criteria](https://learn.benibix.com/term/business/acceptance-criteria)
- [INVEST Criteria](https://learn.benibix.com/term/business/invest-criteria)
- [Product Backlog](https://learn.benibix.com/term/business/product-backlog)
- [Story Points](https://learn.benibix.com/term/business/story-points)
- [User Scenario](https://learn.benibix.com/term/design/user-scenario)

## Told apart from

- [Epic vs User Story](https://learn.benibix.com/compare/epic-vs-user-story): People think an epic is a different kind of thing from a story. It is a story too big to finish in one sprint. Before anyone builds it, it is split into user stories that each fit a sprint.
- [User Story vs Project Requirements](https://learn.benibix.com/compare/user-story-vs-project-requirements): People think a user story is a requirement in a new format. A requirement tries to write down all the detail up front. A user story is a short note that promises a talk. The detail comes later, in that talk and in the acceptance criteria.
- [User Scenario vs User Story](https://learn.benibix.com/compare/user-scenario-vs-user-story): People think a user scenario is a user story, and it is not. A user story is one small thing to build, in one line: as a user, I want this, so that I can do that. A user scenario is a longer story about a real moment, with where the person is and what gets in the way. Designers write scenarios to understand people. Teams write stories to plan the work.
- [Use Case vs User Story](https://learn.benibix.com/compare/use-case-vs-user-story): People think a use case is just a long user story, and it is not. A user story is one short line about what a user wants and why. The details come later, in talk. A use case writes out each step to the goal, plus what happens when a step fails.
- [Job Story vs User Story](https://learn.benibix.com/compare/job-story-vs-user-story): People think a job story is a user story with new words, and it is not. A user story starts from a type of user and is a piece of work to build. A job story starts from a moment: when this happens, I want to do this, so I can get that. It names no product, so it shows the need before anyone picks a fix.

## Taught in

- [User Stories and Epics](https://learn.benibix.com/learn/business-agile/user-stories-and-epics): Agile and Scrum, 12/19
- [Product Requirements Document](https://learn.benibix.com/learn/business-product-management/product-requirements-document): Product Management, 2/13

![Two index cards side by side. The front of the card reads as a shopper, I want to save my cart, so that I can buy later, with the three parts marked who, what and why. The back of the card, in the accent colour, lists two acceptance criteria with tick boxes: the cart is still there after log-out, and the cart empties after 30 days.](https://learn.benibix.com/diagrams/agile-user-story-card.svg)

---

Source: https://learn.benibix.com/term/business/user-story
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-17
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
