“Technical Debt” refers to delayed technical work that is incurred when technical shortcuts are taken, usually in pursuit of calendar-driven software schedules. Technical debt is inherently neither good nor bad. Just like financial debt, some technical debts can serve valuable business purposes. Other technical debts are simply counterproductive. However, just as with the financial kind, it’s important to know what you’re getting into.
In this webinar, noted author and software engineer Steve McConnell explains in detail the different types of technical debt, when organizations should and shouldn’t take them on, and best practices for managing, tracking and paying down debt. You’ll gain insights into how to use technical debt strategically and how to keep technical and business staff involved in the process.