How do you know that your product works?

Transcription

1 Consultant How do you know that your product works? Colombo Agile Conf, June Father Agile & Lean coach Author

2 ? Todo Doing Done

3 Where s my product? Todo Doing Code committed I m done! User Developer

4 Where s my product? Code committed Tested We re Done! User Developer

5 Code committed Tested In production We re Done! 100% completed requirements No reported defects Wait... is anyone actually using it?

6 Code committed Tested In production People actually use it NOW we re surely done! 100% completed requirements No reported defects Aren t we?

7

8 Code committed Tested In production People actually use it 100% completed requirements No reported defects

9 Code committed Tested In production People actually use it Solves the user s problem 100% completed requirements No reported defects

10 Value of your solution

11 Value of your solution Value of old solution

12 Relative gain Value of your solution Value of old solution

13 Relative Pain/Cost Relative Gain

14 Code committed Tested In production People actually use it Solves the user s problem... in a way that is better than before Relative Pain/Cost Relative Gain

15 Code committed Tested In production People actually use it Solves the user s problem... in a way that is better than before People use it willingly Relative Pain/Cost Relative Gain... and recommend it to others

16 All products start with a Great Idea!

17 Risk Business risk Technical risk Social risk Cost & schedule risk

18 Google Buzz Google Wave Google Answers

19 Assume you are building the WRONG thing! Suppose we re building the wrong thing... How can we find out as quickly as possible? 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

20 Example: Hypotheses Demo video 1. File sync is a problem for people 2. Our product will solve the problem 3. People will want to use our product

21

22 Dropbox MVP

23 Dropbox MVP It drove hundreds of thousands of people to the website. Our beta waiting list went from 5,000 people to 75,000 people literally overnight. Drew It totally blew us away.

24 Paper Prototyping = Lo-tech MVP Credit: Ariel Waldman, on Interaction Design/ Rachel Ilan

25 Pirate metrics Aquisition Activation Retention Referral Revenue AARRR! Do people come? Do they use the product? Do they come back? Do they recommend it to others? Do they pay?

26 Big Bang = Big Risk RISK Cumulative Value

27 Big Projects usually fail. Regardless of process. The secret to project success is to strongly recommend and enforce limits on size and complexity. These two factors trump all other factors. < $1 million > $1 million

28 Agile = Iterative + Incremental Don t try to get it all right from the beginning Don t build it all at once cost value cost RISK value

29 Release must be REALLY easy! Release = Drama! Release! Req Code Test Release seldom Release is big Release is hard Release = Routine Release often Release is small Release is simple

30 Fastest learner wins! Delivery frequency = Speed of learning Stakeholders, Users Feedback, Requests, Data Demos, Releases Development team

31 Improving the Value Curve RISK Big Bang Big increments Small increments Highest value first Value Effort

32 Not like this Like this!

33 Maximize Value, not Output High Output High Value

34 Don t focus on maximizing speed Focus on Minimizing distance MVP

35 A/B stats Idea/Problem Narrative & Prototypes & Metrics Build MVP Radio you can save! Follow your favorite artist Tweak Deploy Analyze data

36 User Product Feedback

37 ensure How do you know that your product works? Who are the stakeholders? 1. Understand the problem 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? 2. Iterate until you ve solved it Minimize the distance to MVP Deliver, measure, adjust continuously