Story Mapping

1. Recover from Flat Backlogs with User Story Mapping Tracy Whitehill Agile Team Coach Story Mapping

2. How good are we at predicting what customers need?

3. How good are we at predicting what customers need? Feature/function usage in the software industry always often sometimes never rarely From: A Standish Group 2002 study

4. We want to Shift the Process from a Requirements Delivery Process… False Assumptions: • The customer knows what he wants • The developers know how to build it • Nothing will change along the way

5. …To a Requirements Discovery Process Reality: The customer discovers what he wants The developers discover how to build it Many things change along the way

7. User tasks are decomposed into smaller tasks and organized into activities

8. User Story Maps help us plan releases in complete and valuable slices

9. Anatomy of a User Story Map backbone Activity (Theme/epic) Activity (Theme/epic) Activity (Theme/epic) Activity (Theme/epic) Activity (Theme/epic) Workflow sequence walking skeleton Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) High First Release Action (story) Action (story) Action (story) Action (story) Priority Next Release Action (story) Action (story) Low Action (story)

10. Minimal Viable Product - MVP MVP is “the version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.” – Eric Ries, The Lean Startup

11. 3) What is the simplest thing to build to measure it? (MVP) 1) What do we need to learn? 2) How can we measure it? Validated Learning: the Build-Measure-Learn cycle Learn Build Minimize time thru the loop Measure Eric Ries: The Lean Startup

12. Lean Canvas Lean Canvas: Ash Maurya 4. Solution top 3 features 1. Problem top 3 problems Existing alternatives 9. Unfair advantage Not easily copied or bought 3. Unique value proposition Clear compelling message. Why makes you different? 2. Customer segments Target customers Early adopters? 8. Key metrics e.g. AARRR 5. Channels Path to customers 7. Cost Structure Customer acquisition, distribution, people, etc. 6. Revenue streams Revenue model, life time value, revenue, gross margin Market Product Lean Canvas, from Ash Maurya: Running Lean. Licensed under Creative Commons-Attribution-Share Alike 3.0 *AARRR metrics: acquisition, activation, revenue, retention, referral (Dave McClure)

13. Partial Lean Canvas: Home Automation • 1. Problem • Inefficient energy usage • Age & disability create difficulty • ? • Existing alternatives • Hire help • Perform manually • ? • 4. Solution • Voice command lights, appliances • Scheduled tasks • Motion detection • ? • 3. Unique value proposition • Integrated control of ALL home systems • Free installation • ? • 9. Unfair advantage • Patents • ? • 2. Customer segments • Elderly/disabled • Eco-conscious • ? • Early adopters? • 5. Channels • Infomercials • Social media • ? • 8. Key metrics • # requests 4 info • # subscriptions • ? 7. Cost Structure Marketing, product design, ? 6. Revenue streams Hardware sales, subscription, ? Market Product Lean Canvas, from Ash Maurya: Running Lean. Licensed under Creative Commons-Attribution-Share Alike 3.0

14. Story Map Activity Part 1 • Choose a Customer Segment from your Lean Canvas • One person plays the Customer role • Ask what the customer wants, capture each idea on a post-it Workflow sequence Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) Action (story)

15. Story Map Activity Part 2 Activity (Theme/epic) Activity (Theme/epic) Activity (Theme/epic) Activity (Theme/epic) Activity (Theme/epic) Workflow sequence Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) High Action (story) Action (story) Action (story) Action (story) Priority Action (story) Action (story) Low • Arrange in order of workflow • Group items into common activities or categories • Arrange top to bottom by priority

16. Story Map Activity Part 3 Activity (Theme/epic) Activity (Theme/epic) Activity (Theme/epic) Activity (Theme/epic) Activity (Theme/epic) Workflow sequence Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) High MVP Action (story) Action (story) Action (story) Action (story) Priority Next Release Action (story) Action (story) Low • Draw the line for your MVP • Draw the line for subsequent Releases

17. Reading the activities across the top of the system helps us understand end-to-end use of the system.

18. User Story Mapping is Collaborative & Fosters Co-Ownership

19. User Story Maps help us see things from a user’s perspective Colors for different user personas

20. With User Story Mapping you can test for Gaps by Walking the Map

21. Anatomy of a User Story Map Activity (Theme/epic) Activity (Theme/epic) Activity (Theme/epic) Activity (Theme/epic) Activity (Theme/epic) Workflow sequence Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) Action (story) High MVP Action (story) Action (story) Action (story) Action (story) Priority Next Release Action (story) Action (story) Low Action (story)