5 exercises — Practice the language of Scrum facilitation: timeboxing, voting techniques, retrospective formats, and collaborative structures used in agile ceremonies.
Outcomes: action items, accountability, retrospective prime directive
Key phrase: "Regardless of what we discover, we understand and truly believe that everyone did the best job they could." (prime directive)
0 / 30 completed
1 / 30
The Scrum Master opens the retrospective: "Before we start discussing, I'd like everyone to write their thoughts on sticky notes — no talking yet. We'll share them one at a time using round robin. Any topics that come up but aren't on today's agenda go into the parking lot."
What is the purpose of a parking lot in a facilitated meeting?
Parking lot: a facilitation technique for capturing valuable but off-topic items so the group can stay focused without losing the idea. Items in the parking lot are reviewed at the end of the session or scheduled for a future meeting.
Related facilitation vocabulary: Round robin — a structured turn-taking format where each person speaks in sequence, ensuring equal participation. Silent brainstorm — participants write ideas independently before sharing aloud, reducing groupthink and giving quieter voices equal weight. Ice-breaker — a short activity at the start of a meeting to warm up the group and lower social barriers. Facilitation — the act of guiding a group through a process to achieve a shared goal, without directing the outcome. In conversation: "Let's park that — it's important but out of scope for today's retro."
2 / 30
At the end of sprint planning, the Scrum Master says: "We've been in this room for 90 minutes. Remember, we have a two-hour timebox for planning. That gives us 30 minutes to finish the sprint backlog and confirm the sprint goal — then we're done, whether we feel fully ready or not."
Which statement best describes the concept of a timebox?
Timebox: a strict, fixed time limit for an activity. When the timebox expires, the activity ends — even if the work is not complete. Timeboxing prevents ceremonies from overrunning and forces prioritisation within the available time.
Scrum ceremony timeboxes (for a one-month sprint): Sprint Planning ≤ 8 hours; Daily Scrum ≤ 15 minutes; Sprint Review ≤ 4 hours; Sprint Retrospective ≤ 3 hours. For two-week sprints, these are proportionally shorter. Key phrase: "We're timeboxed to 30 minutes — let's focus on the most important questions." Diverge-converge is a facilitation pattern that pairs this with time: first diverge (generate ideas freely), then converge (narrow down, decide) — each phase is typically timeboxed separately.
3 / 30
The Scrum Master explains two techniques to a new team member: "For choosing which topics to discuss, I'll use dot voting — everyone gets three dots and sticks them on their preferred items. For checking team consensus on a decision, I'll use fist-to-five. Show zero fingers — a fist — if you completely oppose. Show five fingers if you fully support. Anything below three means we need more discussion."
In a fist-to-five vote, what does showing two fingers typically signal?
Fist-to-five scale: 0 (fist) = block/veto; 1 = serious concerns, not ready to proceed; 2 = significant concerns, needs discussion; 3 = can live with it, will support; 4 = good idea, minor reservations; 5 = fully support. Decisions proceed when everyone shows 3 or above. If anyone shows 0–2, the facilitator surfaces concerns before moving on.
Dot voting: each participant receives a fixed number of dots (typically 3–5) to allocate across options. They can concentrate all dots on one item or spread them. The item with the most dots is prioritised. Useful for selecting retrospective topics, prioritising improvement ideas, or choosing between options. Both techniques support facilitation by making preferences visible, reducing dominance by louder voices, and generating quick, transparent decisions.
4 / 30
Complete the Scrum Master's sentence: "We're going to run a ___________ retro today. I'll put three columns on the board: one for things we want to start doing, one for things we should stop doing, and one for things that are working well and we should keep doing."
Which retrospective format is being described?
Start/Stop/Continue: one of the most widely used retrospective formats. Three columns map directly to actionable categories — Start (new practices to adopt), Stop (habits or processes to drop), Continue (what is already working). It is action-oriented by design.
4Ls (Liked, Learned, Lacked, Longed For): encourages reflection on both positive experiences and gaps. "Lacked" surfaces missing resources or support; "Longed For" captures aspirational improvements. Mad-Sad-Glad: an emotion-first format that surfaces team morale and psychological safety issues. The facilitator clusters emotional responses before deriving action items. Liberating Structures: a collection of 33 facilitation microstructures (e.g. 1-2-4-All, TRIZ, Troika Consulting) designed to include every voice and avoid conventional meeting traps. All three are valid retrospective formats — the facilitator chooses based on team context and goals.
5 / 30
The Scrum Master reads out the prime directive at the start of the retrospective: "Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."
The team then identifies three improvement actions and assigns an owner and a due date to each.
What is the primary purpose of the retrospective prime directive?
Retrospective prime directive (Norm Kerth): creates psychological safety by framing the retrospective as an inquiry into systemic issues rather than individual blame. Without this, team members self-censor, and the retrospective loses its value.
Action items: specific, concrete improvements the team commits to implementing before the next retrospective. Effective action items follow the SMART format and each has a single named owner. Accountability: the expectation that the owner will follow through and report progress. The Scrum Master often opens the next retrospective by reviewing the previous sprint's action items. Without accountability, retrospectives become "complaining sessions" with no lasting change. Key phrase: "Every action item needs an owner and a date — otherwise it's just a wish."
6 / 30
During a sprint retrospective, the team lead asks: "What's one thing we could have done differently to improve our workflow?" A developer responds with, 'I wish I had asked for clarification on that task earlier.' Which phrase best describes this situation?
Lack of clarity refers to a situation where requirements or expectations were not clearly defined, leading to confusion and potentially rework. Technical debt is accumulated costs from prioritizing short-term fixes over long-term solutions. Scope creep describes uncontrolled expansion of the project scope. The core issue here is the missing information.
7 / 30
"I'm seeing a lot of comments on this PR about inconsistent naming conventions across modules. It's making it hard to understand the code and track down bugs."
Code review feedback specifically addresses issues identified during the process of reviewing code changes. While inconsistent naming can contribute to technical debt, the immediate concern is the direct feedback received on a specific PR. Feature requests are for new functionality, sprint planning concerns the overall roadmap.
8 / 30
"Okay team, let's quickly run through the last two days of work. Sarah, you were working on the user authentication module? What roadblocks did you encounter?", Sarah replies: "I spent a lot of time debugging intermittent issues with the API calls."
Sprint retrospective is the appropriate setting for discussing challenges and impediments encountered during a sprint. A daily stand-up focuses on immediate progress updates. User story definition occurs during sprint planning, while technical documentation supports development tasks.
9 / 30
"We need to address the fact that we've been consistently missing our velocity targets over the last few sprints. What's a good way to investigate this?"
A Fishbone diagram analysis (also known as an Ishikawa diagram) is a structured technique for identifying the potential root causes of a problem. Kanban is a workflow management system. A spike is a time-boxed research activity, and refactoring legacy code addresses technical debt—neither directly investigates velocity issues.
10 / 30
"The team's been struggling to prioritize tasks during sprint planning. I want to introduce a method to help us focus on the most valuable items."
A Kanban board provides a visual representation of workflow stages and helps teams prioritize tasks based on their current status. A burnup chart tracks completed vs. remaining work over time; value stream mapping focuses on process efficiency; and daily scrum meetings are for status updates.
11 / 30
During a sprint retrospective, the team lead asks: "What's one thing we could have done differently to improve our workflow?" A developer responds with, 'I wish I had asked for clarification on that task earlier.' Which phrase best describes this situation?
Lack of clarity refers to a situation where requirements or expectations were not clearly defined, leading to confusion and potentially rework. Technical debt is accumulated costs from prioritizing short-term fixes over long-term solutions. Scope creep describes uncontrolled expansion of the project scope. The core issue here is the missing information.
12 / 30
"I'm seeing a lot of comments on this PR about inconsistent naming conventions across modules. It's making it hard to understand the code and track down bugs."
Code review feedback specifically addresses issues identified during the process of reviewing code changes. While inconsistent naming can contribute to technical debt, the immediate concern is the direct feedback received on a specific PR. Feature requests are for new functionality, sprint planning concerns the overall roadmap.
13 / 30
"Okay team, let's quickly run through the last two days of work. Sarah, you were working on the user authentication module? What roadblocks did you encounter?", Sarah replies: "I spent a lot of time debugging intermittent issues with the API calls."
Sprint retrospective is the appropriate setting for discussing challenges and impediments encountered during a sprint. A daily stand-up focuses on immediate progress updates. User story definition occurs during sprint planning, while technical documentation supports development tasks.
14 / 30
"We need to address the fact that we've been consistently missing our velocity targets over the last few sprints. What's a good way to investigate this?"
A Fishbone diagram analysis (also known as an Ishikawa diagram) is a structured technique for identifying the potential root causes of a problem. Kanban is a workflow management system. A spike is a time-boxed research activity, and refactoring legacy code addresses technical debt—neither directly investigates velocity issues.
15 / 30
"The team's been struggling to prioritize tasks during sprint planning. I want to introduce a method to help us focus on the most valuable items."
A Kanban board provides a visual representation of workflow stages and helps teams prioritize tasks based on their current status. A burnup chart tracks completed vs. remaining work over time; value stream mapping focuses on process efficiency; and daily scrum meetings are for status updates.
16 / 30
During a sprint retrospective, the team lead asks: "What's one thing we could have done differently to improve our workflow?" A developer responds with, 'I wish I had asked for clarification on that task earlier.' Which phrase best describes this situation?
Lack of clarity refers to a situation where requirements or expectations were not clearly defined, leading to confusion and potentially rework. Technical debt is accumulated costs from prioritizing short-term fixes over long-term solutions. Scope creep describes uncontrolled expansion of the project scope. The core issue here is the missing information.
17 / 30
"I'm seeing a lot of comments on this PR about inconsistent naming conventions across modules. It's making it hard to understand the code and track down bugs."
Code review feedback specifically addresses issues identified during the process of reviewing code changes. While inconsistent naming can contribute to technical debt, the immediate concern is the direct feedback received on a specific PR. Feature requests are for new functionality, sprint planning concerns the overall roadmap.
18 / 30
"Okay team, let's quickly run through the last two days of work. Sarah, you were working on the user authentication module? What roadblocks did you encounter?", Sarah replies: "I spent a lot of time debugging intermittent issues with the API calls."
Sprint retrospective is the appropriate setting for discussing challenges and impediments encountered during a sprint. A daily stand-up focuses on immediate progress updates. User story definition occurs during sprint planning, while technical documentation supports development tasks.
19 / 30
"We need to address the fact that we've been consistently missing our velocity targets over the last few sprints. What's a good way to investigate this?"
A Fishbone diagram analysis (also known as an Ishikawa diagram) is a structured technique for identifying the potential root causes of a problem. Kanban is a workflow management system. A spike is a time-boxed research activity, and refactoring legacy code addresses technical debt—neither directly investigates velocity issues.
20 / 30
"The team's been struggling to prioritize tasks during sprint planning. I want to introduce a method to help us focus on the most valuable items."
A Kanban board provides a visual representation of workflow stages and helps teams prioritize tasks based on their current status. A burnup chart tracks completed vs. remaining work over time; value stream mapping focuses on process efficiency; and daily scrum meetings are for status updates.
21 / 30
During a sprint retrospective, the team lead asks: "What's one thing we could have done differently to improve our workflow?" A developer responds with, 'I wish I had asked for clarification on that task earlier.' Which phrase best describes this situation?
Lack of clarity refers to a situation where requirements or expectations were not clearly defined, leading to confusion and potentially rework. Technical debt is accumulated costs from prioritizing short-term fixes over long-term solutions. Scope creep describes uncontrolled expansion of the project scope. The core issue here is the missing information.
22 / 30
"I'm seeing a lot of comments on this PR about inconsistent naming conventions across modules. It's making it hard to understand the code and track down bugs."
Code review feedback specifically addresses issues identified during the process of reviewing code changes. While inconsistent naming can contribute to technical debt, the immediate concern is the direct feedback received on a specific PR. Feature requests are for new functionality, sprint planning concerns the overall roadmap.
23 / 30
"Okay team, let's quickly run through the last two days of work. Sarah, you were working on the user authentication module? What roadblocks did you encounter?", Sarah replies: "I spent a lot of time debugging intermittent issues with the API calls."
Sprint retrospective is the appropriate setting for discussing challenges and impediments encountered during a sprint. A daily stand-up focuses on immediate progress updates. User story definition occurs during sprint planning, while technical documentation supports development tasks.
24 / 30
"We need to address the fact that we've been consistently missing our velocity targets over the last few sprints. What's a good way to investigate this?"
A Fishbone diagram analysis (also known as an Ishikawa diagram) is a structured technique for identifying the potential root causes of a problem. Kanban is a workflow management system. A spike is a time-boxed research activity, and refactoring legacy code addresses technical debt—neither directly investigates velocity issues.
25 / 30
"The team's been struggling to prioritize tasks during sprint planning. I want to introduce a method to help us focus on the most valuable items."
A Kanban board provides a visual representation of workflow stages and helps teams prioritize tasks based on their current status. A burnup chart tracks completed vs. remaining work over time; value stream mapping focuses on process efficiency; and daily scrum meetings are for status updates.
26 / 30
During a sprint retrospective, the team lead asks: "What's one thing we could have done differently to improve our workflow?" A developer responds with, 'I wish I had asked for clarification on that task earlier.' Which phrase best describes this situation?
Lack of clarity refers to a situation where requirements or expectations were not clearly defined, leading to confusion and potentially rework. Technical debt is accumulated costs from prioritizing short-term fixes over long-term solutions. Scope creep describes uncontrolled expansion of the project scope. The core issue here is the missing information.
27 / 30
"I'm seeing a lot of comments on this PR about inconsistent naming conventions across modules. It's making it hard to understand the code and track down bugs."
Code review feedback specifically addresses issues identified during the process of reviewing code changes. While inconsistent naming can contribute to technical debt, the immediate concern is the direct feedback received on a specific PR. Feature requests are for new functionality, sprint planning concerns the overall roadmap.
28 / 30
"Okay team, let's quickly run through the last two days of work. Sarah, you were working on the user authentication module? What roadblocks did you encounter?", Sarah replies: "I spent a lot of time debugging intermittent issues with the API calls."
Sprint retrospective is the appropriate setting for discussing challenges and impediments encountered during a sprint. A daily stand-up focuses on immediate progress updates. User story definition occurs during sprint planning, while technical documentation supports development tasks.
29 / 30
"We need to address the fact that we've been consistently missing our velocity targets over the last few sprints. What's a good way to investigate this?"
A Fishbone diagram analysis (also known as an Ishikawa diagram) is a structured technique for identifying the potential root causes of a problem. Kanban is a workflow management system. A spike is a time-boxed research activity, and refactoring legacy code addresses technical debt—neither directly investigates velocity issues.
30 / 30
"The team's been struggling to prioritize tasks during sprint planning. I want to introduce a method to help us focus on the most valuable items."
A Kanban board provides a visual representation of workflow stages and helps teams prioritize tasks based on their current status. A burnup chart tracks completed vs. remaining work over time; value stream mapping focuses on process efficiency; and daily scrum meetings are for status updates.
These modules build the same on-the-job skills as Scrum Facilitation Vocabulary
— work through them together for a fuller vocabulary set.
Scrum & Agile— useful for Retrospective facilitation (Project Manager)
Frequently Asked Questions
What does the "Scrum Facilitation Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to scrum facilitation vocabulary through 30 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 30 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — this module shares real-world context with 1 other vocabulary module. See "Related vocabulary" below to keep building a connected skill set.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.