Collaborate with stakeholders for Product Success!

User Story Mapping Workshop​

A User Story Map captures the journey a customer takes with the product including activities and tasks they perform with the system. We will explore the big picture of what it is we will be building and define high level user stories.

What is User Story Mapping?

A User Story Map organises User Stories according to a narrative flow that presents the big picture of the product. The technique was developed by Jeff Patton from 2005 to 2014 to address the risk of projects flooded with very detailed user stories that distract from realizing the product’s main objectives.

1: Why Story Mapping?

Creating a story map collaboratively ensures team members are on the same page from the start of the project through to ongoing development of new releases.

2: Creating a shared understanding

It replaces the lengthy, technical requirement gathering and siloed updating processes found in waterfall development. Story maps are intended to spark collaboration and conversation among Agile team members, while providing them with the bigger picture of how the digital product flows and fits together. This latter quality of story maps is important in the Agile environment, because losing sight of the product as a whole is a common challenge, likely to arise when teams work from a discrete list of user stories in a backlog.

A shared understanding can be achieved by defining a Product Vision together, and understanding the customers better by defining Persona’s.

3: Focus on the customer

If you’re new to the concept of User Stories, they are informal, natural language descriptions of features, UI elements, or tasks, written from the perspective of the user. They’re intended to get the team talking to each other about solutions in the context of end users and the benefit they’ll receive. These conversations help everyone arrive at shared understanding much faster than reading a requirements document. User stories can be written at a high level to describe a full product or feature and what it enables users to do or at low level, to outline an interface element and its value. The Persona’s above can also help to move away from classical requirements specification and to try to look at things from the perspective of the customer.

Exected Outcome

Shared understanding of the product direction and aligned roadmap and priorities.

  • Product Vision co-created by the participants
  • Personas representing different User Segments
  • User Story Map, an overview of actions the Users would do and a list of users stories to allow them to complete them.
  • Release Roadmap, a release strategy with concrete short to medium goals and less defined longer term release goals

Intended audience

Business, Functional and Technical Stakeholders

Delivery

Virtual or In-Person

Duration

4 – 8 hours depending on the scope of the product or feature

Let's Talk About how We Can Help!

Are you curious about how User Story Mapping can help you?