Agile anti-patterns at CodeMotion Madrid

3,027 views

Published on

Slide deck for the talk I did at CodeMotion Madrid 2013. Many organizations turn towards agile to escape failing traditional software development. Due to this increase in popularity, many newcomers enter the field. Without the necessary real-life experience but proudly waving certificates from two days of training. During this challenging talk Sander shows what happens to projects that are coached by ill-experienced coaches, and how to move around anti-patterns as Scrumdamentalism, Dogmatic Agile, Bob-the-Builder or Scrumman.

Published in: Technology

Agile anti-patterns at CodeMotion Madrid

  1. 1. Agile Anti Patterns Sander Hoogendoorn Principal Technology Officer & Global Agile Thoughtleader Capgemini 1 @aahoogendoorn
  2. 2. Sander Hoogendoorn Capgemini Principal technology officer Global agile thought leader Chief architect Accelerated Delivery Platform Other Author books on UML, agile Author +200 articles, columns Speaker +100 international conferences Microsoft Partner Advisory Council .NET Editorial boards & Advisory boards Capping IT Off Blog Web www.sanderhoogendoorn.com sander.hoogendoorn@capgemini.com @aahoogendoorn @aahoogendoorn
  3. 3. @aahoogendoorn
  4. 4. On being a developer ... 4 @aahoogendoorn
  5. 5. Why waterfall should have never existed • @aahoogendoorn
  6. 6. Waterfall? @aahoogendoorn
  7. 7. Waterfall? @aahoogendoorn
  8. 8. Agile! 8 @aahoogendoorn
  9. 9. right? @aahoogendoorn
  10. 10. @aahoogendoorn They should never have used waterfall. @aahoogendoorn Does the name of the project coincidently start with a C? @aahoogendoorn
  11. 11. @aahoogendoorn
  12. 12. @aahoogendoorn This project likely did ScrumBut, not Scrum. @aahoogendoorn
  13. 13. 13 @aahoogendoorn
  14. 14. 14 @aahoogendoorn
  15. 15. Jack states that we have over 300 resources who are trained 16 @aahoogendoorn
  16. 16. Lowering Our Fences @aahoogendoorn
  17. 17. The Agile Hippies @aahoogendoorn
  18. 18. The Agile Suits @aahoogendoorn
  19. 19. Kindergarden Agile the Hapiness Ready for Celebration before the Done column on your Kanban @aahoogendoorn
  20. 20. Open Door Wisdom @aahoogendoorn
  21. 21. Zenifying Agile @aahoogendoorn
  22. 22. Japanifying Agile @aahoogendoorn
  23. 23. Agile (Un)Conferences... @aahoogendoorn
  24. 24. At the wrong reenactment @aahoogendoorn
  25. 25. Scrumman 27 @aahoogendoorn
  26. 26. Dogmagile @aahoogendoorn
  27. 27. Crusader Agile @aahoogendoorn
  28. 28.  Scrumdamentalism @aahoogendoorn 
  29. 29. @aahoogendoorn
  30. 30. There is no so thing as one-size-fits-all agile @aahoogendoorn
  31. 31. Teams and roles 37 @aahoogendoorn
  32. 32. Customer, Coach, Developer @aahoogendoorn
  33. 33. Product owner, Scrum master, Team @aahoogendoorn
  34. 34. Customer, User, Domain Expert Project Manager, Coach, Developer, Tester Deliver working software Create project proposal Stabilize software Maintain software Write project plan 40 @aahoogendoorn
  35. 35. Multiple roles @aahoogendoorn
  36. 36. Teams? 42 @aahoogendoorn
  37. 37. What is the key to being successful as a team? 43 @aahoogendoorn
  38. 38. Collaboration 44 @aahoogendoorn
  39. 39. What happens to the old roles? @aahoogendoorn 46
  40. 40. An example team A typical Scrum team? Product owner /1 Business analyst /2 Information analyst /2 SAP CRM /1 SAP XI/ BPM /2 SAP ABAP /1 UI developer /1 .NET developer /1 Java developer /1 Tester /2 Scrum master /1 Agile coach /1 47 @aahoogendoorn
  41. 41. Rowing Contest Collaboration Enterprise Architects End Users Development Team Test Team Offshore Development Team 48 @aahoogendoorn
  42. 42. The backlog Where does it come from? @aahoogendoorn
  43. 43. And on the seventh day Ken created the backlog @aahoogendoorn
  44. 44. The automagical backlog @aahoogendoorn
  45. 45. The automagical backlog @aahoogendoorn
  46. 46. Preliminary iterations @aahoogendoorn
  47. 47. Preliminary iterations @aahoogendoorn
  48. 48. Documentation Frenzy @aahoogendoorn
  49. 49. User stories  @aahoogendoorn
  50. 50. @aahoogendoorn
  51. 51. Index cards might just not do the trick @aahoogendoorn
  52. 52. User stories are merely meant to get the conversation going? @aahoogendoorn
  53. 53. So what about documentation? @aahoogendoorn
  54. 54. no documentation (or modeling) @aahoogendoorn
  55. 55. Will you document to maintain?  @aahoogendoorn 
  56. 56. Eventually your software will go into maintenance (hopefully) @aahoogendoorn
  57. 57. On when to estimate 82 @aahoogendoorn
  58. 58. When? @aahoogendoorn
  59. 59. When? @aahoogendoorn
  60. 60. @aahoogendoorn
  61. 61. The overall model @aahoogendoorn
  62. 62. Guesstimation 88 @aahoogendoorn
  63. 63. Apples Team 1 89 @aahoogendoorn
  64. 64. Apples and apples Team 1 Team 2 90 @aahoogendoorn
  65. 65. Apples and oranges Team 1 Team 2 91 @aahoogendoorn
  66. 66. Distributed Apples Team 1 Team 2 Team 3 Off shore Team 92 @aahoogendoorn
  67. 67. Lightweight agile can be to enterprise projects What Monopoly is to solving the financial crisis @aahoogendoorn
  68. 68. Agile is a sliding scale 96 @aahoogendoorn
  69. 69. Assembling Agile @aahoogendoorn
  70. 70. Institutionalizing agile 107 @aahoogendoorn
  71. 71. Freedom and flexibility 108 @aahoogendoorn
  72. 72. Institutionalizing agile 109 @aahoogendoorn
  73. 73. In retrospective @aahoogendoorn
  74. 74. @aahoogendoorn
  75. 75. Agile is no religion S @aahoogendoorn
  76. 76. Agile is a sliding scale 114 @aahoogendoorn
  77. 77. Assembling Agile @aahoogendoorn
  78. 78. Value is found In all agile approaches (and yes, even in waterfall) @aahoogendoorn
  79. 79. Sander Hoogendoorn www.sanderhoogendoorn.com www.speedbird9.com @aahoogendoorn @aahoogendoorn 119

×