Chapter 4. Recognizing Technical Debt
In this chapter, we describe the causal chain of technical debt: causes and consequences. We expand on the concept of a technical debt item as a simple mechanism to identify and record the technical debt in a system. Then we explain how a software evolution strategy provides a starting point for analyzing the costs associated with technical debt.
Where Does It Hurt?
On any project that has run for a while, development teams might begin to observe signs that trouble is brewing, that something is not quite right or not working as well as it was before. The system becomes prone to certain types of defects, more bugs, or more crashes. Customers make more change requests, and it takes developers longer to satisfy ...
Get Managing Technical Debt: Reducing Friction in Software Development now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
