Practice the facilitation vocabulary for running sprint retrospectives: opening, time-boxing, grouping, action items, and closing.
0 / 20 completed
1 / 20
You are opening a sprint retrospective for a team that has had a difficult sprint with a production incident. Which opening best sets the tone?
Retrospective opening after a difficult sprint: name the format ('Start/Stop/Continue'), set the time structure ('5 minutes adding, then group, then discuss top 3'), establish the blameless ground rule ('systems and processes, not individual performance'), set the outcome expectation ('2-3 actionable improvements'), and launch the first phase ('silent adding'). Opening with 'let's talk about what went wrong' is unfocused. 'Who was responsible?' is blame — the antithesis of a blameless retro.
2 / 20
During the item-adding phase, a team member adds: 'the on-call rota is broken.' How do you handle this during silent adding?
The silent adding phase has one rule: add items, do not discuss. Discussion during adding creates two problems: it wastes time on items that may get merged or deprioritised, and it lets early discussion anchor the group's thinking before everyone has contributed. 'Note it for grouping' — the facilitator's job in this phase is to record, not filter or discuss. Ambiguous items get clarified during the grouping or voting phase.
3 / 20
Two items on the retro board are closely related: 'CI pipeline is too slow' and 'tests take forever to run.' How do you handle grouping?
Grouping related items: 'these feel related — should we merge?' + quick check with the authors. This preserves the intent of both items while avoiding duplicate discussion. The authors' consent matters — they may have intended different things with similar phrasings. Asking for 'quick yes/no' time-boxes the decision. Discarding one item or fully explaining each before merging wastes time in the grouping phase.
4 / 20
Discussion on one item has been running for 12 minutes with no resolution. The team has 3 more items to cover. How do you time-box?
Time-boxing an extended discussion: name the time elapsed ('12 minutes'), explain the impact on the agenda ('3 more items'), offer a bounded extension ('2 more minutes'), name the exit path ('dedicated session if unresolved'), ask for consent ('does that work?'). 'Time's up. Next item.' is abrupt and creates resentment if the topic is genuinely important. The facilitator's job is to balance depth with breadth.
5 / 20
The team has identified an improvement: 'Fix the deployment process.' How do you convert it to an actionable retro item?
Converting a vague improvement to an action item requires four elements: what specifically (which part of deployment), what the done state looks like, who owns it, and when it's due. 'Fix the deployment process' fails all four. As facilitator, your job is to ask these questions before closing the retro — not after. Items without owners and due dates are forgotten. 'Add it to the backlog' is the most common way retrospective actions die.
6 / 20
Context: You're reviewing a pull request for a new feature. A team member comments: 'This validation logic is overly complex; could we simplify it?' Which response best facilitates a productive discussion during the code review?
The key here is constructive feedback. Option 2 demonstrates willingness to consider changes and seeks clarification. Options 1 suggests immediate action without understanding, option 3 encourages specific details (crucial for problem-solving), and option 4 dismisses the concern prematurely – all of which are less effective in a code review setting. Focusing on 'what' is wrong and 'how' to improve is vital.
7 / 20
Context: You're in a Slack channel discussing the sprint retrospective. Sarah writes: 'I felt like we spent too much time debating the UI changes and not enough on the database performance.' How should you respond to encourage focused discussion?
Sarah's statement highlights a perceived imbalance. Option 1 is dismissive and unproductive. Option 2 directly prompts for more detail about her concern – this is the correct approach to understanding the issue before escalating it. Options 3 and 4 simply agree or move on without addressing the core feedback, which can be frustrating for the original speaker.
8 / 20
Context: During a sprint retrospective, the team is using an online whiteboard tool. A user suggests: 'Let's group 'Slow CI pipeline' and 'Tests take forever to run' because they're related.' How should you respond when grouping items on the board?
The team is using a technique called 'affinity mapping,' where related ideas are grouped together. Option 1 acknowledges the suggestion and facilitates further discussion. Option 2 prompts for the reasoning behind the grouping (critical to ensure it's valid). Options 3 and 4 avoid critical thinking, potentially leading to incorrect groupings. Grouping should be based on *why* things are linked.
9 / 20
Context: The team is using a Kanban board. After discussing 'Deployment process needs improvement' for 15 minutes with no clear action items, you realize it's going over time. What should you do?
Time-boxing is a key technique for managing discussions. Option 2 introduces a clear boundary to force focus and decision-making within a limited timeframe. Options 1 prolongs the unproductive discussion, option 3 avoids addressing the issue, and option 4 accepts inaction without attempting to resolve it – all of which are less effective than setting a time limit.
10 / 20
Context: The team identifies 'Improve monitoring for critical services' as an improvement. How do you translate this into a concrete action item for the next sprint?
The initial statement is too vague. Option 2 forces clarification – defining 'critical' requires specific criteria (services and metrics) to make it actionable. Options 1 simply acknowledges the suggestion without any commitment, option 3 adds it to a backlog without detail, and option 4 misses the point entirely. Action items must be clearly defined to facilitate implementation.
11 / 20
Context: You're reviewing a pull request for a new feature. A team member comments: 'This validation logic is overly complex; could we simplify it?' Which response best facilitates a productive discussion during the code review?
The key here is constructive feedback. Option 2 demonstrates willingness to consider changes and seeks clarification. Options 1 suggests immediate action without understanding, option 3 encourages specific details (crucial for problem-solving), and option 4 dismisses the concern prematurely – all of which are less effective in a code review setting. Focusing on 'what' is wrong and 'how' to improve is vital.
12 / 20
Context: You're in a Slack channel discussing the sprint retrospective. Sarah writes: 'I felt like we spent too much time debating the UI changes and not enough on the database performance.' How should you respond to encourage focused discussion?
Sarah's statement highlights a perceived imbalance. Option 1 is dismissive and unproductive. Option 2 directly prompts for more detail about her concern – this is the correct approach to understanding the issue before escalating it. Options 3 and 4 simply agree or move on without addressing the core feedback, which can be frustrating for the original speaker.
13 / 20
Context: During a sprint retrospective, the team is using an online whiteboard tool. A user suggests: 'Let's group 'Slow CI pipeline' and 'Tests take forever to run' because they're related.' How should you respond when grouping items on the board?
The team is using a technique called 'affinity mapping,' where related ideas are grouped together. Option 1 acknowledges the suggestion and facilitates further discussion. Option 2 prompts for the reasoning behind the grouping (critical to ensure it's valid). Options 3 and 4 avoid critical thinking, potentially leading to incorrect groupings. Grouping should be based on *why* things are linked.
14 / 20
Context: The team is using a Kanban board. After discussing 'Deployment process needs improvement' for 15 minutes with no clear action items, you realize it's going over time. What should you do?
Time-boxing is a key technique for managing discussions. Option 2 introduces a clear boundary to force focus and decision-making within a limited timeframe. Options 1 prolongs the unproductive discussion, option 3 avoids addressing the issue, and option 4 accepts inaction without attempting to resolve it – all of which are less effective than setting a time limit.
15 / 20
Context: The team identifies 'Improve monitoring for critical services' as an improvement. How do you translate this into a concrete action item for the next sprint?
The initial statement is too vague. Option 2 forces clarification – defining 'critical' requires specific criteria (services and metrics) to make it actionable. Options 1 simply acknowledges the suggestion without any commitment, option 3 adds it to a backlog without detail, and option 4 misses the point entirely. Action items must be clearly defined to facilitate implementation.
16 / 20
Context: You're reviewing a pull request for a new feature. A team member comments: 'This validation logic is overly complex; could we simplify it?' Which response best facilitates a productive discussion during the code review?
The key here is constructive feedback. Option 2 demonstrates willingness to consider changes and seeks clarification. Options 1 suggests immediate action without understanding, option 3 encourages specific details (crucial for problem-solving), and option 4 dismisses the concern prematurely – all of which are less effective in a code review setting. Focusing on 'what' is wrong and 'how' to improve is vital.
17 / 20
Context: You're in a Slack channel discussing the sprint retrospective. Sarah writes: 'I felt like we spent too much time debating the UI changes and not enough on the database performance.' How should you respond to encourage focused discussion?
Sarah's statement highlights a perceived imbalance. Option 1 is dismissive and unproductive. Option 2 directly prompts for more detail about her concern – this is the correct approach to understanding the issue before escalating it. Options 3 and 4 simply agree or move on without addressing the core feedback, which can be frustrating for the original speaker.
18 / 20
Context: During a sprint retrospective, the team is using an online whiteboard tool. A user suggests: 'Let's group 'Slow CI pipeline' and 'Tests take forever to run' because they're related.' How should you respond when grouping items on the board?
The team is using a technique called 'affinity mapping,' where related ideas are grouped together. Option 1 acknowledges the suggestion and facilitates further discussion. Option 2 prompts for the reasoning behind the grouping (critical to ensure it's valid). Options 3 and 4 avoid critical thinking, potentially leading to incorrect groupings. Grouping should be based on *why* things are linked.
19 / 20
Context: The team is using a Kanban board. After discussing 'Deployment process needs improvement' for 15 minutes with no clear action items, you realize it's going over time. What should you do?
Time-boxing is a key technique for managing discussions. Option 2 introduces a clear boundary to force focus and decision-making within a limited timeframe. Options 1 prolongs the unproductive discussion, option 3 avoids addressing the issue, and option 4 accepts inaction without attempting to resolve it – all of which are less effective than setting a time limit.
20 / 20
Context: The team identifies 'Improve monitoring for critical services' as an improvement. How do you translate this into a concrete action item for the next sprint?
The initial statement is too vague. Option 2 forces clarification – defining 'critical' requires specific criteria (services and metrics) to make it actionable. Options 1 simply acknowledges the suggestion without any commitment, option 3 adds it to a backlog without detail, and option 4 misses the point entirely. Action items must be clearly defined to facilitate implementation.
What will I practise in "Facilitating a Sprint Retrospective — Vocabulary"?
This module focuses on Meetings & Collaboration — real workplace phrasing you'll use on the job. It contains 20 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 20 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Meetings & Collaboration exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around meetings & collaboration — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Meetings & Collaboration exercises?
See the Meetings & Collaboration hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.