37
Author Father Agile & Lean coach www.crisp.se Consultant Henrik Kniberg [email protected] @HenrikKniberg How do you know that your product works? Colombo Agile Conf, June 2014

How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Embed Size (px)

Citation preview

Page 1: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Author

Father

Agile & Lean coach

www.crisp.se

Consultant Henrik Kniberg [email protected]

@HenrikKniberg

How do you know that your product works? Colombo Agile Conf, June 2014

Page 2: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

Todo Doing Done ?

Page 3: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Todo Doing Code committed

Henrik Kniberg

Where’s my product?

User I’m done!

Developer

Page 4: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

Code committed

Tested

Where’s my product?

User We’re Done!

Developer

Page 5: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

In production

We’re Done!

Wait... is anyone actually using it?

Code committed

100% completed requirements No reported defects

Tested

Page 6: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

People actually use it

NOW we’re surely done!

Aren’t we? 100% completed requirements No reported defects

In production

Code committed

Tested

Page 7: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

http://www.youtube.com/watch?v=FWTtcOQjOXI

Page 8: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

People actually use it

100% completed requirements No reported defects

In production

Code committed Tested

Page 9: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

People actually use it

100% completed requirements No reported defects

In production

Code committed Tested Solves the

user’s problem

Page 10: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

Value of your solution

Page 11: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

Value of your solution

Value of old solution

Page 12: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Value of old solution

Relative gain

Value of your solution

Henrik Kniberg

Page 13: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

Relative Gain

Relative Pain/Cost

Page 14: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

People actually use it

In production

Code committed Tested Solves the

user’s problem

... in a way that is better than before

Relative Gain

Relative Pain/Cost

Page 15: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

Relative Gain

Relative Pain/Cost

People actually use it

In production

Code committed Tested Solves the

user’s problem

... in a way that is better than before

... and recommend it

to others

People use it willingly

Page 16: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

All products start with a Great Idea!

Henrik Kniberg

Page 17: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Risk

Henrik Kniberg

Business risk

Social risk

Cost & schedule risk

Technical risk

Page 18: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

Google Buzz

Google Wave

Google Answers

Page 19: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Assume you are building the WRONG thing!

•  List your hypotheses •  Build an MVP to validate/invalidate it

•  ”Minimum Viable Product” – the fastest & cheapest thing you can build to field-test your hypothesis

Henrik Kniberg

Suppose we’re building the wrong

thing....

How can we find out as quickly as

possible?

Page 20: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Example:

Henrik Kniberg

2. Our product will solve the problem

1. File sync is a problem for people

Hypotheses Demo video

3. People will want to use our product

Page 21: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

Page 22: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Dropbox MVP

Henrik Kniberg

Page 23: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg Drew

Dropbox MVP

It totally blew us away.

Our beta waiting list went from 5,000 people to 75,000

people literally overnight.

It drove hundreds of thousands of people to the website.

Page 24: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Paper Prototyping = Lo-tech MVP

Credit: Ariel Waldman, on Interaction Design/ Rachel Ilan http://chiefdisruptionofficer.com/helpful-rapid-prototyping-methods-and-tools-to-bring-digital-ideas-to-life-fast/

Page 25: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Pirate metrics

Henrik Kniberg

Aquisition

Activation

Retention Referral Revenue

AARRR! Do people

come?

Do they use the product?

Do they come back?

Do they pay?

Do they recommend it to others?

Page 26: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

RISK

Big Bang = Big Risk

Henrik Kniberg

Cumulative Value

Page 27: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Big Projects usually fail. Regardless of process.

Henrik Kniberg

< $1 million > $1 million

”The secret to project success is to strongly recommend and enforce limits on size

and complexity.”

”These two factors trump all other factors.”

Page 28: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Agile = Iterative + Incremental

Henrik Kniberg

Don’t try to get it all right from the beginning

Don’t build it all at once

cost value

cost value

RISK

Page 29: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Release must be REALLY easy!

Henrik Kniberg

Req Code Test

Release!

Release = Drama!

Release = Routine

Release often

Release is small

Release seldom

Release is big

Release is hard

Release is simple

Page 30: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Fastest learner wins! Delivery frequency = Speed of learning

Henrik Kniberg

Feedback, Requests, Data

Demos, Releases

Development team

Stakeholders, Users

Page 31: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Improving the Value Curve

Henrik Kniberg

Big Bang Big increments Small increments Highest value first

Value

Effort

RISK

Page 32: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

1

1

2 3

2 3

4

5 4

Not like this....

Like this!

Page 33: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

Maximize Value, not Output High Output

High Value

Page 34: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

MVP

Don’t focus on maximizing speed

Focus on Minimizing distance

Page 35: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

Analyze data

Narrative & Prototypes & Metrics

Build MVP

Deploy Tweak

“Radio you can save!”

A/B stats

Idea/Problem

“Follow your favorite artist”

Page 36: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Henrik Kniberg

User Feedback

Product

Page 37: How do you know that your product works?': Henrik Kniberg @ Colombo Agile Conference 2014

Deliver, measure, adjust continuously

How do you know that your product works?

Henrik Kniberg

ensure

1. Understand the problem

2. Iterate until you’ve solved it

Who are the stakeholders?

What need do they have, that we want to solve?

How will we know when we’ve solved

it?

How will we know if we’re moving in the right direction?

Minimize the distance to MVP