Being Agile: Eleven Breakthrough Techniques to Keep You from “Waterfalling Backward”
by Leslie Ekas, Scott Will
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, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access