Project Debt
To ensure that the original meaning of the term technical debt is not lost, we will use the term project debt throughout this chapter as an umbrella term to cover typical wastes that occur in software development (including technical debt). Project debt describes a broad range of compromises that teams make to ship a product sooner. Examples include defect backlogs that carry over from release to release; performing manual testing instead of pursuing automation; automation that is in place but is broken; having hard-coded strings (especially if globalization is required); code duplication and code complexity; faulty builds; an out-of-date version of a compiler; and incomplete cross-functional criteria (for example, accessibility, ...
Get Being Agile: Eleven Breakthrough Techniques to Keep You from “Waterfalling Backward” 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.
