StackLift
All terms

Glossary

User Story

A short note of a feature from the user's view: as a user, I want a goal, so that a benefit.

A user story is a short description of a feature written from the viewpoint of the person who needs it, commonly as: as a type of user, I want a goal, so that a benefit. It starts a conversation and is paired with acceptance criteria that define when it is done.

Good stories are small, testable and valuable to a user. Large goals are called epics and are split into stories that fit in one sprint.

Stories sit in a prioritized backlog and are sized, often in story points, so a team can plan what fits in each sprint.

Start in 60 seconds

Put this to work on your project.

Get an AI-assisted, architect-reviewed scope, cost range, and timeline. Free, no login.

The complete guide

User Story: the complete guide

Updated November 18, 2026 · Published by , Founder, StackLift AI. Written with AI assistance; how we make content.

Short answer

A user story is a short description of a feature from the point of view of the person who wants it, usually written as: as a type of user, I want a goal, so that a benefit. It keeps the team focused on the user's need, and it is paired with acceptance criteria that say when the story is done.

What is a user story?

A user story is a small, plain-language statement of something a user needs. It describes the result for the user, not the technical work. The classic template is: As a [user], I want [goal], so that [benefit].

The story is a starting point for a conversation, not a full specification. The detail comes from talking with the team and from the acceptance criteria attached to it.

What does a good user story look like?

Take a customer portal. A weak story says: build a password reset. A better one says: as a customer who forgot my password, I want to reset it by email, so that I can get back into my account without calling support.

One story with its acceptance criteria
PartExample
StoryAs a customer who forgot my password, I want to reset it by email, so that I can sign in without calling support.
CriterionGiven a registered email, when I request a reset, then I receive a link that works once.
CriterionGiven an expired link, when I open it, then I see a clear message and can request a new one.
CriterionGiven an unknown email, when I request a reset, then the page does not reveal whether the account exists.

How do you know a story is well written?

A widely used check is INVEST. A good story is independent, negotiable, valuable, estimable, small and testable. It is not a rule to follow blindly, but stories that fail several of these usually cause trouble.

  • Independent: it can be built without waiting on many other stories.
  • Negotiable: details can be discussed, so it is not a fixed order.
  • Valuable: a user or the business gets something from it.
  • Estimable: the team can size it. See story points.
  • Small: it fits inside one sprint.
  • Testable: you can tell when it works, which is what acceptance criteria are for.

User stories, epics and tasks: how they fit together

An epic is a large goal that is too big for one sprint, such as customer self-service. It is split into stories. Each story is split into the tasks engineers do, such as building the endpoint, the screen and the tests.

Stories sit in a prioritized backlog. The team pulls the top ones into a sprint. Splitting large stories until they are small is one of the most useful habits in agile work.

How do you write user stories for a new project?

  1. List the types of user: customer, admin, support agent, and so on.
  2. For each, list the goals they have, from discovery conversations, not guesses.
  3. Write each goal as a story with its benefit.
  4. Split any story that is too large for one sprint.
  5. Add acceptance criteria, including the error and edge cases.
  6. Order the backlog by value and risk, and review it with the people who will use the product.

Common user story mistakes

  • Writing technical tasks as stories, such as set up the database, which no user would recognize.
  • Leaving out the so-that part, which hides why the story matters.
  • Stories so large that nobody can say when they are finished.
  • Skipping acceptance criteria, so testers and developers guess differently.
  • Treating the story as a contract and refusing to talk about it.

Stories also feed the product requirements document and the estimate. StackLift's AI Scope Sprint produces user stories as part of its scoping plan, and the free estimate is a quick way to see your features laid out.

How do user stories connect to estimates and delivery?

Stories are the unit most teams use to plan. The backlog is the list of stories in priority order, and each story is sized so the team can see how much fits in a sprint. Sizing in story points compares complexity instead of guessing hours.

Because each story ends in something a user can do, progress is easy to see. A client can look at the finished stories and check them against the criteria. If a story keeps growing as it is discussed, that is a signal to split it, or to ask whether the underlying need is understood.

What formats can a user story take?

The classic template is: as a (type of user), I want (an action), so that (a benefit). The benefit clause is the most important part, because it tells the team why the story exists and lets them suggest a simpler way to reach the same goal.

Common ways to write a story
FormatLooks likeBest for
Role, goal, benefitAs a store manager, I want to export last month's orders, so that I can reconcile paymentsMost product backlogs
Job storyWhen a payment fails, I want to retry it quickly, so I can still complete my purchaseStories driven by a situation more than a persona
Given, when, thenGiven I am signed in, when I open orders, then I see only my ownAcceptance criteria that testers can run; see acceptance criteria
Plain statementAdmins can deactivate a user without deleting their historySmall teams that value brevity

The format matters less than the conversation behind it. A card is a reminder to talk, not a replacement for talking.

What do user stories look like in different products?

Concrete examples make the template easier to apply. Each story below is small enough to finish within one sprint.

  • Online store: as a shopper, I want to save items for later, so that I can come back when I am ready to buy.
  • Clinic booking: as a patient, I want to pick an appointment time from the open slots, so that I do not need to call.
  • Field service: as a technician, I want to see today's jobs on my phone, so that I know where to go next.
  • Internal tool: as a finance lead, I want to approve invoices over a set limit, so that large payments get a second review.
  • AI feature: as a support agent, I want a suggested reply with its source, so that I can check it before sending.
  • Marketplace: as a seller, I want to see my payout schedule, so that I can plan my cash.

Each one names a real person, an action and a reason. None says which database, framework or button to use; that is for the team to decide.

How do you split a story that is too big?

A story that cannot be finished in one sprint is usually an epic in disguise. Split it so that each piece still delivers something a user can notice, rather than cutting by technical layer, such as database first and screen later.

Ways to split a story
Split byExample
Workflow stepSearch for a flight, then choose a seat, then pay
Business rulePay by card first; add discount codes later
User roleCustomers can see orders; admins can edit them later
Data variationImport one file format now; add the others after
Happy path and exceptionsSuccessful payment first; failed payments and refunds next
Quality levelSimple search now; filters and sorting later

After splitting, check each piece against the question: could we demo this on its own? If not, the cut is probably technical, not user-facing.

User story vs. requirement, use case and task

How the terms differ
TermWhat it isHow it differs from a user story
RequirementA statement of something the system must doOften written as a command with little context; a story adds who and why
Use caseA step-by-step interaction between an actor and the systemMore detailed and formal; a story is lighter and sparks conversation
TaskA unit of work for one person, such as write the API endpointA task is about building; a story is about value
EpicA large body of work covering many storiesToo big for one sprint; split into stories
Product requirements documentA written description of what to build and whyGives the wider picture that stories break down

They work together. A short PRD explains the goal, the backlog holds the stories, and acceptance criteria say how each one is checked. The PRD template shows one layout.

How do you know your backlog of stories is in good shape?

  • The top of the backlog is ready: stories are small, clear and have acceptance criteria.
  • The team rarely needs to ask what a story means once the sprint starts.
  • Most stories are finished inside a single sprint.
  • Stories are ordered by value and risk, not by who shouted loudest.
  • Stakeholders recognize their needs in the stories and see them in demos.
  • Few stories come back as defects after they were called done.

If many stories are unclear or oversized, spend a short session each week refining the next few sprints' worth of work. This is called backlog refinement, and it saves far more time than it costs.

What tools hold and manage user stories?

Teams keep stories in Jira, Linear, Azure DevOps, GitHub Projects, Trello, ClickUp or Notion, and often use story mapping boards in Miro or FigJam to see the whole journey. Pick something that links each story to its acceptance criteria, designs and code changes, so anyone can trace what was built and why.

What do user stories mean for cost and timeline?

Stories are the unit most teams size and schedule, so their quality drives how reliable the plan is. Clear stories with acceptance criteria give tight estimates. Vague ones hide work, and the surprise arrives mid-project as a change request. The number and complexity of stories, plus integrations and compliance needs, shape the total effort.

Most first versions take 6–16 weeks depending on scope. The free estimate turns your feature list into sized work, and the MVP feature prioritization playbook helps decide which stories go first.

Questions people ask

Who writes user stories?

Usually the product owner or product manager, with input from the team and users. Anyone who understands the user's need can draft one, and the team refines it together.

What is the difference between a user story and a requirement?

A traditional requirement states what the system shall do. A user story states what a user needs and why, and leaves the details open for discussion. Both can describe the same feature.

How detailed should a user story be?

Short enough to read in a moment, with acceptance criteria covering the details. If you need paragraphs to explain it, split it or move the detail into the criteria.

Do user stories work outside Scrum?

Yes. They are common in Kanban and other agile approaches, and many teams use them without any fixed framework because they are simply a clear way to describe needs.

How do user stories relate to cost?

Stories are the unit teams size and plan. At StackLift, pricing is by deliverable complexity in story points, not hours, so clear stories make the estimate firmer.

Who writes user stories?

Anyone can draft them, but the product owner is accountable for the backlog. The best stories come from a conversation among the owner, developers, designers and testers, not from one person alone.

How detailed should a user story be?

Detailed enough that the team can estimate and build it without guessing, and short enough to leave room for conversation. Acceptance criteria hold the specific details and edge cases.

Are user stories only for agile teams?

They come from agile practice, but any team can use them to describe needs from the user's point of view. They are especially useful when requirements will change as you learn.

How many user stories does a project need?

It depends on scope. A first version may have dozens, and you only need detail for the next few sprints. Keep far-future work as larger epics until it gets closer.

Sources

Sources and further reading

The standards, rules, research and official documentation this page draws on.