Sprint Planning Facilitation — Vocabulary and Language
Learn vocabulary for facilitating sprint planning: capacity, goal-setting, and commitment language.
0 / 10 completed
1 / 10
What is 'team capacity' in sprint planning vocabulary?
Capacity is the realistic available hours or story points for the sprint, adjusted for: planned absences, recurring meetings, support duties, and team ceremonies — not the theoretical maximum.
2 / 10
What is the 'sprint goal' in Scrum vocabulary?
The sprint goal is a single, coherent objective: e.g., 'Enable customers to manage their subscription from the mobile app.' It guides decisions during the sprint and provides flexibility in how the team achieves it.
3 / 10
What does 'commitment' mean in modern Scrum vocabulary (vs. original Scrum)?
Modern Scrum (2020 Scrum Guide) replaced 'committed' with 'forecasted' for sprint items. The team commits to the sprint goal, not to completing every single backlog item — reducing the pressure that led to overcommitment.
4 / 10
What is 'refinement' (backlog refinement) in Scrum planning vocabulary?
Refinement (formerly 'grooming') prepares backlog items for sprint planning: clarifying acceptance criteria, splitting epics into stories, adding technical notes, and estimating effort — so the team can pull them into a sprint confidently.
5 / 10
What does 'sprint backlog' mean?
The sprint backlog is the set of items the team selected for the sprint (from the product backlog) plus the detailed plan for achieving the sprint goal. It is a living artefact — developers update it daily.
6 / 10
Alex (the Scrum Master) asks you to 'pull the story' during the daily standup. Which of the following best describes what he means?
'Pulling the story' is a common idiom in Agile, particularly Scrum. It means requesting further detail or clarification about a user story from the Product Owner – essentially, asking for more information before committing to its implementation. The incorrect options misinterpret this as immediate coding or prioritization without seeking understanding.
7 / 10
You're writing the description for a pull request that includes a significant refactoring of a legacy module. Which phrase would be MOST effective in communicating this change to your team?
A good pull request description should clearly state the *purpose* of the change. Using terms like 'refactored' and specifically naming the affected module (legacyModule) provides context and transparency for reviewers. Options A and B are too vague; option D simply describes the act of updating code without explaining its significance.
8 / 10
During sprint planning, Sarah (a developer) suggests adding a new story to the sprint backlog. The Product Owner initially declines. What is the MOST appropriate response for you to offer?
Scrum emphasizes transparency and collaboration. Suggesting a new story without considering its impact on the Sprint Goal is counterproductive. The correct response focuses on a discussion of priority and alignment with the sprint's objectives, reflecting a core principle of iterative planning and adapting to changing needs.
9 / 10
You receive this API response:
{
"status": "error",
"message": "Insufficient details provided for the requested operation."
}
Which of the following actions should you take immediately after receiving it?
This API response indicates a problem with the input data. The most immediate action is to examine the request that generated this error – specifically, the parameters sent – to identify what's missing or incorrect. Simply escalating without investigation won't resolve the underlying issue.
10 / 10
Ben asks you during sprint planning, 'How are we tracking our velocity?' You should respond by explaining that velocity is:
Velocity is a key metric in Scrum that represents the *rate* at which a team completes work. It's calculated by summing up the story points completed across multiple sprints and provides insight into the team's capacity. The other options describe different aspects of sprint performance but don't define velocity itself.
What will I learn from the "Sprint Planning Facilitation — Vocabulary and Language" exercise?
Learn vocabulary for facilitating sprint planning: capacity, goal-setting, and commitment language.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall required.
How many questions are in this exercise?
This set contains 10 multiple-choice questions, each with a detailed explanation shown after you answer.
Do I need to create an account to track my progress?
No account is required. Your progress bar and score reset each time you reload the page, but you can retry the exercise as many times as you like.
Who is this Scrum Master Facilitation exercise for?
This exercise is built for IT professionals and non-native English speakers who need to read, write, and discuss scrum master facilitation topics confidently at work.
What happens if I answer a question incorrectly?
You will see the correct answer highlighted along with a detailed explanation of why it is correct -- so every wrong answer becomes a learning moment, not just a lost point.
Can I retry this exercise?
Yes -- click "Try again" on the results screen at any time to reset your score and go through all the questions again.
How long does this exercise take to complete?
Most learners finish all 10 questions in under 10 minutes, since each question is answered by clicking a single option.
Where can I find more Scrum Master Facilitation exercises?
See the full Scrum Master Facilitation exercises hub for more vocabulary drills on this topic.
Is this exercise mobile-friendly?
Yes -- the exercise works on any device with a modern browser, including phones and tablets, with no app download required.