# Story Maps and Releases

> How a user story map lays stories along the steps a user takes. How release planning cuts the map into slices and says about when each one ships.

**Course:** [Agile, Scrum and Kanban](https://learn.benibix.com/learn/business-agile)  
**Time:** 11 min

**After this lesson you can:**

- Build a simple story map
- Slice a first release across it
- Forecast a release with velocity

## How to plan a release with a story map

User story mapping lays out stories along the path a user takes through a product. The top row is the backbone: the big steps, such as find, choose, pay and track. Under each step hang its stories, most needed at the top. A food app might have 4 steps and 30 stories under them.

A flat backlog hides the shape of the product. A map shows it. You can see at once that a team has 12 stories for paying and none for tracking an order. The gap would be easy to miss in a list of 200 items.

Lines across the map cut it into releases. The first slice takes the top story under every step, so a user can go from start to end, however simply. That thin first slice is called the walking skeleton. Search by name, pick a dish, pay by card and see status is enough to be useful.

Release planning decides what goes into a release and about when it ships. Add up the size of the stories in the slice and divide by the team's velocity. A slice of 105 points with a velocity of 21 is about 5 sprints.

Either the date or the scope can be fixed, not both. If the date is fixed, the slice shrinks to fit. If the scope is fixed, the date moves. Saying both are fixed only means something else gives way, usually quality.

The plan is checked every sprint. Velocity shifts, stories are added and some turn out bigger than sized. A release plan that is never updated is a guess dressed as a promise.

The common mistake is building the map layer by layer, every story for find before any for pay. Then nothing works end to end for months. Slice across the whole map, and each release is a product someone can use.

![A story map titled backbone on top, releases sliced across. The backbone row has four steps: find, choose, pay and track. Under them, a first slice marked release 1, walking skeleton: search by name, pick a dish, pay by card, see status. Below that, release 2: filter by price, add notes, save a card, live map. At the bottom, later: reviews, split the bill, rate the rider.](https://learn.benibix.com/diagrams/agile-story-map.svg)

### Example: Emma plans a fixed launch date

Emma's team must launch a ticket app in 6 sprints, for a festival in Edinburgh. The first two slices of the map add up to 150 points, and velocity is 20.

That is 7 and a half sprints, so the date cannot hold both slices. She keeps the first slice, 70 points, and moves 4 stories from the second. The new total is 115 points, which fits in 6 sprints with 5 to spare.

**Words in this lesson:** [User Story Mapping](https://learn.benibix.com/term/business/user-story-mapping), [Release Planning](https://learn.benibix.com/term/business/release-planning)

**Question:** A release holds 120 points and the team's velocity is 20. About how many sprints will it take?

**Answer:** 6 sprints. Divide the size of the release by the velocity. 120 points at 20 a sprint is about 6 sprints, and the plan is checked again every sprint.

---

Source: https://learn.benibix.com/learn/business-agile/story-maps-and-releases
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
