Today, I would like to tell you about Story Mapping.
It’s a method for arranging User Stories to create a more holistic view of how they fit into the overall user experience.
On the horizontal axis, you’ll find the fundamental steps of the customer journey (epics); arranged in a chronological narrative flow.
Individual User Stories are arranged beneath the larger steps they roll up under. When a Story Map is complete, you can see all of the ways a user might interact with a product in a single, logical view that progresses from the first interaction to the completion of the overall user objective.
Flat Product Backlogs are a great way to prioritise work, but they don’t show the full picture.
By creating Story Maps you can better join the dots between what you’re building, the value it delivers, the Minimum Viable Product and the build time across multiple releases.
It makes it easy to track progress; enables the team to better understand what their customers want and value; and highlights risks. It is co-created by the team and stakeholders.
Jeff Patton literary wrote the book on Story Mapping
I received my CSPO training from Jeff Patton, who formulated the original concept and wrote a book about it. You can find his excellent resources here. If you are keen to learn more, have a look at Jeff Patton's book on Story Mapping
This post was first published here. I used Jeff Patton's material, and information from productplan.com, and easyagile.com .
Commentaires