Lean Startup + Story

Mapping =
Awesome Products
Faster!
STORY
DavidMAPPING
Hawks & Brad Swanson
David Hawks
CEO of Agile Velocity
Agile Trainer and Coach
Certified Scrum Coach (CSC)

Agile Austin Board Member

(Education Chair)

@austinagile

austinagile.com (blog)
2
Transforming Technology Organizations
 Brad  Swanson  
Senior  Agile  Coach  @  agile42  
brad.swanson@agile42.com  
@bradswanson  
Agile42  
The  Agile  Coaching  Company  

3  
What is the difference between focusing
on

Outcomes

Vs

Output?
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?
Feature/funcGon  usage  in  the  soIware  industry  
always  
oIen   7%  
13%   Never  
45%   Rarely  
16%  someGmes   never  
rarely   SomeGmes  
19%   OIen  
Always  

From:  A  Standish  Group  2002  study  

8  
 Validated  Learning:  the  Build-­‐
Measure-­‐Learn  cycle  
3) What is the
1) What do simplest thing
we need to Learn   Build   to build to
learn? measure it?
Minimize time (MVP)
thru the loop

Measure  

Eric  Ries:  The  Lean  Startup  

2) How can we measure it? 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  
Lean  Canvas:  Ash  Maurya  
Lean  Canvas  
1.   4.   3.  Unique   9.  Unfair   2.  
Problem   SoluGon   value   Not  advantage  
easily  copied  or  
Customer  
top  3  problems   top  3  features   proposiGon   bought   segments  
 
  Clear  compelling   Target  customers  
  message.  Why    
  8.  Key   makes  you  
5.    
ExisGng    
alternaGves  
metrics   different?     Channels   Early  adopters?  
e.g.  AARRR   Path  to  customers  

7.  Cost  Structure   6.  Revenue  streams  

Customer  acquisiGon,  distribuGon,  people,   Revenue  model,  life  Gme  value,  revenue,  
etc.   gross  margin  

Product   Market  
Lean  Canvas,  from  Ash  Maurya:  Running  Lean.  Licensed  under  CreaGve  Commons-­‐AaribuGon-­‐Share  Alike  3.0  
11  
*AARRR  metrics:  acquisiGon,  acGvaGon,  revenue,  retenGon,  referral  (Dave  McClure)  
 ParGal  Lean  Canvas:  Home  AutomaGon  
1.  Problem   4.  SoluGon   3.  Unique  value   9.  Unfair   2.  Customer  
•  Inefficient  energy   •  Voice  command   proposiGon   advantage   segments  
usage   lights,  appliances   •  Integrated  control  of   •  Patents   •  Elderly/disabled  
•  Age  &  disability   •  Scheduled  tasks   ALL  home  systems   •  Eco-­‐conscious  
•  ?  
create  difficulty   •  MoGon  detecGon   •  Free  installaGon   •  ?  
•  ?   •  ?   •  ?  
 
 
   
ExisGng  alternaGves   8.  Key  metrics   5.  Channels    
•  Hire  help   •  #  requests  4  info   •  Infomercials    
•  Perform  manually   •  #  subscripGons   •  Social  media  
•  ?   •  ?  
Early  adopters?  
•  ?  

7.  Cost  Structure   6.  Revenue  streams  

MarkeGng,  ,  product  design,  ?   Hardware  sales,  subscripGon,  ?  

Product   Market  
Lean  Canvas,  from  Ash  Maurya:  Running  Lean.  Licensed  under  CreaGve  Commons-­‐AaribuGon-­‐Share  Alike  3.0  
12  
 Challenges  with  One  
dimensional  backlogs  
• Do  you  understand  
the  workflow?  
• Are  you  able  to  see  
the  relaGonship  of  
larger  stories  to  child  
stories?  
• How  do  you  validate  
that  your  backlog  is  
complete?  
• What  context  do  you  
use  for  
prioriGzaGon?   15  
User stories (epics) are decomposed
into smaller stories and organized
into activities (themes/epics) 16  
User Story Maps help us plan releases
in complete and valuable slices
17  
 Anatomy  of  a  User  Story  Map  
backbone  
AcGvity   AcGvity   AcGvity   AcGvity   AcGvity  
(Theme/epic)   (Theme/epic)   (Theme/epic)   (Theme/epic)   (Theme/epic)  

Workflow  sequence  
walking  skeleton  
Task   Task   Task   Task   Task   Task   Task   Task  
High  

(story)   (story)   (story)   (story)   (story)   (story)   (story)   (story)  

MVP  
Task   Task   Task   Task  
Priority  

(story)   (story)   (story)   (story)  

Next  
Release  
Task   Task  
(MVI)  
(story)   (story)  
Low  

Task  
(story)  

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

Task   Task   Task   Task   Task   Task   Task   Task  

(story)   (story)   (story)   (story)   (story)   (story)   (story)   (story)  

Task   Task   Task   Task  

(story)   (story)   (story)   (story)  

Task   Task  
(story)   (story)  

Task  
(story)  

19  
 Story  map  acGvity  Part  2  

AcGvity   AcGvity   AcGvity   AcGvity   AcGvity  

(Theme/epic)   (Theme/epic)   (Theme/epic)   (Theme/epic)   (Theme/epic)  

Workflow  sequence  

Task   Task   Task   Task   Task   Task   Task   Task  

High  

(story)   (story)   (story)   (story)   (story)   (story)   (story)   (story)  

Task   Task   Task   Task  

Priority  

(story)   (story)   (story)   (story)  

Task   Task  
(story)   (story)  
Low  

Task  
1.  Arrange  in  order  of  (story)  
workflow  
2.  Group  items  into  common  acGvites  or  categories  
20  
3.  Arrange  top  to  boaom  by  priority  
 Story  map  acGvity  Part  3  

AcGvity   AcGvity   AcGvity   AcGvity   AcGvity  

(Theme/epic)   (Theme/epic)   (Theme/epic)   (Theme/epic)   (Theme/epic)  

Workflow  sequence  

Task   Task   Task   Task   Task   Task   Task   Task  

High  

(story)   (story)   (story)   (story)   (story)   (story)   (story)   (story)  

MVP  
Task   Task   Task   Task  
Priority  

(story)   (story)   (story)   (story)  

Next  
Release  
Task   Task  
(MVI)  
(story)   (story)  
Low  

Task  
(story)  

1.  Draw  the  line  for  your  MVP   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

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

26  
User tasks make ideal user stories

27  
User Story Mapping is Collaborative &
Fosters Co-Ownership

28  
User Story Maps help us see things
from a user’s perspective

Colors  for  different  

user  personas  
29  
With User Story Mapping you can test
for Gaps by Walking the Map

30