How do you handle wildly fluctuating team velocity?
Tests if you know velocity is for team planning, not a manager's KPI. A good answer reframes the goal to predictability, investigates root causes with the team (e.g., story sizing, unplanned work), and proposes experiments.
What's really being asked
This question tests your understanding that velocity is a tool for team forecasting, not a performance metric for management. It probes your ability to diagnose systemic issues, coach a team towards improvement without being prescriptive, and manage stakeholder (management) expectations. The interviewer wants to see if you can move beyond reporting a number to facilitating a root cause analysis.
The full answer
A strong answer has four parts. First, reframe the conversation with management. Explain that the goal is predictable delivery, not necessarily higher velocity, as predictability enables reliable business planning. Second, facilitate a team-led investigation, likely in a retrospective, to explore the 'why' behind the fluctuations. Third, present a list of potential root causes to investigate, such as inconsistent story point estimation, unaccounted-for unplanned work, hidden dependencies, or volatile team capacity due to holidays or illness. Fourth, propose specific, small experiments to address these causes, like using a rolling 3-sprint average for planning, formalizing spikes for research, or reserving a fixed capacity (e.g., 15%) for interrupts.
The mistakes people make
A major red flag is treating velocity as a productivity KPI. Answers like "I'd push the team to increase their velocity" or "We need to get our numbers up" are immediate fails. Another common mistake is comparing velocity across different teams, as story points are relative to a specific team's context. Blaming individuals or suggesting overtime to 'catch up' also demonstrates a misunderstanding of agile principles. Finally, simply reporting the numbers without a plan to investigate the underlying system is a weak, junior-level response.
What usually comes next
Expect questions like: "Management insists on seeing velocity increase. How do you handle that?" which tests your ability to push back constructively and educate stakeholders. Another is: "What if the team doesn't know why it's fluctuating?" which tests your deeper diagnostic skills, perhaps suggesting the team track interrupts or analyze cycle time for different story types. They might also ask how you'd adjust for a new hire joining the team.
A concrete example
Our team's velocity swung from 30 to 12 to 35. In the retro, we found the 12-point sprint was derailed by two 'simple' 5-point stories that uncovered major tech debt. The 35-point sprint was all small, well-understood tasks. The fluctuation wasn't about effort, but about uncertainty. Our experiment was to introduce a 'Spike' of 1-2 points for any story with significant unknowns. We also started using a rolling 3-sprint average (26 points) for our sprint commitment. This immediately made our planning more realistic and our delivery cadence stabilized around 25-30 points per sprint, making our forecasts trustworthy.
Interview question
When a team's velocity fluctuates significantly, what is the primary goal of the investigation that follows?
- a.To implement a rolling average for planning, making commitments more consistent.
- b.To normalize story point values by comparing them with other teams in the organization.
- c.To identify ways to increase the team's average velocity over time.
- d.To improve the predictability of delivery for more reliable business planning.Correct
Why? this is the answer
The primary purpose of velocity is forecasting. The goal is to make delivery predictable for reliable business planning, not simply to increase the number. Using a rolling average is a useful tactic, but it's a tool to aid planning, not the core goal of the investigation itself.
Just read this? Test yourself on what you have been reading.
Read the original → agilealliance.org
- #agile
- #scrum
- #metrics
- #coaching
- #leadership
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles