Lean Startup + Story Mapping = Awesome Products Faster
39 likes15,390 views
The document discusses the integration of lean startup principles with story mapping to enhance product development efficiency. It emphasizes the importance of transitioning from a requirements delivery to a discovery process, highlighting the necessity of understanding customer needs and involving them in product creation. Key concepts include minimal viable products (MVPs), the lean canvas framework, and the benefits of user story mapping for clear and collaborative project management.
Lean Startup + Story Mapping = Awesome Products Faster
- 1. Lean Startup + Story Mapping = Awesome Products Faster! www.agile42.com 1
- 2. Brad Swanson Senior Agile Coach @ agile42 brad.swanson@agile42.com @bradswanson Agile42 The Agile Coaching Company 2
- 3. David Hawks CEO of Agile Velocity Agile Trainer and Coach Certified Scrum Coach (CSC) Agile Austin Board Member (Education Chair) @austinagile austinagile.com (blog) 3 Transforming Technology Organizations
- 4. What is the difference between focusing on Outcomes Vs Output? 4
- 5. 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
- 6. …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
- 7. How good are we at predicting what customers need? Feature/funcPon usage in the soRware industry oRen 13% always 7% 16% somePmes Never 45% never rarely 19% Rarely SomePmes ORen Always From: A Standish Group 2002 study 8
- 8. Validated Learning: the Build-‐ Measure-‐Learn cycle 1) What do we need to learn?! Learn Build Minimize time thru the loop 3) What is the simplest thing to build to measure it?! (MVP)! Measure 2) How can we measure it?! Eric Ries: The Lean Startup 9
- 9. Minimal Viable Product -‐ MVP MVP is “the fastest way to get through the Build-Measure-Learn feedback loop with the minimum amount of effort.” – Eric Ries, The Lean Startup 10
- 10. Lean Canvas: Ash Maurya 1. Problem top 3 problems ExisPng alternaPves Lean Canvas 4. SoluPon top 3 features 8. Key metrics e.g. AARRR 7. Cost Structure 3. Unique 9. Unfair 2. advantage value Not easily copied or Customer bought proposiPon segments Clear compelling message. Why makes you different? Target customers 5. Channels Path to customers Early adopters? 6. Revenue streams Customer acquisiPon, distribuPon, people, Revenue model, life Pme value, revenue, etc. gross margin Product Market Lean Canvas, from Ash Maurya: Running Lean. Licensed under CreaPve Commons-‐AdribuPon-‐Share Alike 3.0 *AARRR metrics: acquisiPon, acPvaPon, revenue, retenPon, referral (Dave McClure) 11
- 11. ParPal Lean Canvas: Home AutomaPon • • • 1. Problem Inefficient energy usage Age & disability create difficulty ? 4. SoluPon • Voice command lights, appliances • Scheduled tasks • MoPon detecPon • ? 3. Unique value proposiPon • Integrated control of • ALL home systems • • Free installaPon • ? 9. Unfair advantage Patents ? 2. Customer segments • Elderly/disabled • Eco-‐conscious • ? ExisPng alternaPves • Hire help • Perform manually • ? • • • 8. Key metrics # requests 4 info # subscripPons ? 7. Cost Structure MarkePng, , product design, ? Product 5. Channels • • • Infomercials Social media ? Early adopters? 6. Revenue streams Hardware sales, subscripPon, ? Market Lean Canvas, from Ash Maurya: Running Lean. Licensed under CreaPve Commons-‐AdribuPon-‐Share Alike 3.0 12
- 12. Challenges with One dimensional backlogs • Do you understand the workflow? • Are you able to see the relaPonship of larger stories to child stories? • How do you validate that your backlog is complete? • What context do you use for prioriPzaPon? 15
- 13. User tasks are decomposed into smaller tasks and organized into activities 16
- 14. User Story Maps help us plan releases in complete and valuable slices 17
- 15. Anatomy of a User Story Map backbone AcPvity AcPvity (Theme/epic) (Theme/epic) High Task (story) AcPvity (Theme/epic) (Theme/epic) AcPvity (Theme/epic) Workflow sequence walking skeleton Task (story) AcPvity Task (story) Task (story) Task (story) Task (story) Task (story) Task (story) Low Priority MVP Task (story) Task (story) Task (story) Task (story) Task (story) Task (story) Next Release (MVI) Task (story) 18
- 16. 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 19
- 17. Step 2: Merge these post-‐its into a single model: Ø Ø Ø Arrange them leR to right in an order that makes sense to the group Eliminate duplicates Cluster items that seem similar and create labels for the 20 clusters if items seem to go together
- 18. Step 3: Determine 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 21
- 19. Minimal Viable Product -‐ MVP MVP is “the fastest way to get through the Build-Measure-Learn feedback loop with the minimum amount of effort.” – Eric Ries, The Lean Startup 22
- 20. Reading the activities across the top of the system helps us understand end-to-end use of the system. 23
- 21. User tasks make ideal user stories 24
- 22. User Story Mapping is Collaborative & Fosters Co-Ownership 25
- 23. User Story Maps help us see things from a user’s perspective Colors for different user personas 26
- 24. With User Story Mapping you can test for Gaps by Walking the Map 27