Strategies for Reducing Technical Debt

Speed of development is a benefit of Agile software projects but can have an undesirable side effect. Software that developers deliver in an iteration (e.g., Scrum sprint) might work but not have the same level of quality, reliability, or consistency as more “polished” code. The team might also take credit for finishing a user story that is later found to be incomplete. As time passes, bugs may surface and the code base may become misaligned with upgraded libraries, patched operating systems, and other newer system components. The need to refactor, fix, or upgrade delivered code is called technical debt, a phrase that originally described the cumulative consequences of taking development shortcuts.  Read more (Dynanet Blog Technical Debt) to learn about technical debt and avoiding the pitfalls of owing too much technical debt or paying off that debt early at the expense of the project.

Scroll to Top