User Story Mapping


Troubles with user stories? Create a clear map of the user journey to build a successful product

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.

Why Attend

In this 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 60% of the time spent practicing the concepts that are presented. You will also benefit from a short presentation, continuous feedback from the trainer, Q&A, and Anti-patterns.

Who Should Attend

Product Owners, Product Managers, and Business Analysts who want to:

  • close the gap between the business view and the technical view on a product
  • visualize a clear map of the user journey
  • visually define the incremental growth of the product and the release plan
  • understand user stories at a more profound level
  • want to find a better way to manage the user journey, the product growth, and the release plan

Managers, Software Developers, and other roles involved in product design and delivery can benefit from applying the user story mapping technique.

Practical Details

  • Language: English
  • Experiential, hands-on, interactive online learning with practical examples
  • Participants will be awarded a Mozaic Works certificate of completion
Quantity:
- +

Agenda

  • 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

More details and full agenda here.

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.

Meet Your Trainers

0
    0
    Your Cart
    Your cart is empty
      Apply Coupon
      Scroll to Top