case nextdoor.fi at less2010
Post on 19-Oct-2014
2.495 views
DESCRIPTION
This is the presentation I gave at LESS2010 on 18th of Oct in 2010. The deck describes how we do lean product development and customer development and what are the current results.TRANSCRIPT
Case NextdoorMarko Taipale
1st promise: Predictability
2nd promise: Adaptability
(3rd promise: Continuous
Deployment)
I. What is a (lean) Startup?
II. Nextdoor.fi
III. How do we do it
I. What is a (lean) Startup?
“Startup is a human institution creating a
new product or service under
conditions of extreme uncertainty.”- Eric Ries
It does not state size
Customer
Discovery
Customer
Validation
Customer
Creation
Scale
Company
Customer Development
Customer
Discovery
Customer
Validation
Customer
Creation
Scale
Company
Agile
Product
Development
Data,
feedback,
Insights
Hypotheses,
experiments,
insights
Customer Development
Customer
Discovery
Customer
Validation
Customer
Creation
Scale
Company
Agile
Product
Development
Data,
feedback,
Insights
Hypotheses,
experiments,
insights
Customer Development
Problem Team
Solution Team
Customer
Development
Agile
Product
Development
Business
Model
Iteration
Source: Ann Miura-Ko Maples Investments
Tactical
Strategy
Iterating the business model
- The Pivot
Team vision and discipline over individuals
and interactions (or processes and tools)
Validated learning over working software (or
comprehensive documentation)
Customer discovery over customer
collaboration (or contract negotiation)
Initiating change over responding to change (or following a plan)
http://www.justin.tv/startuplessonslearned#r=POlUU9I~&s=em
II. www.nextdoor.fi
Why?
Who?
What?
120 man days / Beta
-70 functionalities
-50 User interface
(1. day = get some laptops)
30 000 visitors / month
>2 000 active users
>500 open offer/request
3 days lead time
1/day release to production
24/7 monitoring
1/day backups
1/day biz reports
5 integrations
550+ acceptance tests
>80% test coverage
28 IE6 issues
2 bugs (in 3 years)
0 people in operations
0 testers
0 full-time developers
Production bug fix < 1h
III. Our way
Theme
DiscoveryFeatures
Defining
READYDevelopment
Regression Test
Deployment
37 2
Themes Product
Queue
READY
MMFs
2h 2d 2d 6d 15min 1min
Theme
DiscoveryFeatures
Defining
READYDevelopment
Regression Test
Deployment
37 2
Themes Product
Queue
READY
MMFs
2h 2d 2d 6d 15min 1min
From READY to DONE 6 days
Dev time: From NOT STARTED to DONE 8 days
DWT: (PQ size * Dev Time) / capacity = (7 * 8) / 2 = 28 days
Theme
DiscoveryFeatures
Defining
READYDevelopment
Regression Test
Deployment
37 2
Themes Product
Queue
READY
MMFs
2h 2d 2d 6d 15min 1min
From READY to DONE 6 days
Dev time: From NOT STARTED to DONE 8 days
DWT: (PQ size * Dev Time) / capacity = (7 * 8) / 2 = 28 days
Problem team Solution team
Themes
(3)
Product
Queue
(7)
READY
(2)
In Progress
(2)Done
TODO Done
SMART
goals
MMF
Biz Value
Definition of
READY
Definition of
DONE
Updated
metrics
X
Y
Z
Themes
(3)
Product
Queue
(7)
READY
(2)
In Progress
(2)Done
TODO Done
SMART
goals
MMF
Biz Value
Definition of
READY
Definition of
DONE
Updated
metrics
X
Y
Z
Themes
(3)
Product
Queue
(7)
READY
(2)
In Progress
(2)Done
TODO Done
SMART
goals
MMF
Biz Value
Definition of
READY
Definition of
DONE
Updated
metrics
X
Y
Z
Themes
(3)
Product
Queue
(7)
READY
(2)
In Progress
(2)Done
TODO Done
SMART
goals
MMF
Biz Value
Definition of
READY
Definition of
DONE
Updated
metrics
X
Y
Z
PLAN!
Themes
(3)
Product
Queue
(7)
READY
(2)
In Progress
(2)Done
TODO Done
SMART
goals
MMF
Biz Value
Definition of
READY
Definition of
DONE
Updated
metrics
X
Y
Z
Review!
Themes
(3)
Product
Queue
(7)
READY
(2)
In Progress
(2)Done
TODO Done
SMART
goals
MMF
Biz Value
Definition of
READY
Definition of
DONE
Updated
metrics
X
Y
Z
Themes
(3)
Product
Queue
(7)
READY
(2)
In Progress
(2)Done
TODO Done
SMART
goals
MMF
Biz Value
Definition of
READY
Definition of
DONE
Updated
metrics
X
Y
Z
STOP THE LINE
Comments for service offers and requests
Owner: Marko
QUEUE: 1.6.2010
READY: 3.6.2010
DONE: 6.6.20105 days
3 days
Size: S
0
10
20
30
40
50
60
70
80
Nextdoor.fi Cumulative Flow Diagram (2009)
BL READY IP DONE
1st promise: Predictability
2nd promise: Adaptability
(3rd promise: Continuous
Deployment)
Is your message about delivering features as fast as possible?
Who cares about velocity?
We can work on highest priority story – who cares?
Nr 1 waste =
Unused features
Building a feature
maybe the wrong
answer
Philosophy
• Validated learning (over working software)
• Doing only things that match the demand
• Team vision and discipline
• Continuous improvement
I help companies to improve by
showing what I have done
how I have done it and
what I have learned about it.
I am a CTO of a lean startup
Marko Taipale
@markotaipale
huitale.blogspot.com
Photo credits
Flickr users
http://www.flickr.com/photos/kodomut/
http://www.flickr.com/photos/amagill/
http://www.flickr.com/photos/themarmot/
http://www.flickr.com/photos/unloveable/
http://www.flickr.com/photos/shapourbahrami/
http://www.flickr.com/photos/thatguyfromcchs0
http://www.flickr.com/photos/fxtreme/
http://www.flickr.com/photos/aussiegall
http://www.flickr.com/photos/lululemonathletica
http://www.flickr.com/photos/4yas
http://www.flickr.com/photos/sualk61/
http://www.flickr.com/photos/can3ro55o/
http://www.flickr.com/photos/jwdill/
http://www.flickr.com/photos/minidriver/
http://www.flickr.com/photos/donaldmacleod/
http://www.flickr.com/photos/jburgin/