What are Technical Debt?
Technical debt is usually the result of a decision made by development teams to take the easy path or skip development best practices, in order to meet a delivery schedule. This leaves behind issues in the codebase that need to be resolved at some point. In other cases, software needs to be updated or maintained, and these changes are delayed to allow for the delivery of new features. This leftover work is a debt that must be paid off at some point in the future.
All software development projects, including Agile projects, accumulate technical debt, and a major challenge of development teams and R&D leadership is to keep technical debt at a level that does not affect the team’s performance on the one hand, and the organization’s long-term goals on the other hand.