A flat backlog loses the narrative. You end up with hundreds of stories, nobody can see the product shape, and prioritization becomes guesswork.
Story mapping, developed by Jeff Patton, fixes this. The map is two-dimensional:
- Horizontal axis: the user journey — what users do, in time order
- Vertical axis: the depth of functionality — must-have vs. nice-to-have for each part of the journey
"A way of working with user stories to identify those that deliver the greatest value to the end user." — from User Story Mapping notes (Jeff Patton)
The map shows not just what to build, but why each piece matters in relation to the whole. Releases get sliced horizontally: the first release contains the minimum set of tasks across the full user journey to deliver a thin but complete experience. That's your MVP slice.
I've used story mapping to build roadmaps on several projects — it's one of the most effective tools for getting stakeholders to agree on scope, because they can see the trade-offs instead of arguing about them in the abstract.
The output isn't a replacement for the backlog. The map helps you understand and order the backlog — especially when you have enough stories that you've lost the thread of what you're actually building.
Exam tip: A story map is a planning tool, not a Scrum artifact. The map doesn't live in the sprint; the items extracted from it do. Exam questions may test whether you know the difference between a story map, a backlog, and a release plan.