Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Prototyping and Agile Development @ Denver Startup Week

Robbie Clutton
September 19, 2013

Prototyping and Agile Development @ Denver Startup Week

Many of us take agile and lean for granted, we'll take a walk through what the world looked like before through 'best practices' and examples of failures. We'll then turn our attention to prototypes from other industries as well as technology and how they help us through the build-measure-learn cycle. Finally we'll look at tools which can help us get to market quicker without inhibitive costs.

This talk was given at Denver Startup Week, Thursday 19th September 2013.

Robbie Clutton

September 19, 2013
Tweet

More Decks by Robbie Clutton

Other Decks in Technology

Transcript

  1. @robb1e Please propose a system to satisfy the attached requirements

    specification. Specify date of delivery and total cost.
  2. @robb1e • Customers can change their minds • Suppliers aren’t

    encouraged to sacrifice quality as soon as something goes wrong • Customers’ and suppliers’ interests are contractually aligned • The knowledge that both parties gain during the project can influence the finished product. Optional Scope Contracts
  3. @robb1e • Request for tender announced • Cheapest bid usually

    wins • Pay company several $m for licenses • Then another few $m for configuration • By the time it’s up and running, it’s out of date Vendor driven development
  4. @robb1e • Software replaces paper-based system • Aims to improve

    dispatch time • Keep track of where ambulance (units) are so closest can be sent to location • Big bang release 1992 London Ambulance Dispatch disaster http://en.wikipedia.org/wiki/London_Ambulance_Service#System_failures
  5. @robb1e • Multiple units sent to the same address •

    No units sent to other addresses • Calls got lost • System became congested 1992 London Ambulance Dispatch disaster http://en.wikipedia.org/wiki/London_Ambulance_Service#System_failures
  6. @robb1e Indepentent (newspaper), October 1992 Ambulance chief quits after patients

    die in computer failure. http://www.independent.co.uk/news/ambulance-chief-quits-after-patients-die-in-computer-failure-1560111.html
  7. @robb1e • Originally called “Just in time production” • Goals

    are all about eliminating waste • Principles are about continuous improvement, people and process Toyota Production System http://en.wikipedia.org/wiki/Toyota_Production_System
  8. @robb1e Agile manifesto http://agilemanifesto.org/ Individuals and interactions over processes and

    tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
  9. @robb1e • Story writing • Iteration planning • Daily stand-ups

    • Customer acceptance • Retrospectives Agile process Agile processes enable customer collaboration and empower the individual
  10. @robb1e Kellan Elliot McCrea, 2012 Change is what you should

    be optimizing for. You never know what's coming next.
  11. @robb1e • Test driven development • Pair programming • Continuous

    integration • Automating everything • Continuous refactoring Agile engineering Agile engineering practices promote working software early and enables easier change
  12. @robb1e • Eliminate waste • Amplify learning • Decide as

    late as possible • Deliver as fast as possible • Empower the team • Build integrity in • See the whole Lean software development http://en.wikipedia.org/wiki/Lean_software_development
  13. @robb1e • Minimum viable product • Continuous deployment • Split

    testing • Actionable metrics • Pivot Lean startup http://en.wikipedia.org/wiki/Lean_Startup
  14. @robb1e Eric Ries The goal of a lean startup is

    to move through the build-measure- learn feedback loop as quickly as possible
  15. @robb1e • easel.io • proto.io • groosoft.com/ blueprint • appcooker.com

    • axure.com • pidoco.com Prototyping tools • finto • ratchet • invision • hotgloo • middleman • Keynote • Powerpoint
  16. @robb1e • Sketch 8 ideas in 5 minutes • Pitch

    ideas to team • Team critique the ideas • Repeat Design Studio
  17. @robb1e • Day 1: Understand • Day 2: Diverge •

    Day 3: Decide • Day 4: Prototype • Day 5: Validate Rapid Prototyping Process
  18. @robb1e • Cross skilled team • Present the business /

    concept • Competition analysis • Success metrics • Existing research / analytics • Team interviews Understand
  19. @robb1e • Conflict resolution • Best shot or battle royale?

    • Create tests for assumptions • Whiteboard the user story Converge
  20. @robb1e • Invite users to come in • Test against

    assumptions and conflicts • Be nice to the tester • Take lots of notes • Create a scorecard Validate
  21. @robb1e • Dodgeball => Foursquare • MySpace => Facebook •

    Rocket Internet Ideas/others can be prototypes too http://en.wikipedia.org/wiki/Dodgeball_(service) http://www.rocket-internet.de/ http://www.businessweek.com/articles/2012-02-29/the-germany-website-copy-machine
  22. @robb1e • Features that have hypotheses • Hypotheses that can

    be easily validated • Code that is always production ready • Code that is easy to change Goals
  23. @robb1e Ron Jefferies, ~2005 Always implement things when you actually

    need them, never when you just foresee that you need them
  24. @robb1e Francis Hwang, 2012 The biggest expense for a startup

    is your time. Not your laptop, not your hosting bill, not your office, but the hours in your day.
  25. @robb1e Paul Hammond, 2012 Hosted services are usually cheaper and

    better than anything you will build. Use them.