📈 Velocity & Capacity Vocabulary
Master the language of story points, sprint forecasting, and communicating capacity to stakeholders. Intermediate
0 / 25 completed
1 / 25
A new Scrum team member who came from a waterfall background says:
"Why don't we just estimate in hours? I can say this feature will take me 3 days. Why do we need 'story points'? It seems like extra complexity."
Which explanation most accurately describes why Agile practitioners use story points instead of hours?
The core argument for story points over hours rests on three insights:
| Problem with hours | How story points address it |
|---|---|
| False precision — "3 days" implies certainty that doesn't exist | Relative sizing (this story is twice as complex as that one) is more honest about uncertainty |
| Individual accountability — "you said 3 days, it took 5" | Team estimates; velocity is a team metric — no individual is blamed for variance |
| Skill-level variance — 3 days for a senior ≠ 3 days for a junior | Complexity is the same regardless of who does the work; the team velocity accounts for the mix |
Note: the Scrum Guide (2020) does not mandate story points at all — it only requires that the Development Team selects an estimation approach. Many modern Agile teams use "#NoEstimates" flow-based approaches instead. Option D is incorrect: story points deliberately do not map to calendar time.
2 / 25
The Scrum Master is presenting velocity data to business stakeholders in a quarterly planning meeting. The team's 6-sprint rolling average velocity is 42 story points.
Which statement should the Scrum Master NOT make when presenting this velocity data?
Option D contains a critical misconception: story points are not units of business value. Equating them destroys trust with stakeholders once they realise the statement is misleading:
| Incorrect framing | Why it's wrong | Better phrasing |
|---|---|---|
| "42 points = 42 value units" | Story points measure relative effort and complexity, not business outcomes or value delivered | "42 points tells us our capacity for work; value delivered depends on what stories we choose" |
Other things Scrum Masters should not say when presenting velocity:
- Comparing velocity across different teams (team-relative measure)
- "We must hit 42 points every sprint" (velocity is a guide, not a floor)
- "Higher velocity = better team" (inflating estimates raises velocity artificially)
The safest framing: "Velocity is our historical planning input. It helps us forecast, not judge team performance."
3 / 25
For the upcoming sprint (10 working days), Developer A is on holiday for 3 days and Developer B for 2 days. The remaining 3 developers are fully available. All 5 developers average 6 focus hours per day. The team's normal velocity is 42 story points.
How should the Scrum Master communicate the adjusted capacity and sprint forecast?
Communicating capacity as a percentage of normal is the clearest way to convey the impact to both the team and stakeholders:
| Calculation step | Values |
|---|---|
| Normal capacity (5 devs × 10 days) | 50 developer-days |
| Lost capacity (3 + 2 holiday days) | 5 developer-days |
| Available capacity | 45 developer-days = 90% of normal |
| Adjusted forecast | 42 × 0.90 ≈ 38 points (some teams round down for safety margin) |
Option B (raw focus hours) is too technical for stakeholder communication and doesn't map to story points. Option C is incorrect — velocity reflects past completions and does not automatically adjust for future absences. Option D is a non-starter in Agile; partial-capacity sprints are normal and expected.
4 / 25
A product manager sends the Scrum Master a message before sprint planning:
"The next sprint is critical for our Q3 roadmap. I need the team to commit to 60 story points instead of your usual 42. This is not negotiable."
Which response from the Scrum Master is most appropriate?
Artificially inflating sprint commitments to satisfy external pressure is one of the most damaging anti-patterns in Scrum:
| What happens when teams over-commit | Impact |
|---|---|
| Stories rushed to hit the number | Acceptance criteria not fully met; bugs increase next sprint |
| Tests skipped or cut short | Technical debt accumulates; future velocity drops |
| Velocity data becomes inflated | Future forecasts are unreliable; planning trust erodes |
| Team morale drops | Sustainable pace principle is violated; burnout risk rises |
The Scrum Master's role includes protecting the team's process from external pressure. The correct response is to explain — with data — why the request undermines the very reliability the product manager depends on, and to offer a transparent conversation about priorities instead of a velocity number change.
5 / 25
During sprint planning, the team debates which wording to use when communicating the sprint plan to stakeholders. One developer says: "We always say we're 'committing' to these points." The Scrum Master replies: "Modern Scrum actually prefers different language."
Which wording does modern Scrum encourage, and why?
The shift from "commitment" to "forecast" in the 2020 Scrum Guide update was deliberate:
| Term | Implication | Problem |
|---|---|---|
| Commit | A binding promise — failure to deliver = breach | Encourages scope protection over collaboration; punishes honest re-planning |
| Forecast | A data-based prediction — subject to revision as learning occurs | None — aligns with empirical process control (inspect and adapt) |
Forecast language aligns with Scrum's empirical foundation: the team plans based on what they know now and adapts as they learn more. Saying "we forecast 38 points" opens a healthy conversation about risk and uncertainty, whereas "we commit to 38 points" creates contractual pressure that incentivises cutting corners to avoid the appearance of failure.
6 / 25
During a sprint review, the Development Team demonstrates a newly completed feature. The Product Owner asks the team, 'What was your velocity for this sprint?' Team Member C responds: 'We delivered 25 story points this sprint.' The Scrum Master notices that the team's average velocity over the last three sprints has been significantly lower—around 18 story points per sprint. Which of the following best explains why this variance in velocity is important to monitor and discuss with the team?
Note: This scenario highlights the importance of understanding trends, not just individual sprint outputs.
Note: This scenario highlights the importance of understanding trends, not just individual sprint outputs.
Velocity isn't simply about the points delivered in a single sprint; it's a *trend* representing the team's capacity over time. Monitoring variance helps identify issues like changing priorities, new complexities introduced, or perhaps inconsistent estimation practices. Addressing these trends allows for proactive adjustments to future sprints and improves overall predictability. Focusing solely on a single sprint's output provides a misleading picture of true team performance.
7 / 25
During a sprint retrospective, the team discusses their velocity. Developer X says: 'Our velocity was really high last sprint – we delivered 85 story points! We should aim for that consistently.' The Scrum Master gently pushes back and asks the team to consider what factors might have contributed to this unusually high output. Which of the following is the MOST important thing the Scrum Master should emphasize to the team?
Velocity isn't just about the raw number of story points delivered; it represents the *sustainable* rate at which a team can consistently complete work. A high velocity in one sprint could be due to external factors (e.g., a simpler backlog) and wouldn't necessarily reflect the team's true capacity. The Scrum Master needs to guide the team towards understanding that velocity is an average over time, not a target for individual sprints, and that focusing on consistent delivery is key.
8 / 25
A developer is explaining the concept of 'velocity' to a new team member. He says: 'Velocity represents how quickly we're delivering value – essentially, it's like our average speed in completing sprints.' Which of the following best captures the *true* meaning of velocity in Agile development?
Velocity isn't simply about individual speed or bug counts. It's a crucial metric that measures *team* performance over time – specifically, the average amount of work (typically measured in story points) completed within a sprint. This allows teams to forecast future sprints more accurately and understand trends in their delivery capacity. Misunderstanding velocity as solely individual productivity can lead to misaligned expectations and ineffective prioritization.
9 / 25
During a sprint planning meeting, the Development Team is discussing their capacity for the upcoming sprint. The team's Lead Developer states: 'Our velocity has been consistently around 50 story points lately, so we should aim to deliver roughly that much this sprint.' A newer team member raises a concern: 'But what if we have unexpected blockers or dependencies? Shouldn't we account for potential fluctuations in our capacity?' Which of the following best reflects the *purpose* of tracking velocity as a team?
Velocity is primarily used as a *predictive* metric – it represents the team's average capacity over time. Tracking velocity allows the team to estimate how much work they can realistically complete in a sprint, factoring in past performance and potential fluctuations. It's not about rigid targets or pressure, but rather informed planning based on historical data. Option A is incorrect because velocity isn't a constraint; options C and D are misinterpretations of its role.
10 / 25
During a daily standup, Developer Y says: "Our velocity is currently 55 story points. We need to maintain this pace to hit our sprint goal!" The team's Product Owner interjects, "But what if we're overestimating? Shouldn't we be more flexible and adjust based on actual progress?"
This scenario highlights a crucial aspect of Agile: velocity isn't a fixed target but rather an *average* that guides forecasting. The team needs to maintain velocity as a goal, but it must be combined with flexibility and the ability to adjust based on actual progress – ignoring potential risks or changes is a common mistake. The correct option reflects this balanced approach, acknowledging both the value of a consistent velocity and the need for adaptive planning.
11 / 25
During a sprint review, the Development Team demonstrates a newly completed feature. The Product Owner asks the team, 'What was your velocity for this sprint?' Team Member C responds: 'We delivered 25 story points this sprint.' The Scrum Master notices that the team's average velocity over the last three sprints has been significantly lower—around 18 story points per sprint. Which of the following best explains why this variance in velocity is important to monitor and discuss with the team?
Note: This scenario highlights the importance of understanding trends, not just individual sprint outputs.
Note: This scenario highlights the importance of understanding trends, not just individual sprint outputs.
Velocity isn't simply about the points delivered in a single sprint; it's a *trend* representing the team's capacity over time. Monitoring variance helps identify issues like changing priorities, new complexities introduced, or perhaps inconsistent estimation practices. Addressing these trends allows for proactive adjustments to future sprints and improves overall predictability. Focusing solely on a single sprint's output provides a misleading picture of true team performance.
12 / 25
During a sprint retrospective, the team discusses their velocity. Developer X says: 'Our velocity was really high last sprint – we delivered 85 story points! We should aim for that consistently.' The Scrum Master gently pushes back and asks the team to consider what factors might have contributed to this unusually high output. Which of the following is the MOST important thing the Scrum Master should emphasize to the team?
Velocity isn't just about the raw number of story points delivered; it represents the *sustainable* rate at which a team can consistently complete work. A high velocity in one sprint could be due to external factors (e.g., a simpler backlog) and wouldn't necessarily reflect the team's true capacity. The Scrum Master needs to guide the team towards understanding that velocity is an average over time, not a target for individual sprints, and that focusing on consistent delivery is key.
13 / 25
A developer is explaining the concept of 'velocity' to a new team member. He says: 'Velocity represents how quickly we're delivering value – essentially, it's like our average speed in completing sprints.' Which of the following best captures the *true* meaning of velocity in Agile development?
Velocity isn't simply about individual speed or bug counts. It's a crucial metric that measures *team* performance over time – specifically, the average amount of work (typically measured in story points) completed within a sprint. This allows teams to forecast future sprints more accurately and understand trends in their delivery capacity. Misunderstanding velocity as solely individual productivity can lead to misaligned expectations and ineffective prioritization.
14 / 25
During a sprint planning meeting, the Development Team is discussing their capacity for the upcoming sprint. The team's Lead Developer states: 'Our velocity has been consistently around 50 story points lately, so we should aim to deliver roughly that much this sprint.' A newer team member raises a concern: 'But what if we have unexpected blockers or dependencies? Shouldn't we account for potential fluctuations in our capacity?' Which of the following best reflects the *purpose* of tracking velocity as a team?
Velocity is primarily used as a *predictive* metric – it represents the team's average capacity over time. Tracking velocity allows the team to estimate how much work they can realistically complete in a sprint, factoring in past performance and potential fluctuations. It's not about rigid targets or pressure, but rather informed planning based on historical data. Option A is incorrect because velocity isn't a constraint; options C and D are misinterpretations of its role.
15 / 25
During a daily standup, Developer Y says: "Our velocity is currently 55 story points. We need to maintain this pace to hit our sprint goal!" The team's Product Owner interjects, "But what if we're overestimating? Shouldn't we be more flexible and adjust based on actual progress?"
This scenario highlights a crucial aspect of Agile: velocity isn't a fixed target but rather an *average* that guides forecasting. The team needs to maintain velocity as a goal, but it must be combined with flexibility and the ability to adjust based on actual progress – ignoring potential risks or changes is a common mistake. The correct option reflects this balanced approach, acknowledging both the value of a consistent velocity and the need for adaptive planning.
16 / 25
During a sprint review, the Development Team demonstrates a newly completed feature. The Product Owner asks the team, 'What was your velocity for this sprint?' Team Member C responds: 'We delivered 25 story points this sprint.' The Scrum Master notices that the team's average velocity over the last three sprints has been significantly lower—around 18 story points per sprint. Which of the following best explains why this variance in velocity is important to monitor and discuss with the team?
Note: This scenario highlights the importance of understanding trends, not just individual sprint outputs.
Note: This scenario highlights the importance of understanding trends, not just individual sprint outputs.
Velocity isn't simply about the points delivered in a single sprint; it's a *trend* representing the team's capacity over time. Monitoring variance helps identify issues like changing priorities, new complexities introduced, or perhaps inconsistent estimation practices. Addressing these trends allows for proactive adjustments to future sprints and improves overall predictability. Focusing solely on a single sprint's output provides a misleading picture of true team performance.
17 / 25
During a sprint retrospective, the team discusses their velocity. Developer X says: 'Our velocity was really high last sprint – we delivered 85 story points! We should aim for that consistently.' The Scrum Master gently pushes back and asks the team to consider what factors might have contributed to this unusually high output. Which of the following is the MOST important thing the Scrum Master should emphasize to the team?
Velocity isn't just about the raw number of story points delivered; it represents the *sustainable* rate at which a team can consistently complete work. A high velocity in one sprint could be due to external factors (e.g., a simpler backlog) and wouldn't necessarily reflect the team's true capacity. The Scrum Master needs to guide the team towards understanding that velocity is an average over time, not a target for individual sprints, and that focusing on consistent delivery is key.
18 / 25
A developer is explaining the concept of 'velocity' to a new team member. He says: 'Velocity represents how quickly we're delivering value – essentially, it's like our average speed in completing sprints.' Which of the following best captures the *true* meaning of velocity in Agile development?
Velocity isn't simply about individual speed or bug counts. It's a crucial metric that measures *team* performance over time – specifically, the average amount of work (typically measured in story points) completed within a sprint. This allows teams to forecast future sprints more accurately and understand trends in their delivery capacity. Misunderstanding velocity as solely individual productivity can lead to misaligned expectations and ineffective prioritization.
19 / 25
During a sprint planning meeting, the Development Team is discussing their capacity for the upcoming sprint. The team's Lead Developer states: 'Our velocity has been consistently around 50 story points lately, so we should aim to deliver roughly that much this sprint.' A newer team member raises a concern: 'But what if we have unexpected blockers or dependencies? Shouldn't we account for potential fluctuations in our capacity?' Which of the following best reflects the *purpose* of tracking velocity as a team?
Velocity is primarily used as a *predictive* metric – it represents the team's average capacity over time. Tracking velocity allows the team to estimate how much work they can realistically complete in a sprint, factoring in past performance and potential fluctuations. It's not about rigid targets or pressure, but rather informed planning based on historical data. Option A is incorrect because velocity isn't a constraint; options C and D are misinterpretations of its role.
20 / 25
During a daily standup, Developer Y says: "Our velocity is currently 55 story points. We need to maintain this pace to hit our sprint goal!" The team's Product Owner interjects, "But what if we're overestimating? Shouldn't we be more flexible and adjust based on actual progress?"
This scenario highlights a crucial aspect of Agile: velocity isn't a fixed target but rather an *average* that guides forecasting. The team needs to maintain velocity as a goal, but it must be combined with flexibility and the ability to adjust based on actual progress – ignoring potential risks or changes is a common mistake. The correct option reflects this balanced approach, acknowledging both the value of a consistent velocity and the need for adaptive planning.
21 / 25
During a sprint review, the Development Team demonstrates a newly completed feature. The Product Owner asks the team, 'What was your velocity for this sprint?' Team Member C responds: 'We delivered 25 story points this sprint.' The Scrum Master notices that the team's average velocity over the last three sprints has been significantly lower—around 18 story points per sprint. Which of the following best explains why this variance in velocity is important to monitor and discuss with the team?
Note: This scenario highlights the importance of understanding trends, not just individual sprint outputs.
Note: This scenario highlights the importance of understanding trends, not just individual sprint outputs.
Velocity isn't simply about the points delivered in a single sprint; it's a *trend* representing the team's capacity over time. Monitoring variance helps identify issues like changing priorities, new complexities introduced, or perhaps inconsistent estimation practices. Addressing these trends allows for proactive adjustments to future sprints and improves overall predictability. Focusing solely on a single sprint's output provides a misleading picture of true team performance.
22 / 25
During a sprint retrospective, the team discusses their velocity. Developer X says: 'Our velocity was really high last sprint – we delivered 85 story points! We should aim for that consistently.' The Scrum Master gently pushes back and asks the team to consider what factors might have contributed to this unusually high output. Which of the following is the MOST important thing the Scrum Master should emphasize to the team?
Velocity isn't just about the raw number of story points delivered; it represents the *sustainable* rate at which a team can consistently complete work. A high velocity in one sprint could be due to external factors (e.g., a simpler backlog) and wouldn't necessarily reflect the team's true capacity. The Scrum Master needs to guide the team towards understanding that velocity is an average over time, not a target for individual sprints, and that focusing on consistent delivery is key.
23 / 25
A developer is explaining the concept of 'velocity' to a new team member. He says: 'Velocity represents how quickly we're delivering value – essentially, it's like our average speed in completing sprints.' Which of the following best captures the *true* meaning of velocity in Agile development?
Velocity isn't simply about individual speed or bug counts. It's a crucial metric that measures *team* performance over time – specifically, the average amount of work (typically measured in story points) completed within a sprint. This allows teams to forecast future sprints more accurately and understand trends in their delivery capacity. Misunderstanding velocity as solely individual productivity can lead to misaligned expectations and ineffective prioritization.
24 / 25
During a sprint planning meeting, the Development Team is discussing their capacity for the upcoming sprint. The team's Lead Developer states: 'Our velocity has been consistently around 50 story points lately, so we should aim to deliver roughly that much this sprint.' A newer team member raises a concern: 'But what if we have unexpected blockers or dependencies? Shouldn't we account for potential fluctuations in our capacity?' Which of the following best reflects the *purpose* of tracking velocity as a team?
Velocity is primarily used as a *predictive* metric – it represents the team's average capacity over time. Tracking velocity allows the team to estimate how much work they can realistically complete in a sprint, factoring in past performance and potential fluctuations. It's not about rigid targets or pressure, but rather informed planning based on historical data. Option A is incorrect because velocity isn't a constraint; options C and D are misinterpretations of its role.
25 / 25
During a daily standup, Developer Y says: "Our velocity is currently 55 story points. We need to maintain this pace to hit our sprint goal!" The team's Product Owner interjects, "But what if we're overestimating? Shouldn't we be more flexible and adjust based on actual progress?"
This scenario highlights a crucial aspect of Agile: velocity isn't a fixed target but rather an *average* that guides forecasting. The team needs to maintain velocity as a goal, but it must be combined with flexibility and the ability to adjust based on actual progress – ignoring potential risks or changes is a common mistake. The correct option reflects this balanced approach, acknowledging both the value of a consistent velocity and the need for adaptive planning.
Frequently Asked Questions
What will I practice in "Velocity & Capacity Vocabulary | Agile & Scrum Exercises"?
This is an Agile & Scrum exercise set. It walks through 25 scenario-based multiple-choice questions built around real usage of Agile & Scrum terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 25 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the Agile & Scrum vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Agile & Scrum exercises?
See the Agile & Scrum exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — Agile & Scrum vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.