To improve velocity, what should teams do?

• A. Increase scope without planning
• B. Decrease collaboration
• C. Address technical debt and avoid large, unseen work
• D. Remove testing

Answer: (C)

Improving velocity comes from reducing things that slow the team down and create unpredictable work. Paying down technical debt and avoiding large, unseen work makes the work backlog smaller and more predictable, so the team can finish items in a sprint with less rework and surprises. When debt is addressed, code remains easier to maintain, tests catch issues earlier, and future work flows more smoothly, which tends to raise the amount of value the team can deliver each sprint.

Pushing more scope without planning leads to overcommitment and unfinished work, which hurts velocity. Decreasing collaboration breaks shared understanding, often increasing miscommunication and rework. Removing testing introduces defects that require fixes in later stages, again reducing velocity.