User story mapping is a technique developed by Jeff Patton (read more) and is often used to break down a larger initiative into smaller parts that can then be prioritized in a backlog.
Here is an example of how you can create a story map.
Since we in this type of roadmap work our way down to User Stories, it becomes relatively detailed, if we compare it to other types of roadmaps. I think this type is particularly suitable when we have to build something from scratch, where we already have extensive domain knowledge and good customer/user insights.
Above you can see an example of what a User Story map can look like. In this example, Release 1, 2 & 3 are used, but as a suggestion, you think prio 1, 2 & 3 instead and release continuously.
The blue top row contains overall activities that the user or customer performs in the product or service. They are oriented according to the value flow in the service or product.
To create even more clarity, you can group these activities by user or customer. These groups are highlighted in orange and are at the top.
Each blue post-it is then broken down into yellow user stories which are in priority order from top to bottom.
Make sure your user story map is clearly visualized, e.g. posted on a wall where everyone can see it or on a digital board (miro, mural etc) where you can easily co-create and change. During the course of the work, you work in priority order and mark which user stories are in progress (WIP in the picture), ready (Done) and, as a suggestion, if they are blocked in some way. This provides a simple and clear picture of progress and status both for the team(s) and for other stakeholders who want to be able to follow the progress.
|Focus on||Priority och status|
|Used e.g. for||Teams / Product department|
|Owned by||Product owner/Product manager|
|Content size||User stories and groupings of them|