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

Transcription

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

2 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 13% 16% 7% often sometimes always rarely 19% From: A Standish Group 2002 study 45% never Never Rarely Some5mes O8en Always

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

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

6 Challenges with One dimensional backlogs Do you understand the workflow? Are you able to see the relationship of larger stories to child stories? How do you validate that your backlog is complete? What context do you use for prioritization?

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 backbone walking skeleton Anatomy of a User Story Map Workflow sequence Priority High Low First Release Next Release

10 Minimal Viable Product - MVP 10 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 11 Validated Learning: the Build-Measure-Learn cycle 1) What do we need to learn? Learn Minimize time thru the loop Build 3) What is the simplest thing to build to measure it? (MVP) Measure 2) How can we measure it? Eric Ries: The Lean Startup

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

13 Partial Lean Canvas: Home Automation Problem Inefficient energy usage Age & disability create difficulty? Exis5ng alterna5ves Hire help Perform manually? 4. Solu5on Voice command lights, appliances Scheduled tasks Mo5on detec5on? 8. Key metrics # requests 4 info # subscrip5ons? 7. Cost Structure Marke5ng, product design,? 3. Unique value proposi5on Integrated control of ALL home systems Free installa5on? 9. Unfair advantage Patents? 5. Channels Infomercials Social media? 6. Revenue streams Hardware sales, subscrip5on,? 2. Customer segments Elderly/disabled Eco- conscious? Early adopters? Product Market Lean Canvas, from Ash Maurya: Running Lean. Licensed under Crea5ve Commons- AZribu5on- Share Alike 3.0

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

15 Story Map Part 2 Workflow sequence High Priority Low 1. Arrange in order of workflow 2. Group items into common activities or categories 3. Arrange top to bottom by priority

16 Story Map Part 3 Workflow sequence High MVP Priority Low Next Release Draw the line for your MVP 2. Draw the line for subsequent Releases

17 Step 1 At your tables: Ø Ø Ø Choose a Customer Segment from your Lean Canvas Someone plays the part of this Customer and describes what they would do with the product The rest of the group writes these tasks down on post-its

18 Step 2 Merge these post-its into a single model: Ø Ø Ø Arrange them left to right in an order that makes sense to the group Eliminate duplicates Cluster items that seem similar and create labels for the clusters if items seem to go together

19 Step 3 Create the MVP and subsequent releases: Ø Ø Ø Walk the map to determine necessary tasks Draw a line below those tasks this is your MVP Discuss with stakeholders to determine subsequent logical releases

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

21 User Story Mapping is Collaborative & Fosters Co-Ownership

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

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

24 Anatomy of a User Story Map Workflow sequence Priority High Low MVP Next Release