The New Science of Product Development

3,531 views

Published on

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.

Published in: Technology, Business
1 Comment
5 Likes
Statistics
Notes
  • The words --rapidly iterate -- may be a bad choice when refuring to testing and continous development on IMVU ?
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
3,531
On SlideShare
0
From Embeds
0
Number of Embeds
1,317
Actions
Shares
0
Downloads
0
Comments
1
Likes
5
Embeds 0
No embeds

No notes for slide

The New Science of Product Development

  1. 1. The scienceof productdevelopment James Birchler (@JamesBirchler) VP Engineering Management, IMVU Los Angeles Lean Startup Circle, December 7, 2011
  2. 2. Questions & comments? @jamesbirchler
  3. 3. Thescientific method is based on
  4. 4. experimentation
  5. 5. $ IMVU Revenue GrowthQtr Q106 Q206 Q306 Q406 Q107 Q207 Q307 Q407 Q108 Q208 Q308 Q408 Q109 Q209 Q309 Q409
  6. 6. $ IMVU Revenue GrowthQtr Q106 Q206 Q306 Q406 Q107 Q207 Q307 Q407 Q108 Q208 Q308 Q408 Q109 Q209 Q309 Q409
  7. 7. @copernicus#inquisition
  8. 8. @copernicus#inquisition
  9. 9. @copernicus
  10. 10. @Giordano_Bruno
  11. 11. @Giordano_Bruno
  12. 12. @Galileo
  13. 13. @Galileo
  14. 14. @Galileo
  15. 15. @Jamesbirchler
  16. 16. ExperimentationIS GOOD
  17. 17. RIGHT?
  18. 18. Ask Question Got Do Research Hypothesis Science? TestAnalyze Data ConclusionReport Results
  19. 19. Question Results Research ScientificConclusion Method Hypothesis Analyze Data Test
  20. 20. Question Results Research Scientific #leanstartupConclusion Method Hypothesis Analyze Data Test
  21. 21. Question Results Research Quack. Scientific #leanstartupConclusion Method Hypothesis Analyze Data Test An Alleged “duck”
  22. 22. Ask Question Do Research Hypothesis TestAnalyze Data ConclusionReport Results Looks a lot like the scientific method (it is!)…
  23. 23. culture ofExperimentation
  24. 24. 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!
  25. 25. Keep itsimple
  26. 26. if( setup_experiment(...) == "control" ) { // do it the old way} else {// do it the new way Simple To code}
  27. 27. SimpleTo manage
  28. 28. SimpleTo share
  29. 29. embracefailure
  30. 30. Freedom toExperiment
  31. 31. What could possibly go wrong?
  32. 32. simple toScrew up
  33. 33. What Not to do
  34. 34. Do this: Start with use cases X X
  35. 35. – Laura Klein, Principal, Users Know
  36. 36. ProductDevelopment
  37. 37. Measure
  38. 38. 5whys Root Cause: Fix this!
  39. 39. ProcessExperiments
  40. 40. Dogma
  41. 41. Handling Interrupts…
  42. 42. Scrum 2.0: Continuous Planning
  43. 43. Keep your team Together… • • •
  44. 44. Have a “Fixer”
  45. 45. Technical Project Reviews… • • • •
  46. 46. Small Team + No rules=Big Win
  47. 47. Self Selecting Teams… • •
  48. 48. Shake things up
  49. 49. Recap…
  50. 50. credits Thanks

×