User Story Mapping - Developing a Shared Understanding

Discover how user story mapping can reduce development waste and unify team members behind a well-defined goal in this 59-minute GDC 2019 session. Learn to implement the "Now and Later" model, utilize opportunity canvases, and collaboratively tell stories to create a shared understanding. Explore techniques like the product frame, fist of five voting, and rock breaking to prioritize tasks and build incrementally. Gain insights on developing minimum viable solutions, treating releases as experiments, and fostering group buy-in. Understand why stories are not written requirements but rather tools to encourage conversations and interactions that lead to better project understanding.

USER STORY MAPPING DEVELOPING A SHARED UNDERSTANDING
SEARCHING FOR SOLUTIONS
WHAT IS THIS GAME? WHO WAS THIS GAME FOR?
THE BROKEN TELEPHONE GAME
SHARED DOCUMENTS ARE NOT SHARED UNDERSTANDING
INSTEAD OF DESIGN TABLETS USE THE NOW AND LATER MODEL
OPPORTUNITY CANVAS
BE FLEXIBLE REQUIREMENTS ARE JUST IDEAS
GET A GROUP TOGETHER AND COLLABORATIVELY TELL A STORY
THE PRODUCT FRAME: BUILD A MORNING ROUTINE
TIMERS UP: FIST OF FIVE
PLACE ON THE BOARD IN CHRONOLOGICAL ORDER
FORMING THE BACKBONE
FIRST MILESTONE
WHO IS IT FOR? Fit Types
DISAGREE AND COMMIT
ROCK BREAKING
ASSIGNING WORK AND ESTIMATING
BUILD LESS
THERE'S ALWAYS MORE TO BUILD THAN YOU HAVE THE TIME OR RESOURCES TO BUILD
MINIMUM VIABLE SOLUTION
EVERY RELEASE IS AN EXPERIMENT
BUILD WITH AN INCREMENTAL STRATEGY
WHY I CHOOSE TO CONTINUE TO STORY MAP
WHAT TO BUILD FIRST
ALTERNATE POINTS OF VIEW
GROUP BUY-IN
STORIES ARENT A WRITTEN FORM OF REQUIREMENTS STORIES AREN'T THE REQUIREMENTS STORIES ENCOURAGE CONVERSATIONS, INTERACTIONS, AND QUESTIONS, WHICH LEAD TO A BETTER UNDERSTANDING