User Story
What is a User Story?
A user story is a short description, written from a user's point of view, of an outcome they want from a product and the reason for it, often in the form "As a..., I want... so that...". It opens a conversation rather than replacing a spec.
Updated November 2026 · 4 min read
A user story is a short, plain-language description of something a user wants to do with a product, and why. It is written from the user's point of view rather than the system's, and it describes an outcome rather than a design. The most common format is "As a [type of user], I want [some goal] so that [some reason]."
User stories came out of Extreme Programming in the late 1990s and spread with agile methods such as Scrum. The "As a ... I want ... so that" template is usually credited to a team at the UK company Connextra around 2001. Their purpose is to keep a team focused on the person it is building for and to start a conversation about the work, not to replace that conversation with a specification. Ron Jeffries summed this up as the three Cs: the card, the conversation and the confirmation. Mike Cohn's book User Stories Applied (2004) did much to standardize how teams write and use them.
Parts of a user story
- The user. A specific role or persona, such as "a finance manager approving expenses," not "the user" in general.
- The goal. What that person wants to do, stated without prescribing a solution.
- The reason. The benefit or outcome. This is the part teams most often skip, and the part that helps them find a better solution than the one first imagined.
- Acceptance criteria. The conditions that must be true for the story to be done. See acceptance criteria.
The INVEST checklist
Bill Wake proposed the INVEST acronym in 2003 as a test of whether a story is well formed. It is still one of the most common checklists for story quality.
| Letter | Quality | What it means in practice |
|---|---|---|
| I | Independent | The story can be built and released without waiting on another story. |
| N | Negotiable | The details are open to discussion between the team and the product owner. |
| V | Valuable | Completing it delivers something a user or customer would notice. |
| E | Estimable | The team understands it well enough to size it. |
| S | Small | It fits comfortably within a single sprint or iteration. |
| T | Testable | There is a clear way to confirm it works. |
User story vs. epic vs. task
An epic is a large body of work that is too big for one iteration and is broken down into several user stories. A task is a unit of technical work, such as "add an index to the invoices table," that a developer does to complete a story. Stories sit in the middle: small enough to finish in an iteration, big enough to deliver value on their own. When a story is too big, teams use story splitting to break it into thinner slices, each still useful to a user.
How to write a user story
- Start from a real user need. Use research, support tickets or interviews, not internal guesses.
- Name a specific user. The more specific the role, the easier it is to judge the right solution.
- State the goal and the reason. Keep implementation details out of the story itself.
- Add acceptance criteria. Many teams use Given/When/Then statements so criteria can be turned into tests.
- Discuss it with the team. Refine the story together during backlog refinement, and split it if it will not fit in an iteration.
- Check it against a definition of ready. Only pull it into a sprint when the team can start without major open questions.
User story examples
Consider a hypothetical expense-management app. A weak story reads: "As a user, I want a CSV export button." It names no real user, prescribes a solution and gives no reason.
A stronger version reads: "As a finance manager, I want to get approved expenses into our accounting system each month so that I can close the books without retyping data." The acceptance criteria might be: given 200 approved expenses in March, when the manager runs the monthly export, then all 200 appear with date, amount, category and approver, and amounts match the app's totals to the cent. Discussing the story, the team learns that most customers use one of two accounting systems, and decides a direct integration for those two plus a CSV fallback serves the need better than a button alone.
Other examples of well-formed stories:
- "As a new employee, I want to submit my first expense from my phone so that I can get reimbursed for travel during my first week."
- "As an approver, I want to see which expenses break policy before I approve them so that I do not have to check each receipt by hand."
Common pitfalls
- Writing tasks in story format. "As a developer, I want to refactor the API" is a task. Stories should describe value to a user or customer.
- Dropping the "so that." Without the reason, the team cannot judge trade-offs or suggest better solutions.
- Treating the story as a full specification. A story is a placeholder for a conversation. Detail belongs in acceptance criteria and in what the team agrees together.
- Stories that are too big. A story that takes the whole sprint is risky. If it cannot be finished in a few days, split it.
- Generic users. "As a user" hides who the work is for, and different users often need different things.
User stories are the working unit of a product backlog. Arranging them along the user's workflow with user story mapping helps plan releases, and teams often size them with story points and confirm completion against a definition of done.
Frequently asked questions
What does the INVEST acronym mean for user stories?
INVEST is a checklist proposed by Bill Wake in 2003 for judging whether a user story is well formed. A good story is Independent of other stories, Negotiable in its details, Valuable to a user or customer, Estimable by the team, Small enough to fit in one sprint, and Testable, with a clear way to confirm it works.
What is the difference between a user story, an epic and a task?
An epic is a large body of work too big for one iteration, broken down into several user stories. A task is a unit of technical work, such as adding a database index, that a developer does to complete a story. User stories sit in between: small enough to finish in an iteration and large enough to deliver value on their own.
Where does the "As a, I want, so that" user story format come from?
The "As a [type of user], I want [goal] so that [reason]" template is usually credited to a team at the UK company Connextra around 2001. User stories themselves came out of Extreme Programming in the late 1990s and spread with agile methods such as Scrum. Mike Cohn's 2004 book User Stories Applied did much to standardize how teams write them.
How do you write acceptance criteria for a user story?
Acceptance criteria list the conditions that must be true for a user story to be done. Many teams write them as Given/When/Then statements so they convert directly into tests, for example: given 200 approved expenses, when the manager runs the monthly export, then all 200 appear with matching amounts. Detail belongs in the criteria and team discussion, not the story sentence.