IMVU is referred to as the first "Lean Startup", and was the proving ground for applying Build-Measure-Learn (the Scientific Method) to rapidly iterate and continuously improve its product development process, resulting in a valuable strategic advantage and highly productive, happy, and motivated teams. This presentation focuses on IMVU's continuous improvement to product development process through experimentation. Success factors are reviewed, including a culture that values and supports experimentation and learning, Agile and XP engineering practices (which support iterative development), and strong product vision and user experience design. Recent product development process experiments will be shared.

1. The science
of product
development
James Birchler (@JamesBirchler)
VP Engineering Management, IMVU
Los Angeles Lean Startup Circle, December 7, 2011

2. Questions & comments?
@jamesbirchler

3. The
scientific method
is
based
on

4. experimentation

7. $
IMVU Revenue Growth
Qtr Q1'06 Q2'06 Q3'06 Q4'06 Q1'07 Q2'07 Q3'07 Q4'07 Q1'08 Q2'08 Q3'08 Q4'08 Q1'09 Q2'09 Q3'09 Q4'09

8. $
IMVU Revenue Growth
Qtr Q1'06 Q2'06 Q3'06 Q4'06 Q1'07 Q2'07 Q3'07 Q4'07 Q1'08 Q2'08 Q3'08 Q4'08 Q1'09 Q2'09 Q3'09 Q4'09

10. @copernicus
#inquisition

11. @copernicus
#inquisition

12. @copernicus

13. @Giordano_Bruno

14. @Giordano_Bruno

15. @Galileo

16. @Galileo

17. @Galileo

20. @Jamesbirchler

21. Experimentation
IS GOOD

22. RIGHT?

23. Ask Question
Got
Do Research
Hypothesis
Science?
Test
Analyze Data
Conclusion
Report Results

24. Question
Results Research
Scientific
Conclusion
Method Hypothesis
Analyze
Data Test

26. Question
Results Research
Scientific #leanstartup
Conclusion
Method Hypothesis
Analyze
Data Test

27. Question
Results Research
Quack.
Scientific #leanstartup
Conclusion
Method Hypothesis
Analyze
Data Test An Alleged “duck”

28. Ask Question
Do Research
Hypothesis
Test
Analyze Data
Conclusion
Report Results
Looks a lot like the scientific method (it is!)…

29. culture of
Experimentation

30. Okay, I’ll run an
Okay, I’ll run an
Okay, I’ll run an experiment! Okay, I’ll run
experiment! Okay, I’ll run an
experiment! experiment
experiment!
Okay, I’ll run an
experiment!
Let’s keep this
Okay, I’ll run an
simple! Okay, I’ll run an
experiment!
Prove your idea experiment!
is the best!

31. Keep it
simple

32. if( setup_experiment(...) == "control" ) {
// do it the old way
} else {
// do it the new way
Simple
To code
}

33. Simple
To manage

34. Simple
To share

35. embrace
failure

39. Freedom
to
Experiment

40. What could possibly go wrong?

41. simple
to
Screw up

48. What Not to do

49. Do this: Start with use cases
X
X

52. – Laura Klein, Principal, Users Know

59. Product
Development

64. Measure

72. 5
whys
Root Cause:
Fix this!

75. Process
Experiments

76. Dogma

77. Handling Interrupts…

79. Scrum 2.0: Continuous Planning

80. Keep your team Together…
•
•
•

81. Have a “Fixer”

82. Technical Project Reviews…
•
•
•
•

83. Small Team + No rules=Big Win

84. Self Selecting Teams…
•
•

85. Shake things up

86. Recap…

87. credits Thanks