User story mapping

Also called story mapping.

Business basics4min read

User story mapping is a product-planning technique that arranges user activities in the order people do them, with smaller stories underneath. Teams use the map to see the whole experience, find gaps and choose what belongs in each release.

Key takeaways

  • Read across the map to follow the user's journey. Read down to see more detailed tasks and lower-priority options.
  • A release should support a useful end-to-end journey, rather than finish every feature in one area.
  • Mapping helps a team choose scope. It does not replace estimates, acceptance criteria or customer research.
  • For a startup, its main value is exposing what you can leave out without breaking the experience you want to test.

How user story mapping works

Jeff Patton developed and popularized the technique. It gives teams a shared picture that a long, ordered backlog often lacks.

Start with one user and one goal, such as a customer booking a fitness class. Mixing customers, instructors and administrators into the same journey makes the map harder to follow.

  1. Write the main activities across the top: find a class, choose a session, reserve a place, get confirmation. This sequence forms the map's backbone.
  2. Put smaller tasks and user stories underneath each activity. Under "reserve a place," these might include booking one seat, paying online and joining a waiting list.
  3. Within each activity, put essential stories above optional ones.
  4. Draw horizontal release boundaries across the map. The first release should contain enough stories to complete the chosen journey.

Write acceptance criteria separately for the stories selected for development. "Reserve a place" is not specific enough until the team agrees what happens when the class is full or the customer submits twice.

Cutting a booking prototype from 22 to 8 engineering-days

A team is planning a class-booking prototype. Accounts, class inventory and messaging services already exist. The figures below are illustrative implementation estimates, excluding design, testing and contingency.

ReleaseFind a classChoose a sessionReserve a placeGet confirmation
First releaseClass list: 2 daysAvailable times: 3 daysBook one seat: 2 daysConfirmation email: 1 day
Later releaseSearch filters: 3 daysRecurring bookings: 5 daysOnline payments: 4 daysSMS reminders: 2 days

The arithmetic:

  • First release: 2 + 3 + 2 + 1 = 8 engineering-days.
  • Deferred features: 3 + 5 + 4 + 2 = 14 engineering-days.
  • Everything together: 8 + 14 = 22 engineering-days.

The first release still lets someone complete a booking. Building every search feature first would consume time without producing a usable booking flow.

Eight engineering-days is not an eight-day launch promise. The useful result is a smaller scope that can test booking completion before the team spends effort on payments and recurring sessions. It cannot yet test willingness to pay through the product.

What the Scrum Guide says

The Scrum Guide, November 2020, describes the Product Backlog as an emergent, ordered list of what is needed to improve the product. It does not prescribe story mapping or a particular format for backlog items.

A story map is therefore an optional planning aid, not a Scrum artifact or event. Link selected stories to the team's backlog rather than maintaining two competing versions of the work.

What to question in a map

Challenge a map whose top row consists of "database," "API" and "frontend." Those describe system components, not what a user is trying to accomplish. Technical work still matters, but it should support the journey rather than replace it.

Also question a first-release boundary that includes every requested feature. Ask: "Which user outcome fails if we move this story below the line?" If none does, it is a candidate for deferral.

Story map vs. backlog vs. journey map

ToolMain organizing principleBest question it answers
User story mapUser activities, supporting stories and release slicesWhat belongs in a useful release?
Product backlogOrdered product workWhat should the team work on next?
Customer journey mapCustomer actions, touchpoints and experienceWhere do customers encounter friction?

Questions people ask

What is a user story in Scrum?

A user story describes a small outcome from the user's perspective. A common format is "As a [user], I want [capability], so that [benefit]." On a story map, it sits beneath the activity it supports. The sentence starts a discussion; acceptance criteria make the expected behavior testable.

Which is bigger, an epic or a story?

An epic is larger. Teams use it for a body of work that needs splitting into smaller stories. Terminology varies, so do not assume every activity across a story map's backbone must be an epic. The map organizes the experience; epic labels organize work.

Related terms

Sources

  1. Jeff Patton, O'Reilly Media, User Story Mapping: Discover the Whole Story, Build the Right Product, 2014.
  2. Agile Alliance, glossary entry, "Story Mapping."
  3. Ken Schwaber and Jeff Sutherland, The Scrum Guide, November 2020.