Creating an Agile Road Map Using Story Mapping

Story Mapping: A Reliable Agile Tool

28 August 2013

Andrea Gigante
Tyche Consulting Ltd

We know that a prioritized backlog helps us understand what to do next, but sometimes it's difficult to grasp where we are and where we should go -- especially if we just dive into a big project that's been started, with hundreds of stories and/or issues already created.

To solve these situations, I have found it very useful to manage the road map and backlog with the help of a story map.

A user story map arranges user stories into a useful model to help understand the functionality of the system, identify holes and omissions in your backlog, and effectively plan holistic releases that deliver value to users and business with each release (from Jeff Patton's The New User Story Backlog Is a Map).

Where to start?

First we group the stories by application/theme/functionality and create the grid.

Horizontally, we can find the title for each grouped functionality; vertically, the main stories/issues related to each group.

The functionalities are prioritized from left (more important) to right (less important). Each group will then have the stories prioritized again vertically.

Personally, I don’t have any restrictions as to what I have in the grid. Here we can find stories with estimation, without, simple ideas not even confirmed, or technical improvements. Anything that helps understand the status of the project is welcome to be here.

Grouping and prioritizing

Once the stories are organized, we can start the surgical operation: slicing the list!

Creating the divisory line is not more difficult than the typical task of prioritizing a backlog, but personally I find the map even easier than managing a list of stories.

Given my experiences, I always try to have the next three sprints already prioritized (at a high level), but of course they can change radically if the necessity appears.

The story map is not static, but very much alive! I have found myself updating, prioritizing, adding, and removing stories every week.

For obvious business reasons, I have removed the content from it, but here you can see the same Agile road map in two different stages of the development:

First contact

After a couple of sprints

What are the differences between blue and red boxes? Colors can be used in different ways. For example, in this case I have used them to identify the main objectives of each sprint. But there is no straight rule; we can use colors for many different purposes. For example, use different colors:

  • Depending on the estimation (or if they are not estimated yet)
  • To identify complexity
  • To split between technical and business
  • Even to identify new functionality added in a second instance

I have personally found this tool really interesting and easy to manage. It allows both team and stakeholders to understand:

  • What we have done
  • What we are doing
  • What we are going to do

As a team, we are able to show the work we have accomplished in each sprint and establish an approach for the following ones.

There is a phrase in Mike Cohn's Agile Estimating and Planning that has had great value for me: "Agile planning balances the effort and investment in planning with the knowledge that we will revise the plan through the course of the project."

In my experience so far, I believe this tool is reliable, and I am sure it is going to be a "must" for any of my future projects. The stakeholders can easily grasp the velocity of the team and the status of the product, and they can help by introducing or suggesting new changes.

Clearly the idea and the process is not new; I base my work on the concept of Jeff Patton explained in the article "The New User Story Backlog Is a Map" (noted above). This is just my experience with it, how I have used it, and what I have changed from the original idea.

Are you using a similar tool?
What is your experience?
Do you have any suggestions?

Opinions represent those of the author and not of Scrum Alliance. The sharing of member-contributed content on this site does not imply endorsement of specific Scrum methods or practices beyond those taught by Scrum Alliance Certified Trainers and Coaches.

Article Rating

Current rating: 4.9 (8 ratings)


Glauber Queiroz de Oliveira, CSM, 8/29/2013 6:24:22 AM
Excellent experience Andrea. The use of roadmaps facilitates daily management activities. However, I have realized that this technique is not as well regarded by Brazilian executives. They always want something more simplistic. Have you ever experienced this? As this situation was handled?
Andrea Gigante, CSPO, 8/30/2013 1:32:13 PM
Hi Glauber, thanks for the comment.
So far I haven't experienced the feedback you have received.
Are you adding every single user story you have in your backlog?

Personally I found that by grouping stories or filtering minor ones, it is allowing both Business and the Team to grasp faster what the main functionalities are (ongoing, pending or already delivered).
I believe as well that different colours highlighting the main functionalities for each sprint could be of help.

My first roadmap was using colours to identify different phases... but I changed pretty fast to using colours identifying the Business priority (I found it really useful especially when you are in a project with several sprint behind your back and you need to review the history and/or possible future).

I hope it helps!
Lina Pullinger, CSM,CSPO, 9/3/2013 4:50:54 AM
Hi Andrea,
Thank you for the article, I have been looking for a good solution to do more effective knowledge transfer for backlog items and product roadmap, and am going to try and implement a similar approach like this with my team.
I also linked your article in my blog, I hope you don't mind.
Thanks again,
Andrea Gigante, CSPO, 9/3/2013 10:53:31 AM
Hi Lina
I do not mind at all, actually I am more than glad that you have found it helpful.
Personally I found story mapping really useful, but as commented I went trough different trial and errors... the beginning was interesting but it wasn't really ...perfect!
Good luck and let me know how it goes.
Mike Cohn, CST,CSP,CSM,CSPO, 9/12/2013 9:26:09 AM
Hi Andrea--
Thanks for sharing this. Story mapping can be a very effective way to communicate flow and priority on some projects.
I like how Patton describes the map as being read with "then" across the rows. It can be read with "First [first card] then [second card] then [third card...]". That combined with priorities down is what makes the map helpful. Thanks for sharing your experiences with it.
Andrea Gigante, CSPO, 9/13/2013 2:21:21 PM
Thanks to you Mike for your feedback.
I am finding Story Mapping as a great solution as visual roadmap for our Agile projects. It does help the whole team to understand our progress and where we are heading.
Srinath Ramakrishnan, CSP,CSM,CSPO, 9/19/2013 1:48:25 AM
Nice article. The prioritized boxes (stories) in different colours would be very easy to follow as well for all in the team.
Mohit Mishra, CSM, 12/10/2013 2:30:10 AM
I am reading your article now, but this exactly what I have been practicing, and believe me this works, organizing the stories vis-a-vis functionality is great but practical challenge is how you track the progress, and it needs to be done on the basis of weightage tagged with the each user story and to determine the criterion to flag the Functionality as red or blue on the basis of user story status
Gary Weis, CSM, 4/17/2014 4:48:38 PM
Andrea, I assume this is done in visio? Just checking incase there is a tool out there? Thanks - Gary
Jenny Nunemacher, CSPO, 7/1/2014 2:01:33 PM
I second Gary's question: What tool are you using as your repository for your maps? Stickies and whiteboards are functional, but temporary and not portable. I've used Excel because of the grid format, but moving cells around and detailed editing within cells can be a bit cumbersome.
Tristan Thevenin, 8/1/2014 3:49:02 PM
For those looking for tools supporting Story Mapping, have a look at It is free.

You must Login or Signup to comment.