How does technical debt relate to velocity?

• A. It can slow velocity due to hidden debt
• B. It speeds velocity
• C. It has no impact
• D. It always improves velocity

Answer: (A)

Technical debt affects velocity by reducing future throughput. Velocity represents how much value a team can deliver in a sprint, often measured in story points or features completed. When shortcuts, quick fixes, or incomplete work are taken, debt builds up in the codebase, architecture, tests, or documentation. Some of this debt sits below the surface—hidden from current planning—so the team’s current sprint might look fine, but the debt will demand attention in later sprints. That payback comes as refactoring, bug fixing, or rework, which consumes time that could have been spent delivering new functionality. Over time, this drains capacity and slows velocity.

Other ideas aren’t as accurate because debt almost always introduces extra work and risk, rather than speeding things up, having no impact, or always making performance better.