O'Reilly logo
  • Matthew Hutchings thinks this is interesting:

The best way to pay off your technical debt is to assess what "loans" were taken at the end of each iteration. Ask your developers to identify specific hacks[3] they would like to unwind, and quantify how much time they think they need to do so.

They do not need to pay debt off immediately, but it is good to gauge the extent of the needed repair while the shortcuts are still fresh in the developers' minds.


Cover of 97 Things Every Project Manager Should Know


Would like to make this a standard part of iteration reviews.