Story Mapping 101

Learn how this simple, but powerful tool can completely transform the way you and your team think about and manage your story backlogs.

Originally created by Jeff Patton, story maps are an incredibly effective way to help agile teams stay honest by, among other things, providing visibility into how each and every piece of work a team does delivers incremental value directly to users.

Transcript

1. © Copyright 2017 Pivotal Software, Inc. All rights Reserved. Version 1.0 Story Mapping 101 Chisa Nwabara 15 November, 2017
2. WHO AM I?
3. I’M CHISA! (chee-suh)
4. LONDON STAFF TECHNICAL PROGRAM MANAGER gif source: AIGA DIVERSITY & INCLUSION GLOBAL COUNCIL EMEA CO-LEAD & EXEC LEADERSHIP STRATEGY
5. strategy process enablement tactical
6. Enough about me, let’s go!
7. What does this mean? SHARED UNDERSTANDING
8. WHAT IS IT? SHARED UNDERSTANDING when we both understand what the other person is imagining and why -Jeff Patton individual and collective ownership of a new perspective accepted by the group -IGI Global
9. THE CAKE ORDER Customer: Hello, I’d like to order a cake. Employee: Sure, what would you like written on it? Customer: Could you write “So long, Alicia” in purple? Employee: Sure. Customer: And put stars around it? Employee: No problem. I’ve written this up, and will hand it to my cake decorator right away. We’ll have it for you in the morning.
10. THE RESULTS
11. Shared Documents ≠ Shared Understanding
12. DON’T SKIP THIS STEP...TAKE THE TIME TO DO IT RIGHT. I’m glad we all agree. oh... Ah ha! I’m glad we all agree!
13. DON’T SKIP THIS STEP...TAKE THE TIME TO DO IT RIGHT. I’m glad we all agree. oh... Ah ha! I’m glad we all agree!
14. DON’T SKIP THIS STEP...TAKE THE TIME TO DO IT RIGHT. I’m glad we all agree. oh... Ah ha! I’m glad we all agree!
15. DON’T SKIP THIS STEP...TAKE THE TIME TO DO IT RIGHT. I’m glad we all agree. oh... Ah ha! I’m glad we all agree!
16. THIS BRINGS US TO... STORY MAPS
17. WHAT IS A STORY MAP? A story map arranges user stories into a useful model. Story maps help you to... ...understand a system’s functionality. ...identify holes/omissions in your backlog. ...effectively prioritize/groom your backlog so that value is delivered every iteration. …promote shared understanding (client involvement; collaborative approach). ...measure feature completeness. ...discuss/manage scope.
18. LET’S HAVE AN EXAMPLE...
19. This is Drew...
20. Drew just got a phone call from his friends. “Wanna go to the club?”
21. but in order to do this...
22. ...he needs this:
23. Example LET’S GET DREW TO THE CLUB!
24. SOME ASSUMPTIONS What do we already know about Drew & this situation? • Drew has a bank account (existing customer) • Drew can get to the bank • Drew knows how to use an ATM (experience with the system)
25. MAP IT OUT: Drew Goes Clubbing Withdraw Cash As a bank customer I want a custom amount withdrawal option So that…. As a bank customer I want a standard $20 withdrawal option So that…. As a bank customer I want a standard $40 withdrawal option So that…. As a bank customer I want to select the account to w/d from So that…. See Account Activity As a bank customer I to see my balance in my secondary accounts So that…. As a bank customer I want to see my balance So that…. As a bank customer I want to see my transaction activity So that…. Drive to Bank Drew Use the ATM Get Receipt Cancel Transaction Drive Home Drive to Club
26. ORGANISE BY PRIORITY PRIORITY Drew As a retail customer I want a standard $20 withdrawal option So that…. As a retail customer I want a standard $40 withdrawal option So that…. As a retail customer I want a custom amount withdrawal option So that…. As a retail customer I want to select the account to w/d from So that…. As a retail customer I to see my balance in my secondary accounts So that…. As a retail customer I want to see my balance So that…. As a retail customer I want to see my transaction activity So that…. See Account Activity Withdraw Cash
27. Model LET’S REVIEW
28. 1. SET THE STAGE W/A TITLE & ASSUMPTIONS A DESCRIPTIVE SCENARIO TITLE
29. 2. MAP OUT SCENES & CORRESPONDING ACTORS USER STEP A DESCRIPTIVE SCENARIO TITLE
30. 3. ADD DETAILS & PARTICULARS USER STEP STORY A DESCRIPTIVE SCENARIO TITLE
31. 3. ADD DETAILS & PARTICULARS USER STEP STORY ASSUMPTION A DESCRIPTIVE SCENARIO TITLE
32. 3. ADD DETAILS & PARTICULARS USER STEP STORY ASSUMPTION TASK A DESCRIPTIVE SCENARIO TITLE
33. PRIORITISE BASED ON NECESSITY USER STEP STORY ASSUMPTION TASK A DESCRIPTIVE SCENARIO TITLE
34. WALK THE MAP • Walking the map helps to determine your product backlog. • Do highest value, highest priority items first. NOTE: STORY MAPS ARE DYNAMIC. POC! MVP!
35. THE BIG PICTURE • Drew (User) ◦ Drew’s Goals (User Journeys) • Save for the future • • Pay bills on the go • • Go to the club (get money) •
36. Hey! A backlog! FLAT BACKLOG VS.
37. “The flat backlog is a poor explanation of what a system does. The new user story backlog is a MAP.” -Jeff Patton
38. When should I use story maps?
39. Vision The WHAT and WHY Decades + Strategy HOW we will REALIZE the vision Years Roadmap TIMELINE and TACTICS for how we intend to execute the strategy Months Backlog The DETAILS we need to create the product roadmap Weeks
40. Vision The WHAT and WHY Decades + Strategy HOW we will REALIZE the vision Years Roadmap TIMELINE and TACTICS for how we intend to execute the strategy Months Backlog The DETAILS we need to create the product roadmap Weeks
41. FEATURE MAPPING
42. Who needs to be in the room? Isn’t this just for product people?
43. NO! THIS IS A TEAM EFFORT!
44. Who should be in the room? • Users!!!! • Other actors in the journey • Product Manager • Engineering • UX/Design • SMEs
45. Why should I care?
46. YOU ALL OWN THE OUTCOME
47. If you need to convince somebody... Here are some ways to go about that conversation • They work • Low cost activity • Product people don’t know everything • “Your input is valuable” • Use some metaphors...tell them it’s like making a movie • Measure twice, cut once • “If I asked you to draw me a picture of what we are building and why, could you do it? Would it look the same as so and so’s picture? How confident are you about that?”
48. IN A NUTSHELL... Recap of story mapping steps 1. Set the stage with assumptions and a title for the scenario 2. Map out the scenes and corresponding actors 3. Add details and particulars 4. Determine the slices of your work (red ribbon) 5. Take that slice and determine your dev strategy
49. THINGS TO REMEMBER... Lessons Learned • Give your map a name • Call out assumptions at different levels • Track your actors (users) at each step • Work one layer of granularity at a time • Every step does not require an action • Use a legend/colour code it! • Your secret weapon = “...and then what happens?” • This is not initially about implementation
50. For more information... ...read the book!
51. MAKE YOUR MOVIE SHINE!
52. Source: User Story Mapping by Jeff Patton cnwabara@pivotal.io https://www.linkedin.com/in/chisaranwabara/ @chisology