Technical Debt in Agile Projects
It seems that on almost every project I’ve worked, we end up with a number of TODO’s left over. These things can be as simple as basic code cleanup, or full-on refactoring that would help the application perform better. We often take short-cuts, usually for good reasons, that we wish we hadn’t. Over time these things pile up and we create quite a bit of technical debt.
A friend passed this article, Technical Debt a Perspective for Managers, by Mark Levison on to me that pretty acurately describes how we accumulate such technical debt, particularly in agile processes, and some tips on how to manage it.