79: Managing Tech Debt

In all engineering problems like tech debt, focus on business case first. Telling executives (like CEO) or product management that tech debt has to be worked on will not work. You have to understand the business first and then find the impact of tech debt to the business. If people are complaining that the team speed is slow, find out why. Is it because of the tech debt or because of the lacking capabilities around continuous delivery. Once you found it, explain the problem’s impact to the business with clear impact evaluation and how you’ll make it better and how people will track that it gets better. Don’t start from the tech debt and explaining that you need time; it won’t work.

• Related Note(s):
  • 26: The Cost of Software Deployment and Continuous Delivery;
  • 39: Increasing Quality of Systems;
  • 43: The Role and Responsibility of Software Architect;
  • 49: Accidental Complexity;
  • 59: Functional Decomposition in Software Systems;
  • 78: Using Engineering Metrics;
• Source(s): CTO Craft Con Berlin 2024, Grygoriy Gonchar - CTO Eurowings Digital, Elevate Engineering Goals to your Company’s Genuine Priorities

This note is mentioned in: