Blog

Should you use metrics for technical debt management?

What is technical debt and how is It measured?

  • Technical debt accumulates interests over time and increases software entropy. To effectively measure technical debt, we need to express it as a ratio of the cost it takes to fix the software system to the cost it took to build the system. This quantity is called the Technical Debt Ratio [TDR].

Do you have too much technical debt?

  • Editor’s note: If missed release deadlines and bottlenecks in the development and maintenance sound too familiar, chances are you have excessive technical debt. To manage it, Boris, CTO at ScienceSoft, offers metrics from our technical debt management strategy in this article.

How do you measure technical debt in agile?

  • A basic metric we use to measure technical debt is the number and severity of bugs left unfixed per agile iteration, which helps plan bug fixing activities for the next iteration. We also compare it to the number and severity of bugs fixed per iteration to see how effectively our technical debt management strategy works.

image-Should you use metrics for technical debt management?
image-Should you use metrics for technical debt management?
Share this Post: