What fields would be useful to include in the Technical debt report



  • I've been asked to create a report about the technical debt of an application, but I haven't receive further guidelines about its elaboration. I'll be assisted by Sonar code analysis tool.

    My main doubt is: What fields would be useful to include in the report? I mean, what metrics, parameters, findings, suggestions, etc. would be the most important in such a report?



  • When someone asks me to do something and I have questions about what they want, I go back and ask them. That's the most direct way to get an answer.

    As a manager, I would want these fields:

    • description, i.e. what's the issue and why it's a problem
    • amount of risk if not fixed
    • pervasiveness
    • level of effort to fix, including testing effort
    • associated bug numbers, if any

    Note also that technical debt, as I've heard the term used, is a broader area that the set of problems a code analyzer will identify for you.



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2