A user story is a short description of a need, written from the user’s point of view: "As [persona], I want to [action], so that [benefit]". It comes with acceptance criteria that say when the story is done, often in the Given, When, Then format. The INVEST checklist (independent, negotiable, valuable, estimable, small and testable) helps check whether a story is ready for the backlog.
How to use
- Enter the feature or epic and the persona, as it fits after "As...".
- Write one requirement per line, starting with the verb; if you like, add the benefit after "so that".
- Fill in the overall benefit and the business rules that apply to every story.
- Read each story with its criteria, the INVEST checklist and the splitting hints for those that look big.
- Export as Markdown or CSV to take to Jira or to the team backlog.
What each field asks for
| Field | What to enter |
|---|---|
| Feature or epic | What is being built, in a few words. |
| Persona | Who uses it, as it fits after "As...". |
| Requirements | One per line, starting with the verb. Each becomes a story. |
| Overall benefit | Used in stories that do not state a benefit (optional). |
| Business rules | Limits that apply to every story (optional). |
Example
For the automatic payment reminder of a fictional app, the persona is a freelance designer who issues invoices in the app. Four requirements become four stories, each with two to four acceptance criteria. Two pass every INVEST check. The one that turns on reminders for all invoices gets the hint to start with one case, and the one that combines seeing and exporting the list gets the suggestion to move "export" into its own story. The two business rules become shared criteria.
When to use
- After the PRD, to turn requirements into backlog items the team can estimate.
- Before refinement, to arrive with acceptance criteria and not just titles.
- To review an old backlog and find stories that are too big or have no clear benefit.
- To teach newcomers to write stories in a consistent format.
Frequently asked questions
What is a user story?
It is a need described from the user’s point of view, in the format "As [persona], I want to [action], so that [benefit]". It is an invitation to a conversation, not a complete specification.
What are acceptance criteria?
They are the conditions that say when the story is done. The Given, When, Then format describes a context, an action and a result you can check, which makes testing easier and avoids arguments at the end of the iteration.
What does INVEST mean?
It is a quality checklist: independent, negotiable, valuable, estimable, small and testable. The tool checks each letter with simple rules and says what to adjust when one fails.
How do I split a large story?
Move different actions into their own stories, split broad verbs such as "manage" by operation and start with one simple case before covering them all. Each part must still deliver value to the user.
What is the difference between a user story and a requirement?
A requirement says what the system must do. A story says who needs it and why, and leaves room for the team to propose the best solution. One requirement can become one or several stories.
Does the AI write the stories for me?
Without AI, the tool already builds stories, criteria and the checklist from rules. When AI is switched on, it only improves the wording and suggests extra criteria; the decision stays with the team.