2008 09 06 Eric Ries Haas Columbia Customer Development Engineering

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    5 Favorites

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

    1. Customer Development Engineering Eric Ries
    2. 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.”
    3. Problem: known Waterfall Unit of progress: Advance to Next Stage
    4. Problem: known Waterfall Unit of progress: Advance to Next Stage Solution: known
    5. Problem: known Solution: known Waterfall Unit of progress: Advance to Next Stage
    6. 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
    7. Problem: known Agile (XP) “ Product Owner” or in-house customer Unit of progress: Working Software, Features
    8. Problem: known Solution: unknown Agile (XP) “ Product Owner” or in-house customer Unit of progress: Working Software, Features
    9. Problem: known Solution: unknown Agile (XP) “ Product Owner” or in-house customer Unit of progress: Working Software, Features
    10. Problem: unknown Customer Development Engineering Unit of progress: Learning about Customers Hypotheses, experiments, insights
    11. Problem: unknown Solution: unknown Customer Development Engineering Unit of progress: Learning about Customers Hypotheses, experiments, insights
    12. 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.”
    13. Problem: unknown Solution: unknown Customer Development Engineering Unit of progress: Learning about Customers Hypotheses, experiments, insights Data, feedback, insights
    14. 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
    15. 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
    16. 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

    + guest472f47guest472f47, 2 years ago

    custom

    3094 views, 5 favs, 6 embeds more stats

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 3094
      • 1751 on SlideShare
      • 1343 from embeds
    • Comments 0
    • Favorites 5
    • Downloads 111
    Most viewed embeds
    • 1097 views on http://startuplessonslearned.blogspot.com
    • 242 views on http://www.startuplessonslearned.com
    • 1 views on http://www.blogger.com
    • 1 views on http://feeds.feedburner.com
    • 1 views on http://fx3x.blogspot.com

    more

    All embeds
    • 1097 views on http://startuplessonslearned.blogspot.com
    • 242 views on http://www.startuplessonslearned.com
    • 1 views on http://www.blogger.com
    • 1 views on http://feeds.feedburner.com
    • 1 views on http://fx3x.blogspot.com
    • 1 views on http://74.125.47.132

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories