Ten types of technical debt

How do you describe your tech debt to business? Often saying, "We need to fix our technical debt," is not enough for the company to prioritize it. Here are frameworks that can help you with classification.

Ten types of technical debt

By Thoughtworks

  • Code quality
  • Testing
  • Coupling
  • Unused or low-value features
  • Out-of-date libraries or frameworks
  • Tooling
  • Reliability and performance engineering problems
  • Manual processes
  • Automated deployments
  • Knowledge sharing

By Google engineering

  • Migration is needed or in progress
  • Documentation on project and application programming interfaces (APIs)
  • Testing
  • Code quality
  • Dead and/or abandoned code
  • Code degradation
  • The team lacks necessary expertise
  • Dependencies
  • Migration was poorly executed or abandoned
  • Release process

Here, you can download the cheatsheet PDFs:

Detailed explanations and example Google Sheets frameworks are available for email subscribers. 👇