User story

Business basics4min read

A user story is a short description of something a person wants to accomplish with a product and why it matters to them. Product and software teams use stories to discuss needs, plan work and agree on what success looks like.

Key takeaways

  • A story describes a user's goal, not just a feature or a developer's task.
  • The common format is "As a [user], I want [goal], so that [benefit]." It is a prompt, not a required formula.
  • Acceptance criteria turn the story into something the team can test.
  • For a startup, the benefit should connect the work to a customer problem. It is still a hypothesis until customers use the result.

How a user story works

A story starts with a person, a goal and a reason. The team then discusses the details and agrees on the conditions that must be met.

For example, "Build an export button" names a feature. "As a bookkeeper, I want to export invoices so that I can reconcile payments" explains who needs it and why. That context helps the team decide what to build, including whether a button is the right solution.

Keep a story small enough to finish and test within the team's delivery cycle. Split a large goal into useful outcomes, not separate stories for the database, interface and testing.

Cutting support time with self-service invitations

Here is a sample backlog entry:

As a workspace owner, I want to invite teammates by email so that we can start working together without contacting support.

Its acceptance criteria could include:

  • An owner can send an invitation to a valid email address.
  • The recipient can accept and join the correct workspace.
  • A person without invitation permission cannot send one.
  • A failed invitation displays an error and allows another attempt.

For a planning example, a startup adds 50 workspaces a week. Each currently needs one 10-minute support interaction to add teammates. The team targets self-service invitations for 40 workspaces; the remaining 10 still need support.

MeasureBeforeTarget after release
New workspaces per week5050
Workspaces needing invitation support5010
Minutes per support interaction1010
Weekly support time500 minutes100 minutes

The target saving is (50 − 10) × 10 = 400 minutes, or 6 hours 40 minutes per week.

For a founder handling support, that is time recovered for other work. But the calculation is a forecast, not proof. After release, measure successful invitations and support requests. Shipping the feature does not establish that it delivered the benefit.

What the Scrum Guide requires

The 2020 Scrum Guide describes the Product Backlog as an ordered, evolving list of what is needed to improve the product. It does not require user stories or the "As a..." format.

A user story is one way to describe a backlog item, not a Scrum rule. Teams still need enough detail to understand and complete the work.

What to question

Also question a story that bundles several independent goals. Smaller stories help the team release something useful sooner. But do not force every technical maintenance task into a fictional customer narrative.

User story vs. task

User storyTask
Main questionWhat does the user need, and why?What work must the team do?
Invitation exampleInvite teammates without contacting supportBuild the invitation email template
CompletionAgreed acceptance criteria are satisfiedThe specified work is finished

One story can require several tasks. Completing one task does not necessarily deliver the story's outcome.

Questions people ask

What is in a user story?

The core is a user or role, a goal and a benefit. Teams often attach acceptance criteria, designs or other notes. The short statement opens the discussion; it does not replace every requirement.

What are the 3 C's of user stories?

Ron Jeffries describes them as Card, Conversation and Confirmation. The card records the idea, the conversation develops shared understanding, and confirmation establishes how the team will check that the story works. The card can be a digital backlog item.

What are some good user story examples?

"As a subscriber, I want to cancel online so that I can stop future renewals." Another is: "As an account owner, I want to export invoices so that I can reconcile my books." Both identify a person, an action and a reason.

What is a user story vs. task?

A story describes a useful outcome from the user's perspective. A task describes work needed to deliver it. "Invite a teammate" is the outcome; "Create an invitation API endpoint" is an implementation task.

Related terms

Sources

  1. Agile Alliance, "User Stories," Agile Glossary.
  2. Ron Jeffries, "Essential XP: Card, Conversation, Confirmation," August 30, 2001.
  3. Ken Schwaber and Jeff Sutherland, The Scrum Guide, November 2020.