How can Scrum teams measure technical debt?

Short answer: Follow On: Ways to measure and manage technical debt: Code quality tools (SonarQube, CodeClimate) Automated test coverage Bug rates and frequency of rework Velocity trends — slowed delivery may indicate rising debt Team feedback in Retrospectives Make it visible: Track known debt in the Product Backlog.

Explain a bit more

Reserve capacity every Sprint to pay it down. Example: After frequent issues with legacy code, a team estimates and logs 5 technical debt stories, prioritizing the worst ones during each Sprint.

Real-world example (ShopNest)

Agile for ShopNest means ship a thin checkout slice every sprint, get feedback, then improve—not a 6-month big-bang release.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.