We need to talk about tech debt
- 1. We need to talk about tech debt Matt Whetton 1
- 2. We need to talk about tech debt Matt Whetton 2
- 3. Matt Whetton Chief Technology Officer @ Oakbrook Twitter: @codenutz LinkedIn: https://linkedin.com/in/matthewwhetton/ Medium: https://medium.com/@mattwhetton A LITTLE ABOUT ME 3
- 5. THE TECH DEBTOR’S JOURNEY CALL TO ADVENTURE THRESHOLD CONCEPTS CHALLENGES & TEMPTATIONS TRANSFORMATION REAL WORLD APPLICATION RETURN AND MAKE A CHANGE 5
- 6. THE TECH DEBTOR’S JOURNEY CALL TO ADVENTURE THRESHOLD CONCEPTS 6
- 7. AGILE DELIVERY DEVOPS OR NOOPS LONG-LIVED TEAMS PROBLEMS OVER SOLUTIONS 7
- 8. COINED BY WARD CUNNINGHAM AGILE MANIFESTO CREDITED WITH INVENTING THE WIKI 8
- 9. 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 ref: www.techopedia.com/definition/27913/technical-debt 9
- 11. IT COULD BE A TICKING TIME BOMB 11
- 12. THE TECH DEBTOR’S JOURNEY CALL TO ADVENTURE THRESHOLD CONCEPTS CHALLENGES & TEMPTATIONS 12
- 13. 13
- 14. IRON LABS 14
- 15. IRON LABS SUPPORTABILITY PRODUCTIVITY PERFORMANCE PRIVACY SECURITY SECURITY RESILIENCY QUALITY 15
- 16. THINGS THE DEVS KEEP GRUMBLING ABOUT 16
- 17. THE TECHNICAL DEBT QUADRANT Ref: Martin Fowler - https://martinfowler.com/bliki/TechnicalDebtQuadrant.html 17
- 18. ONTOLOGY OF TECHNICAL DEBT Ref: Software Engineering institute - https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=312135a 18
- 19. 2 WAYS TECH DEBT MANAGEMENT PLAYS-OUT SPRINT ALLOWANCE LOUDEST VOICE IN THE ROOM 19
- 20. ARE WE MAKING THE RIGHT DECISIONS? 20
- 21. NOT ENOUGH DEBT PAID THE 4 DYSFUNCTIONS OF TECH DEBT MANAGEMENT TOO MUCH DEBT PAID DEBT PAYMENT AS A REWARD WRONG DEBT PAID 21
- 22. THE TECH DEBTOR’S JOURNEY CALL TO ADVENTURE THRESHOLD CONCEPTS CHALLENGES & TEMPTATIONS 22
- 23. 23
- 24. 24
- 25. 2 THINGS WE CARE ABOUT VALUE CREATION RISK MANAGEMENT Ref: The art of business value by Mark Schultz 25
- 26. IRON LABS SUPPORTABILITY PRODUCTIVITY PERFORMANCE PRIVACY SECURITY SECURITY RESILIENCY QUALITY 26
- 27. THE TECH DEBTOR’S JOURNEY CALL TO ADVENTURE THRESHOLD CONCEPTS CHALLENGES & TEMPTATIONS TRANSFORMATION 27
- 28. GETTING STARTED WITH RISK ESTABLISH TOP LEVEL RISK STATEMENTS 1 ADOPT GRADING SYSTEM 2 IDENTIFY CURRENT RISKS & GRADES 3 USE IT! 4 ALIGN WITH EXISTING RISK FRAMEWORK IF ONE EXISTS 5 28
- 29. ESTABLISH TOP LEVEL RISK STATEMENTS 1 SECURITY IMPROPER SECURITY CONTROLS RESULTS IN LOSS OF SENSITIVE DATA OR AVAILABILITY OF SYSTEMS PRIVACY IMPROPER DATA MANAGEMENT PRACTICES RESULTS IN BREACH OF SENSITIVE DATA SUPPORTABILITY LACK OF OR IMPROPER OBSERVABILITY CONTROLS IMPACTS SYSTEM AVAILABILITY 28
- 30. ADOPT GRADING SYSTEM 2 LIKELIHOOD • SCORE 1 TO 4 • 1: VERY UNLIKELY • 4: CERTAIN LIKELIHOOD OF OCCURRING IN NEXT 6 MONTHS 2 IMPACT • SCORE 1 TO 4 • 1: LOW IMPACT (MINOR COST) • 4: HIGH IMPACT (BUSINESS ENDING) X 3 = SCORE 6 29
- 31. ADOPT GRADING SYSTEM 2 LIKELIHOOD 2 IMPACT X 3 = SCORE 6 30 INHERENT RISK LIKELIHOOD 1 IMPACT X 2 = SCORE 2 RESIDUAL RISK
- 32. IDENTIFY CURRENT RISKS & GRADES 3 Identify risk causes Grade your risks LIKELIHOOD X IMPACT = SCORE 2 X 2 = 4 31
- 33. PRIORITISING USE IT REPORTING RISK MANAGEMENT BECOMES PART OF THE CONVERSATION • SHOULD WE BE REDUCING RISK • SHOULD WE BE MAINTAINING RISK RISK MANAGEMENT BECOMES PART OF INSPECTION • REPORT ON RISK DISPOSITION AT INSPECTION POINTS • REVIEW MOVEMENT IN RISK ALWAYS REFLECT NEW RISKS OR MITIGATIONS IN THE SCORING 4 32
- 34. USE IT - REPORTING 4 RISK APPETITE LAST MONTH CURRENT MONTH MOVE COMMENTARY SECURITY 1.5 3.5 3.0 Enabled mutual TLS on diagnostic comms PRIVACY 1.5 1.5 1.5 - RESILIENCY 2.0 1.0 1.5 New thruster missing failover SUPPORTABILITY 2.5 2.0 2.0 - PRODUCTIVITY 2.5 2.5 3.0 Copy pasted thrust controller (duplicate logic) QUALITY 2.5 1.5 1.5 - 33
- 35. ALIGN WITH EXISTING FRAMEWORK IF ONE EXISTS 4 34
- 36. the tech debtor’s journey Call to adventure Threshold concepts Challenges & temptations transformation Real world application Return and make a change 35
- 37. QUESTIONS?
- 38. GOODBYE