Davide Falessi – Practical Considerations, Challenges and Requirements of Tool-support for Managing Technical Debt

Managing TDD consists of three activities according to Davide Falessi:

  1. Identify the TD items
  2. Estimating the economic consequences
  3. Analyzing differences between consequences

Davide states that the real challenge is #2, as we need to convince customers that time spent on resolving TD makes sense from a financial perspective.

Observations here are that not all TD has to be removed and that customers can actually be involved in and educated about TD concepts. Challenges are to make good estimations. Single values are inadequate: rather say at least 2 months or within 2 and 4 months than just 2 months.

Now, Davide presents his 10 requirements for tools that manage technical debt:

  1. Ability to manage principle, interest and time-to-market
  2. Translate decisions to economic consequences (for instance: is fixing on this bug now and shipping a week later cheaper than shipping with the bug?)
  3. Manage uncertainty
  4. Manage evolution
  5. Balance rigor and ease-of-use.
  6. Completeness and integration
  7. <<missing, I was too slow>>
  8. What if analysis of possible interpretations
  9. Sensitivity analysis
  10. Scenario analysis

1 Comment

  1. Stephan Eggermont

    Estimating the economic consequences is only possible if the code is still in a reasonable state. That limits the applicability of these observations severely, and is not so helpful for those most in need…

Comments are closed.