2008 09 06 Eric Ries Haas Columbia Customer Development Engineering
Upcoming SlideShare
Loading in...5
×
 

2008 09 06 Eric Ries Haas Columbia Customer Development Engineering

on

  • 25,542 views

 

Statistics

Views

Total Views
25,542
Views on SlideShare
7,816
Embed Views
17,726

Actions

Likes
21
Downloads
370
Comments
0

18 Embeds 17,726

http://www.startuplessonslearned.com 16551
http://startuplessonslearned.blogspot.com 1097
http://translate.googleusercontent.com 18
http://theleadershipprogram.blogspot.com 17
http://www.slideshare.net 16
http://feeds.feedburner.com 5
http://fx3x.blogspot.com 5
http://www.the-innovative-entrepreneur.com 3
http://theleadershipprogram.blogspot.jp 3
http://theleadershipprogram.blogspot.in 3
http://theleadershipprogram.blogspot.com.es 1
http://webcache.googleusercontent.com 1
http://www.blogger.com 1
http://207.46.192.232 1
http://awurl.com 1
http://static.slideshare.net 1
http://74.125.47.132 1
http://web.archive.org 1
More...

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    2008 09 06 Eric Ries Haas Columbia Customer Development Engineering 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering Presentation Transcript

    • Customer Development Engineering Eric Ries
    • Customer Development Engineering
      • How do you build a product development team that can thrive in a startup environment?
      • Let's start with the traditional way... Waterfall
        • “The waterfall model is a sequential software development model in which development is seen as flowing steadily downwards through the phases of requirements analysis, design, implementation, testing (validation), integration, and maintenance.”
    • Problem: known Waterfall Unit of progress: Advance to Next Stage
    • Problem: known Waterfall Unit of progress: Advance to Next Stage Solution: known
    • Problem: known Solution: known Waterfall Unit of progress: Advance to Next Stage
    • Agile Development
      • “ Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.” - http://agilemanifesto.org/
      • Embrace Change
        • Build what you need today
        • Process-oriented development so change is painless
      • Prefer flexibility to perfection
        • Ship early and often
        • Test-driven to find and prevent bugs
        • Continuous improvement vs. ship-and-maintain
    • Problem: known Agile (XP) “ Product Owner” or in-house customer Unit of progress: Working Software, Features
    • Problem: known Solution: unknown Agile (XP) “ Product Owner” or in-house customer Unit of progress: Working Software, Features
    • Problem: known Solution: unknown Agile (XP) “ Product Owner” or in-house customer Unit of progress: Working Software, Features
    • Problem: unknown Customer Development Engineering Unit of progress: Learning about Customers Hypotheses, experiments, insights
    • Problem: unknown Solution: unknown Customer Development Engineering Unit of progress: Learning about Customers Hypotheses, experiments, insights
    • Customer Development Engineering
      • How do you build a product development team that can thrive in a startup environment?
      • Let's start with the traditional way... Waterfall
        • “The waterfall model is a sequential software development model in which development is seen as flowing steadily downwards through the phases of requirements analysis, design, implementation, testing (validation), integration, and maintenance.”
    • Problem: unknown Solution: unknown Customer Development Engineering Unit of progress: Learning about Customers Hypotheses, experiments, insights Data, feedback, insights
    • Traditional Agile (XP) Tactics
      • Planning game
        • programmers estimate effort of implementing cust stories
        • customer decides about scope and timing of releases
      • Short releases
        • new release every 2-3 months
      • Simple design
        • emphasis on simplest design
      • Testing
        • development test driven. Unit tests before code
      • Refactoring
        • restructuring and changes to simplify
      • Pair Programming
        • 2 people at 1 computer
      • Split-test (A/B) experimentation
      • Extremely rapid deployment
        • Continuous deployment, if possible
        • At IMVU, 20-30 times per day on average
      • Just-in-time architecture and infrastructure
        • Incremental investment for incremental benefit
        • Software “immune system” to prevent defects
      • Five why's
        • Use defects to drive infrastructure investments
      Customer Development Engineering Tactics
    • Five Why's
      • Any defect that affects a stakeholder is a learning opportunity
      • We’re not done until we’ve addressed the root cause…
      • … including, why didn’t any of our prevention tactics catch it?
      • Technique is to “ask why five times” to get to the root cause
    • Five Why's Example
      • For example:
        • Why did we change the software so that we don't make any money anymore?
        • Why didn’t operations get paged?
        • Why didn’t the cluster immune system reject the change?
        • Why didn’t automated tests go red and stop the line?
        • Why wasn’t the engineer trained not to make the mistake?
      • We’re not done until we’ve taken corrective action at all five levels