Skip to content

Stockertim Dictionary · Project management

User story

Also called user stories, story

In short

A short requirement written from a user's point of view, naming who wants something, what they want and why they want it.

  • Beginner
  • Concept
  • Checked

In detail

A user story captures a need in plain language, usually in the form: as a [type of user], I want [some goal] so that [some reason]. For example: as a tenant, I want to report a repair online so that I do not have to wait on the phone. The format keeps attention on the person and the outcome rather than on technical features.

A story is deliberately brief. It is a placeholder for a conversation between the team and the people who understand the need, and it becomes complete when acceptance criteria are added that say exactly what must be true for the story to be done. Stories are kept in a prioritised backlog and should be small enough to finish within one iteration.

Well-written stories are independent, negotiable, valuable, estimable, small and testable. Large stories, sometimes called epics, are split into smaller ones before work starts. Government service manuals recommend basing stories on evidence from user research rather than assumptions, so that the backlog reflects real needs.

In practice

Adaptive teams write stories on cards or in a backlog tool, discuss them in planning, and test them against their acceptance criteria during the iteration.

Watch out

  • A story without a reason, the so that part, loses its value for prioritising.
  • Stories written by the team about itself, such as as a developer, often hide technical tasks.

Learn it properly

Official sources

Facts last checked on 3 November 2026.

Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.

English