agile revisited
play

Agile Revisited Dan North @tastapod 1990s development @tastapod - PowerPoint PPT Presentation

Agile Revisited Dan North @tastapod 1990s development @tastapod 1990s development Large projects @tastapod 1990s development Large projects Functional silos @tastapod 1990s development Large projects Functional silos Slow, fragmented


  1. Agile Revisited Dan North @tastapod

  2. 1990s development @tastapod

  3. 1990s development Large projects @tastapod

  4. 1990s development Large projects Functional silos @tastapod

  5. 1990s development Large projects Functional silos Slow, fragmented technology @tastapod

  6. 1990s development Large projects Functional silos Slow, fragmented technology Process modelled on Civil Engineering @tastapod

  7. Civil Engineering @tastapod

  8. Civil Engineering Cost of errors rises exponentially @tastapod

  9. Civil Engineering Cost of errors rises exponentially Assurance through formal hand-offs @tastapod

  10. Civil Engineering Cost of errors rises exponentially Assurance through formal hand-offs Plan is intolerant of slippage @tastapod

  11. Civil Engineering Cost of errors rises exponentially Assurance through formal hand-offs Plan is intolerant of slippage Hand-offs are detailed and expensive @tastapod

  12. Software Engineering Assumes : Cost of errors rises exponentially Assumes : Assurance through formal hand-offs Plan is intolerant of slippage Hand-offs are detailed and expensive @tastapod

  13. Agile Then @tastapod

  14. The Manifesto @tastapod

  15. Early and continuous delivery of software Welcome changing requirements Deliver frequently The Manifesto @tastapod

  16. Early and continuous delivery of software Welcome changing requirements Deliver frequently The Manifesto Business and developers working together Build projects around motivated individuals Value face-to-face communication @tastapod

  17. Early and continuous Working software is delivery of software measure of progress Welcome changing Self-organising teams requirements Technical excellence and Deliver frequently good design The Manifesto Business and developers working together Build projects around motivated individuals Value face-to-face communication @tastapod

  18. Early and continuous Working software is delivery of software measure of progress Welcome changing Self-organising teams requirements Technical excellence and Deliver frequently good design The Manifesto Business and developers Simplicity working together Build projects around Sustainable pace for motivated individuals sponsors, users, team Value face-to-face Regular reflection communication and tuning @tastapod

  19. The Brand @tastapod

  20. “ Brand (vt): give a product a distinctive identity” The Brand @tastapod

  21. Early and continuous Working software is delivery of software measure of progress Welcome changing Self-organising teams requirements Technical excellence and Deliver frequently good design The Agile Brand Business and Simplicity developers together Build projects around Sustainable pace for motivated individuals sponsors, users, team Value face-to-face Regular reflection communication and tuning @tastapod

  22. Early and continuous Working software is delivery of software measure of progress Welcome changing Self-organising teams requirements Technical excellence and Deliver frequently good design The Scrum Brand Business and Simplicity developers together Build projects around Sustainable pace for motivated individuals sponsors, users, team Value face-to-face Regular reflection communication and tuning @tastapod

  23. http://infoq.com/news/2015/09/agile-bank Agile Now @tastapod

  24. 2010s development @tastapod

  25. 2010s development Smaller projects @tastapod

  26. 2010s development Smaller projects Cross-functional “feature teams” @tastapod

  27. 2010s development Smaller projects Cross-functional “feature teams” Incremental delivery @tastapod

  28. 2010s development except… @tastapod

  29. 2010s development Upstream batching of money except… @tastapod

  30. 2010s development Upstream batching of money except… Downstream batching of Release @tastapod

  31. 2010s development @tastapod

  32. 2010s development Water- Scrum -fall @tastapod

  33. Agile Next @tastapod

  34. “Move the people to the work” @tastapod

  35. “Move the people to the work” …but remember they are people! @tastapod

  36. “Move the people to the work” …but remember they are people! Build your own Light Saber @tastapod

  37. “Move the people to the work” …but remember they are people! Build your own Light Saber Embrace radical diversity @tastapod

  38. “Move the people to the work” …but remember they are people! Build your own Light Saber Embrace radical diversity Figure out what a “team” looks like at scale @tastapod

  39. Measure Business Impact @tastapod

  40. Measure Business Impact We can build-ship-measure fast enough @tastapod

  41. Measure Business Impact We can build-ship-measure fast enough Less is more, like surgery @tastapod

  42. Measure Business Impact We can build-ship-measure fast enough Less is more, like surgery Developer “productivity” isn’t a thing @tastapod

  43. Measure Business Impact We can build-ship-measure fast enough Less is more, like surgery Developer “productivity” isn’t a thing Neither is velocity @tastapod

  44. Embrace Continuous Delivery @tastapod

  45. Embrace Continuous Delivery Two weeks is an illusion, two months doubly so @tastapod

  46. Embrace Continuous Delivery Two weeks is an illusion, two months doubly so Outcomes create options, requirements emerge @tastapod

  47. Embrace Continuous Delivery Two weeks is an illusion, two months doubly so Outcomes create options, requirements emerge Rolling Op-Ex over committed Cap-Ex @tastapod

  48. Embrace Continuous Delivery Two weeks is an illusion, two months doubly so Outcomes create options, requirements emerge Rolling Op-Ex over committed Cap-Ex Investment collaboration over detailed estimation @tastapod

  49. Would you use a 1990s computer? @tastapod

  50. Then why use a 1990s method? @tastapod

  51. Early and continuous Working software is delivery of software measure of progress Welcome changing Self-organising teams requirements Technical excellence and Deliver frequently good design The Manifesto Business and developers Simplicity working together Build projects around Sustainable pace for motivated individuals sponsors, users, team Value face-to-face Regular reflection communication and tuning @tastapod

  52. Early and continuous Working software Business impact is delivery of software value measure of progress Welcome changing emerging Self-organising teams requirements Technical excellence and Deliver frequently continually good design The Manifesto Business and developers and Simplicity everyone else working together Build projects products around Sustainable pace for sponsors, motivated individuals users, team all stakeholders Value face-to-face Regular Continual reflection communication and tuning @tastapod

  53. Early and continuous Working software Business impact is delivery of software value measure of progress Welcome changing emerging Self-organising teams requirements Technical excellence and Deliver frequently continually good design Not bad for a first draft! Business and developers and Simplicity everyone else working together Build projects products around Sustainable pace for sponsors, motivated individuals users, team all stakeholders Value face-to-face Regular Continual reflection communication and tuning @tastapod

  54. Thanks for listening Dan North @tastapod http://dannorth.net @tastapod

Recommend


More recommend