User story mapping as a tool for teams
User story mapping is an essential tool for an agile team. It helps to better understand the audience’s needs and organise the work on the product. This approach also improves overall productivity by clearly prioritising tasks.
A story mapping is a visual representation of a user’s actions to achieve a specific goal. It is expressed in two dimensions. The first shows the sequence of steps, shown from left to right at the top of the map. The second shows alternative ways in which the user can achieve the goal. The options are displayed from top to bottom.
Such a map gives a general understanding of the product and visualises the user’s needs. It will be a valuable tool in the project implementation process. In this case, the map should be created at the beginning of the work, which will help to outline the overall picture. However, it should be noted that the map will not contain detailed plans for this option. It can also be used when the team is working on extending the existing product’s functionality. This method is ideal for creating or improving an e-commerce site. The map can be used as a wish list for the product.
Where to start
The first step in creating a story map is to set a goal. You need to focus on a single but significant goal, or the minimum viable product, the MVP. This goal can be achieved within about three months. In most cases, this is enough time to see progress, even if it is not very tangible.
A product itself can also be an essential target. The product itself can be a significant goal, and this is often the case in Scrum teams where the project is within three months of completion. There are times when the map goal choice may be less significant. For example, if you need to complete several tasks in a given time. In this case, however, you should create separate maps for different goals.
Once the goals have been set, the team begins to work with the dimensions:
- The first dimension shows the sequence of user tasks.
- The customer or product owner involves all project participants in the discussion.
- Together, they define work steps and actions for each of them.
- The map is supported by a note showing the sequence of steps.
- All notes are written in the order of the steps.
The second dimension presents alternatives for task implementation. In this case, the priority principle is respected: the most important cards with alternatives are at the top. The second dimension has a vertical reading order.
An important point when using story cards is to discuss all stages of the process with the participants. Close communication helps to set the right priorities.
