Top 3 Velocity Interview Questions
Browse 3 real-world technical and behavioral interview questions about Velocity. Review scenarios, edge cases, and architectural best practices.
The team has missed its Sprint Goal four sprints in a row. What do you do as Scrum Master?
Treat four misses as data about the system rather than a verdict on the team: find out whether the goal is set by the team or handed to it, whether unplanned work arrives mid-sprint, and whether done is being deferred, then fix the cause you find instead of shrinking the commitment.
Which delivery metrics would you actually track for a team, and why does velocity stop working the moment you set a target for it?
Track throughput, cycle-time distribution and flow efficiency, because they describe the system rather than the estimate. Velocity is denominated in a unit the team defines, so making it a target lets the number rise without any change in delivered output, and it stops measuring anything.
Why do we estimate in story points at all, and what would you do if the team's estimates were consistently wrong?
Points are relative sizes that trade false precision for a fast conversation whose real output is surfaced disagreement. Estimates that are always wrong are a system symptom, so diagnose unclear criteria, oversized stories, invisible work and interruptions, then forecast with throughput and cycle time.