User story template with examples (and the INVEST check)
A free user story template with examples: the 'As a, I want, so that' format, acceptance criteria, splitting big stories, and the INVEST checklist.
A backlog has 200 items. Most say things like "Export button," "Fix filters," "Admin page v2." In planning, the team spends the first ten minutes on each one working out who it's for and why it matters. A user story answers both before the meeting.
This guide gives a template, examples, and the INVEST check, from Atlassian's user story guide and Bill Wake's original INVEST article, checked on 16 November 2026.
The format
As a [persona], I want [goal], so that [benefit].
Atlassian breaks it down:
- As a [persona]: who you're building for. Not just a job title; a person the team understands.
- I want [goal]: their intent, not the feature. If it describes UI, it's missing the point.
- So that [benefit]: how this fits their bigger goal, and what problem it solves.
Atlassian notes the structure isn't required, but it helps define done. Teams should pick a structure and stick with it.
The template
## Story
As a [persona], I want [goal], so that [benefit].
## Acceptance criteria
- [Testable condition]
- [Testable condition]
- Scenario: [edge case]
Given [state] When [action] Then [result]
## Notes
- Out of scope: [what this story doesn't cover]
- Open questions: [question, owner]
- Links: [epic, designs, research]
Examples
SaaS admin
As a workspace admin, I want to see when each member was last active, so that I can remove access nobody uses before our security review.
Acceptance criteria:
- The members list shows a "Last active" column, sortable.
- Members never active show "Never."
- Only admins see the column.
E-commerce
As a returning customer, I want my saved address filled in at checkout, so that I can buy in fewer steps.
Acceptance criteria:
- The default saved address is preselected.
- I can choose another saved address or add a new one.
- Guests see an empty address form.
Internal tool
As a support agent, I want to see a customer's last five orders in the ticket view, so that I can answer order questions without switching tools.
Acceptance criteria:
- Orders show date, total, and status, newest first.
- Each order links to its detail page.
- If the customer has no orders, show "No orders yet."
Developer platform
As an API user, I want error responses to include a documentation link, so that I can fix integration problems without contacting support.
More criteria formats are in acceptance criteria examples.
The INVEST check
Bill Wake's checklist for a good story:
| Letter | Means | Ask |
|---|---|---|
| I | Independent | Can it be built in any order with other stories? |
| N | Negotiable | Is it the essence, with details left to work out together? |
| V | Valuable | Does it matter to the customer, not only to developers? |
| E | Estimable | Can the team size it? |
| S | Small | Does it fit in one sprint? |
| T | Testable | Do we know how to check it's done? |
Wake describes a story as a shared language between customers and developers, and stresses that it captures the essence rather than a contract of details.
Splitting stories
Atlassian says a story should be completable in one sprint; larger ones should be split or treated as an epic. Wake's advice is to slice vertically, like cutting through every layer of a cake, so each piece delivers something whole.
Ways to split:
- By workflow step: "upload a file" before "share a file."
- By user type: admins first, then members.
- By rule: basic discount codes, then minimum-order rules, then stacking.
- Happy path first, edge cases next.
Avoid horizontal splits like "build the database table" and "build the API," which deliver nothing a user can use on their own.
Mistakes to avoid
- The feature as the goal: "I want a dropdown" instead of "I want to choose a delivery date."
- No "so that": the reason is what lets the team find a better solution.
- The developer as the persona: "As a developer, I want to refactor" is a task, not a story.
- No acceptance criteria: nobody can say when it's done.
When AI agents build stories
If an AI coding agent implements the story, the "so that" and the acceptance criteria are what keep it on target. It will take the goal literally and fill gaps with guesses, so be specific, and mark open questions so it stops instead of choosing. See the PRD template for AI coding agents.
Where Lockstep fits
Stories change after they're written: an edge case is decided in standup, a scope cut in Slack. Lockstep captures decisions like these from documents, Slack, and pull requests, routes each to its owner for approval, and briefs the engineers and Claude Code sessions building the story.
See Lockstep for product teams.
Sources checked 16 November 2026
- https://www.atlassian.com/agile/project-management/user-stories
- https://xp123.com/invest-in-good-stories-and-smart-tasks/
Related reading
For what done means, see definition of done vs acceptance criteria. For planning sprints, see sprint planning with AI. For trackers to hold your stories, see Linear vs Jira.
Frequently asked questions
- What is the user story format?
- The common form is 'As a [persona], I want [goal], so that [benefit].' Atlassian describes the parts as who you're building for, their intent rather than the feature, and how it fits their bigger goal. The format isn't required, but it keeps the focus on the user's need.
- What does INVEST stand for?
- Independent, Negotiable, Valuable, Estimable, Small, and Testable. Bill Wake introduced it as a checklist for good user stories: they shouldn't overlap, the details are worked out together, they matter to the customer, the team can estimate them, they fit in an iteration, and they can be tested.
- How detailed should a user story be?
- Enough for the team to estimate and agree on acceptance criteria, and no more. Bill Wake describes a good story as capturing the essence, not the details, which are worked out between the customer and developers. Put the testable details in acceptance criteria.
- How do I split a big user story?
- Split vertically, so each smaller story still delivers something usable across all layers, rather than horizontally into a database story, an API story, and a UI story. Split by workflow step, by user type, by rule, or by happy path first and edge cases later.
- Can I use this user story template in Jira or Azure DevOps?
- Yes. Put the 'As a, I want, so that' sentence in the summary or description, acceptance criteria in a field or checklist, and link the story to its epic. The template is plain text, so it works in any tracker.
Keep reading