Agile...Looking Back Looking Forward

  • View

  • Download

Embed Size (px)


Keynote delivered by Craig Smith at Agile Encore in Auckland, New Zealand in November 2012. Agile adoption is now becoming more mainstream and, as a community, we are struggling to address the issue of how to take experienced Agile practitioners to the next level, while still supporting those who are beginning their journey. With the "agile" word getting so overloaded, the challenge is to continually innovate without assigning labels or losing focus on our prime objective - to deliver!

Text of Agile...Looking Back Looking Forward

  • 1. CraigSmithImage:

2. Encore! Encore!Image: The Walt Disney Company 3. *Lets take a brief journeyback in time highlights! some selected *These are justImage: The Curiosity Company / 20th Century Fox Television 4. broke the rules, challenged the bureaucratic system that stifledinnovation and hindered progress; spelled out 14 rules and practices." 1943Skunkworksat Lockheed MartinImage: 5. strives for the absolute elimination of waste, overburden andunevenness to allow members to work smoothly and efficiently.1948 Image: System The birth of Lean 6. I believe in this concept, but the implementation describedabove is risky and invites failure. 1970Image: Waterfall & Winston W. Royce 7. Man Month Fred Brooks: The Mythical makes it later.Adding manpower to a late software project 1975Image: / 8. Image: Sigma is a disciplined, data-driven approach and methodology for eliminating defects (toward six standard deviations) in any process 1986Six Sigma sat Motorola 9. ...reduce supervision, combine fragmented tasks, eliminate work thatfails to add value, cut activities within each process to a minimum. 1993Image: Alistair Cockburn:Crystal Clear 10. than either could alone.Together, they accomplish better work more quickly Pair Programming 1995Image: Greenway Productions 11. Image: / exposes every inadequacy or dysfunction within anorganizations product and system development practices. 1995 Ken Schwaber / Jeff Sutherland:Scrum 12. ...reduce supervision, combine fragmented tasks, eliminate work thatfails to add value, cut activities within each process to a minimum. 1997Image: / Jeff De Luca:FeatureDriven Development 13. Adaptive Software Development life cycle comprises of three phases: -Speculation, Collaboration, Learning1999Image: Highsmith: Adaptive Software Development 14. XP starts from the premise that programming is programming, butthat you have to add some activities to sustain it over time 1999 Image: XP: Extreme Programming 15. Image: / you can use continuous integration without using any other parts ofXP its an essential part of competent software development activity. 2000 Martin Fowler: (popularised)ContinuousIntegration 16. We are uncovering better ways of developing software by doing it and helping others do it 2001AgileImage: MGM/UA Entertainment Co. 17. Red Green Refactor 2002 Image: Kent Beck: (published) Test DrivenDevelopment 18. Image: / studies have shown that averaging individual estimatesleads to better results as do group discussions of estimates. 2002James Grenning:Planning Poker 19. Image: / Kanban takes an organizations development process and providesgreater visibility into the status of the work and how it is proceeding. 2007David J. Anderson:Kanban 20. Image: / principles from lean and agile to the process of innovation,helps companies succeed in a business landscape riddled with risk.2008Eric Ries:The Lean Startup 21. Releasing high quality software fast through build, test and deployment automation.2009 ContinuousDeployment /Delivery Image: 22. 2 days, 2 streams, 337 delegates42 speakers, 6 sponsors2009 AgileAustralia 23. AgileEncore! 2012Image: 24. Us ToWhichBringsNowImage: 25. Agile DefinedImage: 26. So manyflavours!Image: 27. Agile? TextbookImage: 28. PureAgile?29Image: 29. Agile?Drunk onImage: 30. JoePublicJust give me the process. I want to deliver something!mage: Columbia Pictures Television 31. Raccoon!Image: 32. 80%40%We haveof IT Organisations* of all Organisations*crossed the chasmImage: * according to Gartner 33. C The AgileSlider AgileTragileFragile 34. agile jobs advertised on SEEK (AU/NZ)1200Success1000= Jobs 800 600 400 2000 Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1 2005 20062007 200820092010 2011 2012 35. ConferenceAttendance Rising90080070060050040030020010002009 2010 2011 2012 Agile Australia Attendees 36. DarwinAgile / Scrum: N/ACommunities Lean Startup: N/A Kanban / Limited WIP: N/A Brisbane Auckland Agile / Scrum: 527 Agile / Scrum: 354PerthLean Startup: 158 Lean Startup: 51Agile / Scrum: 601 Kanban / Limited WIP: 33Kanban / Limited WIP: 8Lean Startup: 234Kanban / Limited WIP: N/A SydneyAgile / Scrum: 1,450AdelaideLean Startup: 289 Agile / Scrum: 39Kanban / Limited WIP: 345 Lean Startup: 70Kanban / Limited WIP: N/A CanberraAgile / Scrum: 59 MelbourneLean Startup: 31 Agile / Scrum: 1,076 Kanban / Limited WIP: N/ALean Startup: 803Kanban / Limited WIP: 362 Wellington Hobart Agile / Scrum: 564 Agile / Scrum: N/A Lean Startup: 436 Lean Startup: N/AKanban / Limited WIP: N/AKanban / Limited WIP: N/A 37. Days?HappyImage: Fuzzy Door Productions / 20th Century Fox Television 38. Decline?Renew or CImage: 39. level?What isthe next CImage: 40. yet? Level 1Have we completed 41 CImage: 41. Looking ForwardImage: 42. Agile inSoftwareImage: 43. WaterScrum FallUpfront project Iterative and Controlled,planningadaptiveinfrequentprocess thatapproach to productiontypicallyachieving the release cyclehappens overall plan that that is governedbetween IT andwas first laid by the business.out in the organizational Water stage. policy andinfrastructureWater-limitationsScrum-Fall 44. Look Left & Right 45. Tools & Developers = Craftsmanship 46Image: Touchstone Television 46. QualityTesters =47Image: 47. Analysts =the Problem Understanding 48Image: Heel & Toe Films / Shore Z Productions / Bad Hat Harry Productions / Universal Media 48. TogetherThe BunchLeaders = Keep 49Image: Redwood Productions / Paramount Television 49. HighPerforming AgileAnalyst /Customer Project Elaboration /Acceptance Manager SpecificationCriteriaHigh Performing AGILEDeveloper AutomationTester 50. Manifesto forSoftwareCraftsmanship 51. Practices RethinkingImage: 52. BasicsUnderstood?Image: 53. Pair ProgrammingImage: 54. ContinuousIntegrationImage: 55