Updated: Mar 20
Story mapping is a simple yet effective technique to visualise the product backlog and product evolution though product development sprints. This is inspired by Jeff Patton's book User Story Mapping: Discover the Whole Story, Build the Right.
A user story map arranges user stories into a useful model to help understand the functionality of the system, identify holes and omissions in the backlog, and effectively plan holistic releases that deliver value to users and business with each release.
Step 1: Group the stories by application/theme/functionality and create the grid
Step 2: Once the stories are organised, start the surgical operation: slicing the list!
Step 3: Update after completion of the first sprint: First contact
Step 4+: Update after each sprint to have an up-to-date picture of the status of the product.
A write up on running a story mapping workshop with your team is available here.