Technical debt is a KPI (Key Performance Indicator) that represents the implied cost in hours of development effort needed to solve the issues/violations detected in the platform due to non-adherence to best practices and changes to the out-of-the-box functionality.
The evolution of this indicator over time and between different instances provides reliable feedback and outlines trends for your instance - whether it is on the improving or declining side.
It is a general rule for the quality of your instance to be understood as a high-level information and not an exact time calculation, as it only includes coding work, and does not account for the following factors which are product and project specific:
- Technical and architectural analysis
- Code reviews and testing
- Release management
Global technical debt
Technical debt including all non-coding activities, such as analysis, project management, testing and release management.