Agile crash course - how to build bad software

  • Published on
    18-Feb-2017

  • View
    173

  • Download
    1

Transcript

<ul><li><p>How to build bad software</p></li><li><p>The problem</p><p>Strong</p><p>LightCheap</p></li><li><p>The problem</p><p>Strong</p><p>Light</p><p>Cheap</p></li><li><p>The problem</p><p>Strong</p><p>Light</p><p>Cheap</p></li><li><p>The problem</p><p>Strong</p><p>Light</p><p>Cheap</p></li><li><p>The problem</p><p>Strong</p><p>LightCheap</p></li><li><p>The problem</p><p>Scope</p><p>QualityTime/cost</p></li><li><p>The solution according to waterfall...</p><p>Functional Requirements Document</p><p>Schedule of work</p></li><li><p>The solution according to waterfall...</p></li><li><p>What if you could fix time, cost AND quality?</p></li><li><p>The agile manifesto</p></li><li><p>The agile manifesto</p></li><li><p>As a... I want a... So I can</p><p>The user story</p><p>Member of the library An online accountChange how long I have </p><p>borrowed a book for without going back into the library</p><p>User Feature Benefit</p></li><li><p>Backlog of stories1 2 3</p><p>5 8 13</p><p>21</p><p>Sprint</p><p>In o</p><p>rder</p><p> of i</p><p>ncre</p><p>asin</p><p>g p</p><p>rior</p><p>ity</p></li><li><p>Sprint board</p></li><li><p>Pulled from backlog into </p><p>sprint</p><p>Who is working on it?</p><p>Stan (for the moment)</p><p>UAT (User Acceptance </p><p>Testing)</p><p>Fixed?</p><p>DoD(Definition of done)</p><p>No Yes</p></li><li><p>Burndown chart</p></li><li><p>Sprint retrospective</p></li><li><p>The agile manifesto</p></li><li><p>I spent 15 years breeding faster horses</p></li><li><p>focus is the art of saying no</p><p>MVP</p></li><li><p>The agile manifesto</p></li><li><p>The problem with FRDs and SoWs</p></li><li><p>Iterative development</p></li><li><p>The agile manifesto</p></li><li><p>User-centric design</p></li><li><p>Lean</p></li><li><p>the aggregation of marginal gains</p><p>The new HOT PANTS by Team GB... </p></li><li><p>Iterative development</p></li><li><p> Fix time, cost and quality and compromise on none Transparent communication in the team Get to market quickly Respond to a changing market</p><p>Arrive at the final product in predictable, incremental steps &amp; build the right thing for the right audience</p><p>Whats the point of Agile anyway?</p></li></ul>