WHAT IS THE STORY MAP?

Story map is a representation of the backlog in two axes: the horizontal axis which represents the customer journey, and the vertical axis which represents the user stories.

The story mapping is a workshop in which all team members participate to dissect all the different phases of a customer journey, to determine the action features appropriate to each of these phases, and to sort them by theme and priority.

Story Map makes it possible to precisely define the user need for the product.

You can create a story map to meet two essential objectives:

• Carry out the customer journey for a new product and determine all of the product’s features;
• Renew the functionality of products that already exist;

The importance of the story map:

Story mapping is important to define and develop the necessary functionalities of a product when there is a need to structure the planning of deliveries (like MVP). The importance of this workshop lies in writing a first release plan for the teams. The defined functionalities can be the subject of a Backlog product, and therefore the story map is an essential tool for planning different sprints.

How to organize a story map workshop?

The story map workshop is generally organized by the Product Owner or Agile Coach, with all team members.

How to lead the story mapping workshop? [A proposal] 

Step 0: Prepare your workshop

Consider preparing the data you will need in your workshop, such as: personas that will help you determine the customer journeys. 

You will need a large piece of paper (2 to 3 meters), post-its, markers, and a timer.

Step 1: Present the workshop to the participants (10 minutes)

Present the workshop while highlighting the different reasons that pushed you to organize it, and also the expected objectives of this workshop.

Step 2: Imagine the customer journey (45 minutes)

All participants must contribute by their ideas and opinions and discuss all decisions.

Step 3: Complete the mapping (45 minutes)

Once the major steps are validated and organized in chronological order, complete the mapping by adding the corresponding small steps (the user stories) under each major step (activities or Epics).

Step 4: Prioritize features (25 minutes)

In this step, you draw multiple horizontal axes to define multiple areas. These represent the priority user stories to be developed in the first version of the product, that is to say the release, and those that are less important and can be delivered in the second or third release.

And therefore, this workshop also allows you to build the MVP and to make a first version of future releases.

After the story mapping workshop, the team has a clear idea about the next sprints. Thanks to this workshop, the team can now begin the product development.

Conclusion : 

Experts recommend updating the story map regularly, especially when making changes to your product.

What do you think? Get in touch via email to talk more!

Check out our posts on LinkedIn.

MORE YOU KNOW, MORE YOU GROW :

Reading more ? Check out other interesting topics !