Your SlideShare is downloading. ×
The     scienceof productdevelopment                      James Birchler (@JamesBirchler)                      VP Engineer...
Questions & comments?      @jamesbirchler
Thescientific method        is      based       on
experimentation
$                                  IMVU Revenue GrowthQtr   Q106 Q206 Q306 Q406 Q107 Q207 Q307 Q407 Q108 Q208 Q308 Q408 Q1...
$                                  IMVU Revenue GrowthQtr   Q106 Q206 Q306 Q406 Q107 Q207 Q307 Q407 Q108 Q208 Q308 Q408 Q1...
@copernicus
@copernicus#inquisition
@copernicus
@Giordano_Bruno
@Galileo
@Jamesbirchler
ExperimentationIS GOOD
RIGHT?
Ask Question                   Got Do Research Hypothesis                 Science?    TestAnalyze Data ConclusionReport Re...
Question    Results                              Research               ScientificConclusion                Method        ...
Question    Results                              Research                  Scientific                              #leanst...
Question    Results                              Research                                                                 ...
Ask Question Do Research Hypothesis    TestAnalyze Data ConclusionReport Results        Looks a lot like the scientific me...
culture ofExperimentation
Okay, I’ll run an    Okay, I’ll run an                         Okay, I’ll run an    experiment!                   Okay, I’...
Keep itsimple
if( setup_experiment(...) == "control" ) {    // do it the old way} else {// do it the new way                            ...
SimpleTo manage
SimpleTo share
embracefailure
Freedom    toExperiment
What could possibly go wrong?
simple   toScrew up
What Not to do
Start with use cases                       X                       X
– Laura Klein, Principal, Users Know
ProductDevelopment
Measure
5whys
5whys   Root Cause:     Fix this!
ProcessExperiments
Dogma
Handling Interrupts…
Measuring value to customers…
Keep your team Together…                  •                  •                  •
Technical Project Reviews…                   •                   •                   •                   •
Self Selecting Teams…                    •                    •
Scrum 2.0: Continuous Planning
Have a “Fixer”
Small Team + No rules=Big Win
Recap…
credits   Thanks
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
SF Lean Startup Circle: The New Science of Product Development
Upcoming SlideShare
Loading in...5
×

SF Lean Startup Circle: The New Science of Product Development

19,314

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 lecture 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.

Takeaway: Attendees will learn how IMVU continuously improves product development using the Scientific Method, Agile, XP, and Scrum supported by strong user experience design. Strategies to support experimental learning (retrospectives, postmortems, and 5 Whys) will be reviewed along with practical examples.

Published in: Technology, Business
6 Comments
28 Likes
Statistics
Notes
No Downloads
Views
Total Views
19,314
On Slideshare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
0
Comments
6
Likes
28
Embeds 0
No embeds

No notes for slide

Transcript of "SF Lean Startup Circle: The New Science of Product Development"

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

×