In 30 seconds
- Template: As a [user], I want [goal], so that [reason].
- A story is a placeholder for a conversation, not a full spec.
- Good stories are small, valuable and testable.
The template
As a returning customer, I want to save my card details, so that checkout is faster next time.
The three parts name who benefits, what they need, and why it matters. The "so that" is the most skipped and most important part, because it lets the team suggest better solutions.
The 3 Cs
- Card: a short written description.
- Conversation: the discussion that fills in details.
- Confirmation: the acceptance criteria that prove it works.
Splitting big stories
A story too big for one sprint is often called an epic. Split it by workflow step, by business rule, by type of user, or by happy path first, edge cases later. Each slice should still deliver something a user can see. Check slices with INVEST.
Where stories came from
User stories grew out of Extreme Programming; the "As a… I want… so that…" template became popular in the early 2000s.
Myth vs reality
The AI angle
Stories handed to AI agents need extra precision: relevant code areas, constraints and executable acceptance criteria. Keep the user and the value; they still guide good decisions.
FAQ
Who writes user stories?
Anyone can, but the Product Owner owns them in the backlog.
How big should a story be?
Small enough to finish in a few days, well within one sprint.
What's the difference between a story and a requirement?
A requirement tries to be complete; a story is deliberately short and invites conversation.