“Technical debt” refers to delayed technical work that is incurred when technical shortcuts are taken, usually in pursuit of calendar-driven software schedules. Just like financial debt, some technical debts can serve valuable business purposes. Other technical debts are simply counterproductive.
In this white paper, Steve McConnell explains the different types of technical debt, when organizations should and shouldn’t take them on, and best practices for managing, tracking, and paying down technical debt. You’ll gain insights into how to use technical debt strategically. You’ll also learn how to keep technical and business staff involved in the process of managing this debt.