Back to training

Story Mapping

About

Agile Planning typically uses user stories. But user stories have a problem: they don’t capture and maintain the context of the story over the whole development period. Jeff Patton has found a better way: a two-dimensional backlog called a story map.

Who should attend

Product Owners and Business Analysts who want to understand user stories at a more profound level and need a better way to manage them. Software developers and other roles involved in the business analysis can benefit from applying story mapping technique.

Why attend

In this 1-day practical workshop, you will learn how to use story mapping to identify, plan and focus the features that need to be done from the users’ point of view.

This workshop is very practical, with about 50% of the time spent to practice the concepts that are presented. You will also benefit from a short presentation, continuous feedback from the trainer, Q&A, and Anti-patterns.

Structure

  • What is really a user story?
  • Downsides of user stories and list – ­style backlogs
  • What does the user really want – or what is a useful working increment
  • Story mapping basics
  • Build a story map by yourself
  • Complex story maps: branches, parallel execution etc.
  • Build a story map in a group

Optional, depending on time and audience:

  • Facilitation techniques for the Story Mapping workshop
  • Personas and how they can help defining story maps

Prerequisites

For best results, you should have at least 2 years of experience as a product owner, business analyst or practicing business analysis from other roles. Knowledge of agile principles and practices will help you understand the content better.

Practical details

  • Included: welcome coffee, lunch and coffee breaks
  • Training language: English/Romanian
  • Participants will receive a certificate of attendance

Need a customized workshop? Contact us and we’ll adapt the content as required.