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

Prototyping and Agile Development @ Denver Startup Week

1668868370ee5829339e06031ad0b145?s=47 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.

1668868370ee5829339e06031ad0b145?s=128

Robbie Clutton

September 19, 2013
Tweet

More Decks by Robbie Clutton

Other Decks in Technology

Transcript

  1. @robb1e Robbie Clutton Prototyping & agile development

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

    specification. Specify date of delivery and total cost.
  3. http://www.flickr.com/photos/26420411@N02/3062930943/

  4. @robb1e Four variables in project management: time, cost, quality and

    scope
  5. @robb1e You say... Lets fix scope, cost and time taking

    a hit in quality
  6. http://www.flickr.com/photos/andrewbain/2228633614/

  7. @robb1e

  8. @robb1e You say... Let’s fix scope, quality and time at

    any cost.
  9. @robb1e We’re working every weekend until this project is finished.

  10. @robb1e

  11. @robb1e You say... Lets fix scope and quality with variable

    costs and time.
  12. None
  13. http://www.flickr.com/photos/virtualwayfarer/5600094306

  14. @robb1e You say... Lets fix quality, time and cost then

    have optional scope.
  15. @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
  16. @robb1e Heraclitus, ~500BC Change is the only constant

  17. @robb1e History lesson

  18. None
  19. None
  20. @robb1e Richard Feynman We are never right, we can only

    be sure we’re wrong.
  21. None
  22. None
  23. @robb1e Getting Real by 37 Signals Build half a product,

    not a half-ass product.
  24. @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
  25. @robb1e The Guardian, January 2006 MPs urge inquiry into delay

    of £6.2bn ($10bn) NHS software
  26. @robb1e Some marketing genius No one ever got fired for

    hiring IBM
  27. http://www.flickr.com/photos/teessideambulances/5570963359

  28. @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
  29. @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
  30. @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
  31. http://www.flickr.com/photos/wwward0/6572799971

  32. @robb1e Toyota production system (1948)

  33. http://www.flickr.com/photos/toyotamheurope/8472007819

  34. http://www.flickr.com/photos/davegray/6354044779

  35. @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
  36. ‘Lean Enterprise’ 2003

  37. @robb1e Extreme Programming (1999)

  38. @robb1e • Coding • Testing • Listening • Designing Activities

  39. @robb1e • Communication • Simplicity • Courage • Feedback •

    Respect Values
  40. None
  41. @robb1e Agile manifesto (2001)

  42. @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.
  43. @robb1e http://www.agilemodeling.com/essays/costOfChange.htm

  44. @robb1e • Story writing • Iteration planning • Daily stand-ups

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

    be optimizing for. You never know what's coming next.
  46. http://www.flickr.com/photos/psd/8591351239

  47. @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
  48. process practices #win

  49. @robb1e Lean software development (2003)

  50. @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
  51. @robb1e Mary and Tom Poppendieck Think big, act small, fail

    fast, learn rapidly
  52. None
  53. @robb1e Lean startup (2008-2011)

  54. @robb1e • Minimum viable product • Continuous deployment • Split

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

    to move through the build-measure- learn feedback loop as quickly as possible
  57. None
  58. http://www.flickr.com/photos/54459164@N00/8003749394

  59. @robb1e • Acquisition • Activation • Retention • Referral •

    Revenue Startup Metrics for pirates
  60. @robb1e Prototyping

  61. http://en.wikipedia.org/wiki/Airbus_A350_XWB

  62. http://www.bikeradar.com/news/article/specialized-unveils-in-house-wind-tunnel-37363/

  63. http://www.carbodydesign.com/archive/2008/01/29-mercedes-benz-advanced-design-studio-como/

  64. @robb1e You say... Can you build a high fidelity prototype

    for a software application?
  65. http://www.flickr.com/photos/psd/9626226855

  66. http://astridforscreen.wordpress.com/2010/09/05/paper-prototyping/

  67. http://arielwaldman.com/projects/interaction-design/

  68. http://balsamiq.com

  69. @robb1e • easel.io • proto.io • groosoft.com/ blueprint • appcooker.com

    • axure.com • pidoco.com Prototyping tools • finto • ratchet • invision • hotgloo • middleman • Keynote • Powerpoint
  70. http://www.flickr.com/photos/lfittl/6940448421/in/photostream/

  71. @robb1e Design Studio

  72. @robb1e • Sketch 8 ideas in 5 minutes • Pitch

    ideas to team • Team critique the ideas • Repeat Design Studio
  73. @robb1e Google Ventures

  74. @robb1e • Day 1: Understand • Day 2: Diverge •

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

    concept • Competition analysis • Success metrics • Existing research / analytics • Team interviews Understand
  76. @robb1e • Design studio Diverge

  77. @robb1e • Conflict resolution • Best shot or battle royale?

    • Create tests for assumptions • Whiteboard the user story Converge
  78. @robb1e • Keynote with Keynotopia • Review • Iterate Prototype

  79. @robb1e • Invite users to come in • Test against

    assumptions and conflicts • Be nice to the tester • Take lots of notes • Create a scorecard Validate
  80. http://www.flickr.com/photos/philhawksworth/5196977902

  81. None
  82. None
  83. @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
  84. @robb1e Beyond prototyping

  85. @robb1e • Features that have hypotheses • Hypotheses that can

    be easily validated • Code that is always production ready • Code that is easy to change Goals
  86. @robb1e Most developers Prototypes tend to find a way into

    production
  87. @robb1e Kent Beck Make it work, make it right, make

    it fast
  88. @robb1e Joel Spolsky, 2001 If it’s a core business function

    - do it yourself, no matter what.
  89. @robb1e Ron Jefferies, ~2005 Always implement things when you actually

    need them, never when you just foresee that you need them
  90. @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.
  91. @robb1e Paul Hammond, 2012 Hosted services are usually cheaper and

    better than anything you will build. Use them.
  92. @robb1e Mary and Tom Poppendieck Think big, act small, fail

    fast, learn rapidly
  93. @robb1e Q/A