• Skip to main content
  • Skip to footer

Agile Pain Relief Consulting

Scrum and Agile Training and Resources

  • Certified Scrum Training
    • Certified ScrumMaster (CSM) Training
    • Advanced Scrum Master Certification (A-CSM)
    • Certified Scrum Product Owner (CSPO) Training
    • Private Scrum & Agile Training
      • Agile Foundations Private Training
    • Choose the Right Scrum Training for Your Needs
    • FAQs and Policies
  • What Is Scrum
  • Resources
    • A Jargon-Free Introduction to Scrum
    • *NEW* Agile Glossary and Reference Library
    • The Guide to Effective Agile Retrospectives
    • Online Agile Teams Game (Beta)
    • Five Steps for Creating High-Performance Teams FREE ebook
    • Foundational Scrum Free Learning Series
    • The Story of a Sprint
    • Free Virtual Scrum Meet-Up
    • Get Scrum Education Units (SEU)
    • Articles & Interviews
    • Newsletter
  • Blog
    • Scrum by Example – Stories for the Working ScrumMaster
    • Beyond Scrum Blog Series
    • Scrum Anti-Patterns – How We Hold Back Our Scrum Teams

Learning Story Mapping Through Exercises

April 30, 2013 by Mark Levison 2 Comments

Attendees in Kitchener Waterloo - collaborating on building their maps
Attendees in Kitchener Waterloo – collaborating on building their Story Maps.

Story Mapping is a simple tool to help you visualize your Product Backlog. The traditional Product Backlog in Scrum is a real improvement over traditional methods for tracking and understanding the work ahead. However it’s still a long To Do List which has some issues:

  • It’s hard to see the forest for the trees.
  • It’s easy to miss important items in the morass of detail.
  • It’s hard to prioritize well since we can’t see the big picture.
  • It’s not explicitly focused on the user needs.

In other words, flat lists become confusing as the Product grows in size and complexity.

Story Mapping is a tool to help overcome these issues by helping the team visualize the needs of the end-users. Along the top we write out all the “User Needs”. On the Y-axis we create the Stories for each “Need” or task. Some “User Needs” aren’t of interest in the current release – so they might get no Stories. Other needs have a number of things that need to be done for them – so they get many Stories. In addition, each user gets their own map.

Attendees in Kitchener Waterloo - collaborating on building their maps

The key here is that the map acts as a tool to help organize the Stories. The map helps us spot gaps in our product and helps us discover the priorities. However, most importantly Story Maps help start conversations among team members about what we’re building.

The files below are from a series of Story Mapping workshops that I have facilitated in Montreal, Toronto and Kitchener-Waterloo this past year. If you would like to bring me into your company to facilitate a Story Mapping Workshop or teach a Product Owner course please contact us.

The files make the most sense if you’ve attended the workshop.

  • StoryMappingWalkThrough – the keynote presentation I run in the background.
  • Story Mapping Basics – the basic introductory handout that all attendees get. It outlines some of the basic ideas behind Story Mapping and provides the core scenario for the exercises
  • Julia Persona and Rob Persona – the personas that the audience gets to use for their exercises.
Photo by Mark Levison. Image by Agile Pain Relief.
Mark Levison

Mark Levison has been helping Scrum teams and organizations with Agile, Scrum and Kanban style approaches since 2001. From certified scrum master training to custom Agile courses, he has helped well over 8,000 individuals, earning him respect and top rated reviews as one of the pioneers within the industry, as well as a raft of certifications from the ScrumAlliance. Mark has been a speaker at various Agile Conferences for more than 20 years, and is a published Scrum author with eBooks as well as articles on InfoQ.com, ScrumAlliance.org an AgileAlliance.org.

Filed Under: Product Owner, User Stories Tagged With: Agile, Product Backlog, Product Backlog Refinement, Scrum, ScrumMaster, Story Mapping, User Needs, User Stories, Workshop

About Mark Levison

Mark Levison has been helping Scrum teams and organizations with Agile, Scrum and Kanban style approaches since 2001. From certified scrum master training to custom Agile courses, he has helped well over 8,000 individuals, earning him respect and top rated reviews as one of the pioneers within the industry, as well as a raft of certifications from the ScrumAlliance. Mark has been a speaker at various Agile Conferences for more than 20 years, and is a published Scrum author with eBooks as well as articles on InfoQ.com, ScrumAlliance.org an AgileAlliance.org.

Reader Interactions

Trackbacks

  1. Agile Lean April 23rd P2P – Learn Story Mapping through Exercises | Waterloo Agile Lean says:
    May 4, 2013 at 7:29 pm

    […] Updated materials are located: https://agilepainrelief.com/blog/learning-story-mapping-exercises.html […]

    Reply
  2. Stories | Pearltrees says:
    May 13, 2013 at 10:43 am

    […] Learning Story Mapping Through Exercises […]

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Footer

  • Certified Scrum Training
  • Private Training
  • Effective Agile Retrospectives
  • Agile Reference Library
  • About Us
  • FAQs and Policies
  • Site Map
  • Partners

Contact Us

  • 877-248-8277

Follow Us

  • LinkedIn
  • Mastodon
  • RSS


Subscribe for Scrum & Agile news and more resources





© 2011–2023 Mark Levison & Agile Pain Relief