# User Stories and Epics

> How a user story writes one need in one line, and why the detail comes from talking. How epics break into stories, and when a spike comes first.

**Course:** [Agile, Scrum and Kanban](https://learn.benibix.com/learn/business-agile)  
**Time:** 12 min

**After this lesson you can:**

- Write a user story in the usual form
- Split an epic into stories
- Know when a spike is needed

## How to write work as user stories

A user story is a short note of one thing a user wants, and why. The usual form is as a kind of user, I want something, so that I get a gain. As a reader, I want to save my place, so that I can stop and come back. The card is kept short on purpose, often one line.

The detail comes from talking, not from the card. A story is a promise of a conversation between the people who want it and the people who build it. That talk happens close to when the work starts, when people know the most.

An epic is a story too big for one sprint. Pay bills in the app is an epic. It splits into stories such as add a payee, pay a bill and set up a monthly payment. Each of those fits in a sprint. The epic is done when its stories are done.

Story splitting is how the big ones get small. The cut should go across the layers, from screen to data, so each small story still works on its own. Building the whole screen first, then all the logic, then the data, gives three pieces that do nothing alone.

Common ways to split are by step in a flow, by kind of user, or simple case first and extra cases later. Pay a bill by card could come before pay a bill by bank transfer. Each slice gives a user something real.

Sometimes a team cannot size a story because something is unknown. A spike is a short piece of research with a fixed time limit, such as two days, to find the answer. Can the old system send data this way? The result is an answer, not a feature.

The common mistake is a story written from the team's side, such as as a developer, I want to tidy the code. That is a task, not a story, because no user gains from it directly. Ask who it helps and what they get.

![A tree in three rows titled epic, stories, tasks, each step down is smaller. The top box is the epic, pay bills in the app, sized in months. Under it three stories: add a payee, pay a bill, set a monthly payment, sized in days. Under pay a bill sit three tasks: screen, check and save, sized in hours.](https://learn.benibix.com/diagrams/agile-epic-stories.svg)

### Example: Jack splits a booking epic

Jack's team has an epic: book a table at a restaurant in Melbourne. The Developers say it is far too big for one 2-week sprint.

They split it into 5 stories. The first is book a table for tonight, with no extras. Before they size it, they run a 2-day spike. It checks if they can reach the restaurants' booking system at all.

**Words in this lesson:** [User Story](https://learn.benibix.com/term/business/user-story), [Epic](https://learn.benibix.com/term/business/epic), [Spike](https://learn.benibix.com/term/business/spike), [Story Splitting](https://learn.benibix.com/term/business/story-splitting)

**Question:** Which of these is written as a user story?

**Answer:** As a shopper, I want to save my basket, so that I can finish later. A user story names a kind of user, what they want and why. The others are a task, a vague wish and a goal for the team, with no user in them.

---

Source: https://learn.benibix.com/learn/business-agile/user-stories-and-epics
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-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
