Recommended
Recommended
More Related Content
Similar to Failed and successful stories with Technical Debt - DevOps D-Day 2018
Similar to Failed and successful stories with Technical Debt - DevOps D-Day 2018 (20)
More from Antonio COBO CUENCA
More from Antonio COBO CUENCA (20)
Recently uploaded
Recently uploaded (20)
Failed and successful stories with Technical Debt - DevOps D-Day 2018
- 1. Failed and successful stories with Technical Debt Antonio Cobo @Mind_of_AC
- 2. “Technical debt is a concept in software development that reflects the implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer.” - Wikipedia Antonio Cobo @Mind_of_AC
- 3. “Technical debt is a concept in software development that reflects the implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer.” - Wikipedia Antonio Cobo @Mind_of_AC
- 4. but also… Antonio Cobo @Mind_of_AC
- 5. A bad code review process (or a non existing one) will generate unconsciously Technical Debt but also… Antonio Cobo @Mind_of_AC
- 6. Who am I? Java Developer Head of Backend Development Technical Project Manager Project Manager Agile Project Manager Scrum Master Agile Delivery Consultant Delivery Manager IT Manager Software developer2000 2018 Senior Agile Delivery Consultant Antonio Cobo @Mind_of_AC
- 7. Antonio Cobo @Mind_of_AC Apology and warning! Antonio Cobo @Mind_of_AC
- 8. Antonio Cobo @Mind_of_AC Apology and warning! Antonio Cobo @Mind_of_AC
- 9. Antonio Cobo @Mind_of_AC Apology and warning! Antonio Cobo @Mind_of_AC
- 10. Antonio Cobo @Mind_of_AC Apology and warning! https://images.fineartamerica.com/images/artworkimages/medium/1/darth-vader-watercolor-olga-shvartsur-transparent.png Antonio Cobo @Mind_of_AC
- 13. What Business think Antonio Cobo @Mind_of_AC
- 14. What Business think Antonio Cobo @Mind_of_AC
- 15. What Devs think Antonio Cobo @Mind_of_AC
- 16. What Devs think Antonio Cobo @Mind_of_AC
- 17. Explain technical debt using business words Antonio Cobo @Mind_of_AC
- 18. Explain technical debt using business words Impact on our customers Antonio Cobo @Mind_of_AC
- 19. Explain technical debt using business words Impact on our customers Impact on our brand Antonio Cobo @Mind_of_AC
- 20. Explain technical debt using business words Impact on our customers Impact on our brand Antonio Cobo @Mind_of_AC
- 21. Chapter 1: The bad teacher Antonio Cobo @Mind_of_AC
- 22. Situation: • Junior Developer • Big company • “Senior” Developer with no real experience • Fixed Price contract • Save as much money as you can mentality Antonio Cobo @Mind_of_AC
- 26. Bad team work Antonio Cobo @Mind_of_AC
- 27. Bad team work Not teaching good practices Antonio Cobo @Mind_of_AC
- 28. Bad team work Not teaching good practices Not making the junior developer to think Antonio Cobo @Mind_of_AC
- 29. Bad team work Not teaching good practices Not making the junior developer to think If the original class used as a model is poorly written Antonio Cobo @Mind_of_AC
- 30. Bad team work Not teaching good practices Not making the junior developer to think If the original class used as a model is poorly written Antonio Cobo @Mind_of_AC
- 31. Bad team work Not teaching good practices Not making the junior developer to think If the original class used as a model is poorly written Antonio Cobo @Mind_of_AC
- 32. Chapter 2: The sellotape fix Antonio Cobo @Mind_of_AC
- 33. Situation: • Extremely optimistic deadline • Development manager asked to be “hands on” • We MUST deliver something tomorrow • After helping the team, it’s late and DM is alone Antonio Cobo @Mind_of_AC
- 39. Chapter 3: The Outlaw Antonio Cobo @Mind_of_AC
- 40. Situation: • Developer finding Tech Debt • Willing to correct it • Refactoring a small part… • Without telling anyone Antonio Cobo @Mind_of_AC
- 43. Situation: • Developer finding Tech Debt • Willing to correct it • Refactoring a small part… • Without telling anyone Antonio Cobo @Mind_of_AC
- 44. Situation: • Developer finding Tech Debt • Willing to correct it • Refactoring a small part… • becoming bigger and bigger and bigger… • Without telling anyone Antonio Cobo @Mind_of_AC
- 49. Situation: • Developer finding Tech Debt • Willing to correct it • Discuss with the Team • Refactor Antonio Cobo @Mind_of_AC
- 53. Chapter 4: The good team Antonio Cobo @Mind_of_AC
- 54. Situation: • Seven senior developers + PO • Long term product development • Some intermediate tight deadlines • Second retrospective and Tech Debt is here! Antonio Cobo @Mind_of_AC
- 55. Added technical debt as new issue type in the backlog Antonio Cobo @Mind_of_AC
- 56. Technical debt tickets were prioritised alongside the stories and tasks Antonio Cobo @Mind_of_AC
- 58. Good team work Antonio Cobo @Mind_of_AC
- 59. Good team work Communication between devs and PO Antonio Cobo @Mind_of_AC
- 60. Good team work Communication between devs and PO Manage to reduce the technical debt fast after its creation Antonio Cobo @Mind_of_AC
- 61. Good team work Communication between devs and PO Manage to reduce the technical debt fast after its creation Antonio Cobo @Mind_of_AC
- 62. Good team work Communication between devs and PO Manage to reduce the technical debt fast after its creation Antonio Cobo @Mind_of_AC
- 63. Chapter 5: It’s a trap! Antonio Cobo @Mind_of_AC
- 64. Evil Team Member Antonio Cobo @Mind_of_AC
- 65. Evil Team Member Antonio Cobo @Mind_of_AC
- 66. Evil Team Member Antonio Cobo @Mind_of_AC
- 67. Evil Product Owner Antonio Cobo @Mind_of_AC
- 68. Evil Product Owner Antonio Cobo @Mind_of_AC
- 69. Evil Product Owner Antonio Cobo @Mind_of_AC
- 72. Chapter 6: Avoiding the trap Antonio Cobo @Mind_of_AC
- 73. Scenario: Evil Team Member Antonio Cobo @Mind_of_AC
- 75. We agreed to dedicate a % of time to repay our debt on each sprint Antonio Cobo @Mind_of_AC
- 76. We reviewed that % on every retrospective Antonio Cobo @Mind_of_AC
- 77. Show improvements in the demo Antonio Cobo @Mind_of_AC
- 78. Show improvements in the demo Antonio Cobo @Mind_of_AC
- 79. Chapter 7: The storyteller Antonio Cobo @Mind_of_AC
- 80. Scenario: Evil Product Owner Antonio Cobo @Mind_of_AC
- 81. Make it a story! Antonio Cobo @Mind_of_AC
- 83. “Improve how we handle DB concurrent connections” Antonio Cobo @Mind_of_AC
- 84. “Improve how we handle DB concurrent connections” Antonio Cobo @Mind_of_AC
- 85. “Improve how we handle DB concurrent connections” As a Head of Product I want to enable special sales events in our website (ie. Black Friday) so that we can increase our revenue Antonio Cobo @Mind_of_AC
- 86. “Improve how we handle DB concurrent connections” As a Head of Product I want to enable special sales events in our website (ie. Black Friday) so that we can increase our revenue Antonio Cobo @Mind_of_AC
- 89. Scout Camp Rule Leave the code you touch cleaner than the way you found it! Antonio Cobo @Mind_of_AC
- 90. CODE REVIEW Never approve added technical debt! Challenge and suggest improvements while reviewing Antonio Cobo @Mind_of_AC
- 91. https://www.lynda.com/Business-Skills-tutorials/Communication-Tips/170778-2.html Communication, communication, communication! Antonio Cobo @Mind_of_AC
- 93. …and they lived happily ever after. THE END Antonio Cobo @Mind_of_AC