What statement best defines Technical Debt?

• A. A fixed, avoidable backlog item
• B. The cost of rework that arises when choosing a quick solution now instead of a better one
• C. It is only about coding style
• D. It has no impact on velocity

Answer: (B)

Technical debt is the future cost of rework that results from taking a quick, suboptimal solution today instead of investing in a better long-term approach. When a fast fix or insufficient testing is chosen to meet a deadline, the team will typically have to revisit and revise that area later, leading to extra effort that could have been spent delivering new value. That rework cost is what the statement captures, making it the best description.

It’s not limited to coding style; technical debt can arise from architecture, design choices, testing gaps, or missing documentation. It does impact velocity because the time spent paying down or repairing debt reduces the capacity to deliver new features. Debt can be tracked and scheduled as work in the backlog, but the core idea is the ongoing cost of rework created by prioritizing speed over a higher-quality solution.