lean startup + story mapping = awesome products faster
Post on 14-Sep-2014
1.393 Views
Preview:
DESCRIPTION
TRANSCRIPT
Lean Startup + Story Mapping = Awesome Products Faster!
1
www.agile42.com
Brad Swanson Senior Agile Coach @ agile42 brad.swanson@agile42.com
@bradswanson Agile42
The Agile Coaching Company
2
David Hawks
CEO of Agile Velocity Agile Trainer and Coach
Certified Scrum Coach (CSC)
Agile Austin Board Member (Education Chair)
@austinagile
austinagile.com (blog)
Transforming Technology Organizations
3
What is the difference between focusing
on
Outcomes
Output?
Vs
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
How good are we at predicting what customers need?
8
45%
19%
16%
13% 7%
Never Rarely SomePmes ORen Always
From: A Standish Group 2002 study
Feature/funcPon usage in the soRware industry
always oRen
somePmes
rarely
never
Build Learn
Minimize time thru the loop
Eric Ries: The Lean Startup
1) What do we need to
learn?!
2) How can we measure it?!
3) What is the simplest thing
to build to measure it?!
(MVP)!
Validated Learning: the Build-‐Measure-‐Learn cycle
Measure
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
1. Problem
top 3 problems
ExisPng alternaPves
4. SoluPon top 3 features
8. Key metrics e.g. AARRR
3. Unique value
proposiPon Clear compelling message. Why makes you different?
2. Customer segments
Target customers
Early adopters?
9. Unfair advantage
Not easily copied or bought
5. Channels Path to customers
7. Cost Structure Customer acquisiPon, distribuPon, people,
etc.
6. Revenue streams Revenue model, life Pme value, revenue,
gross margin
Lean Canvas: Ash Maurya
Product Market
Lean Canvas
11 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)
1. Problem • Inefficient energy
usage • Age & disability
create difficulty • ?
ExisPng alternaPves • Hire help • Perform manually • ?
4. SoluPon • Voice command
lights, appliances • Scheduled tasks • MoPon detecPon • ?
8. Key metrics • # requests 4 info • # subscripPons • ?
3. Unique value proposiPon
• Integrated control of ALL home systems
• Free installaPon • ?
2. Customer segments
• Elderly/disabled • Eco-‐conscious • ?
Early adopters?
9. Unfair advantage
• Patents • ?
5. Channels • Infomercials • Social media • ?
7. Cost Structure MarkePng, , product design, ?
6. Revenue streams Hardware sales, subscripPon, ?
Lean Canvas, from Ash Maurya: Running Lean. Licensed under CreaPve Commons-‐AdribuPon-‐Share Alike 3.0 Product Market
ParPal Lean Canvas: Home AutomaPon
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
User tasks are decomposed into smaller tasks and organized into
activities 16
User Story Maps help us plan releases in complete and valuable slices
17
AcPvity (Theme/epic)
AcPvity (Theme/epic)
AcPvity (Theme/epic)
AcPvity (Theme/epic)
AcPvity (Theme/epic)
Task (story)
Task (story)
Task (story)
Task (story)
Task (story)
Task (story)
Task (story)
Task (story)
Task (story)
Task (story)
Task (story)
Task (story)
Task (story)
Task (story)
Workflow sequence
Priority
MVP
Task (story)
Next Release (MVI)
Anatomy of a User Story Map High
Low
backbone
walking skeleton
18
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
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
clusters if items seem to go together 20
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
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
Reading the activities across the top of the system helps us understand
end-to-end use of the system.
23
User tasks make ideal user stories
24
User Story Mapping is Collaborative & Fosters Co-Ownership
25
User Story Maps help us see things from a user’s perspective
Colors for different user personas
26
With User Story Mapping you can test for Gaps by Walking the Map
27
top related