70 – Story Mapping

Collaborative games or workshops aim at promoting cooperation within your team and provides it with a common goal so that all the members participating in the game can work together.

Technique's info

  • Level:  
  • Number of people:
  • Duration:
  • Categories:
Share on facebook
Facebook
Share on pinterest
Pinterest
Share on whatsapp
WhatsApp
Share on print
Print

Definition

It is about taking a series of user stories and putting them together in a meaningful and visual way. It offers a representation of the sequence of the activities and their adequate solution. By breaking down a process, this technique grants a global view, from end-to-end vision to detailed user stories.

Story Mapping is used to help understand a product’s functionality or the flow of usage. It also assists the prioritization of products’ delivery. Therefore, it is often exposed to the delivery team during versions planning sessions.

Why to use Story Mapping?

  • Provides clarity and meaning to your user stories.

  • Helps to plan and prioritise requirements according to their importance and value.

  • Allows for understanding and explaining the functionalities of a system.

  • Easier and more versatile than a long text.

  • Fosters cooperation by involving all the members of your team.

  • Evaluates and helps to manage risks. This is achieved by analysing the stories through the delivery context of the business value. 

  • Prevents for losing yourself in the details of user stories and to get away from the global context.

Although story mapping pictures a flow, it cannot analyse or illustrate the dependencies between the requirements. Nevertheless, it can be used to facilitate such an analysis.

Contexts that are not process-oriented may find Story Mapping less useful.

How to use Story Mapping

Building a Story Mapping

Example

Read more by subscribing to the BA Toolkit 

On top of the brief description of the method, access to:

  • an explanation of when and how to use it,
  • a practical example,
  • tips and recommendations for use,
  • downloadable checklists and templates,
  • references for further reading,

Table of contents

Latest techniques

E.1 - Specify and modelling

39 – RACI Matrix

The RACI matrix is a tool that can be used to identify and visualize the roles and responsibilities of every member of a project or process. In addition, a RACI matrix allows you to map the activities, to visually determine “who does what”, and to define the size of the project as well as its scope.

Read More »
C.2 - Maintain the requirements

13 – Data Flow Diagrams

We are familiar with rules in our lives. They are in our legal system, our games, our family, and of course business.

​According to BABOK, Business rules is a specific, practicable, testable directive that is under the control of the business. It serves as a criterion guiding behavior, shaping judgments, or making decisions

Read More »
E.1 - Specify and modelling

12 – Data Dictionary

We are familiar with rules in our lives. They are in our legal system, our games, our family, and of course business.

​According to BABOK, Business rules is a specific, practicable, testable directive that is under the control of the business. It serves as a criterion guiding behavior, shaping judgments, or making decisions

Read More »
Agile

70 – Story Mapping

Collaborative games or workshops aim at promoting cooperation within your team and provides it with a common goal so that all the members participating in the game can work together.

Read More »

Not yet a member?