4 exercises — writing constructive retro items, turning personal blame into systemic observations, facilitating safely, and proposing SMART action items.
0 / 19 completed
1 / 19
You're writing a "What Went Well" item for the retrospective board. Which entry is most useful to the team?
Option C is the ideal "What Went Well" entry because it:
Names a specific practice: pair programming sessions — not just "teamwork" Links it to a specific outcome: caught the authentication bug early Proposes making it systematic: "worth building into the process" — turns an observation into a potential improvement
Why vague entries fail: "Everything went well" — no actionable signal; the team can't repeat what they can't name "Good sprint" — means nothing without specifics "We finished all the stories" — describes the outcome, not the practice that enabled it
The purpose of "What Went Well" is not celebration — it's to identify specific practices and behaviours worth repeating or institutionalising. If the team can't name the specific thing that worked, they can't deliberately do it again next sprint.
Format that works: [Specific practice or event] → [Specific positive outcome] → [Optional: how to build on it]
2 / 19
You want to write a "Could Be Better" retro item about missed deadlines without blaming any individual. Which phrasing is most constructive?
Option C demonstrates how to raise problems constructively in retros:
Describes the pattern, not the person: "deployment delays in the last two sprints" — systemic observation, not individual blame Quantifies the impact: "missed our release window twice" — makes the cost of the problem clear Proposes concrete next steps: audit CI/CD configuration + create a runbook — specific, actionable, not just "fix it"
Why the others fail: A — Personal blame shuts down psychological safety; people stop being honest at retros when they fear being singled out B — "Some people don't know" is passive-aggressive blame; "some people" is obvious code for specific people D — "Communicate better" and "be more organised" are the most common useless retro items; they describe desired states, not root causes or solutions
Retro language rules: • Describe systems and processes, not people • Name specific events, not personalities • Propose concrete next steps (what exactly should we do?) • Use "we" not "you" or "they" • If you can't propose a next step, ask: "What would success look like?"
3 / 19
You're facilitating the retro. During the discussion phase, a developer says: "The problem is Maria's estimates are always wrong and it causes us to overcommit." How do you handle this?
Option C demonstrates expert retro facilitation: reframe from personal to systemic.
Reframe technique: "It sounds like we have a broader challenge with estimation accuracy" — takes the spotlight off Maria and puts it on the system that produces inaccurate estimates Invites root cause analysis: offers three concrete hypotheses (hidden dependencies, unclear requirements, larger-than-expected tasks) Stays curious, not defensive: "What specific factors made estimation difficult?" — opens inquiry
Why the others fail: A — "Defend your estimates" puts Maria in the dock; she will feel attacked, become defensive, and the discussion becomes adversarial B — "Everyone who estimates badly" still encodes blame in different words; and it doesn't solve the root cause D — Avoiding the topic lets it fester; the retro exists specifically to have these conversations safely
Facilitation reframe phrases: • "It sounds like the underlying issue is…" • "Let's zoom out — what would need to be true for this to happen systemically?" • "Can we explore that as a system problem rather than an individual one?" • "What factors outside any one person's control contributed to this?"
4 / 19
The retro has surfaced several problems. You want to propose a concrete action item. Which format is most effective?
Option C follows the SMART action item format that retros require to actually produce change:
Specific: PR review turnaround SLA, 24-hour target — not "improve communication" Measurable: 24 hours is a verifiable standard Assigned: Alex is the named owner — not "the team" or "everyone" Time-bound: by Friday — not "soon" or "next sprint" Reviewable: "revisit in the next retro" — closes the loop
Why unspecific action items fail: "Try to do better" — no owner, no deadline, no success criterion "Add to backlog" — the backlog is where good intentions go to die; retro actions need dedicated owners, not a backlog ticket that never gets prioritised "Be more proactive" — means nothing without a specific behaviour change
The critical test for an action item: If you can't answer "who does what by when and how will we know it happened?" — it's not an action item, it's a wish.
5 / 19
John from the QA team just left a comment on your PR describing a critical bug. He says: 'This introduces a race condition – potential data corruption.' Which response is most appropriate to acknowledge his feedback and move the review forward?
Acknowledging the issue and requesting further clarification demonstrates professionalism and a willingness to understand the technical details. Options 'B' and 'C' are inappropriate as they shift responsibility or show a lack of understanding. Option 'D' deflects the problem without action; John has clearly identified a serious concern.
6 / 19
You're drafting a Slack message to announce that the 'Phoenix' API endpoint is now deprecated. The team uses this endpoint extensively. Which of these messages best communicates the change while minimizing disruption?
This message clearly states the deprecation, provides a timeframe (July 15th), and directs users to the alternative solution (falcon). Options 'A' is overly aggressive and unhelpful. Option 'C' lacks specifics, while option 'D' is too informal and directive.
7 / 19
During a sprint retrospective, the team identifies that their communication channels are fragmented, leading to duplicated effort. You want to propose a solution. Which of the following PR description snippets is most effective for documenting this action item?
A good action item description is specific, actionable, and includes the outcome you're aiming for. Option 'B' provides a vague solution; option 'D' is too informal. Option 'A' simply states the problem without offering a concrete step.
8 / 19
Sarah, a senior developer, says during a retro: 'I feel like I'm always being asked to fix other people's mistakes. It's frustrating and impacts my own productivity.' How should you respond constructively in the meeting?
This response validates Sarah's feelings, acknowledges the potential issue with workload distribution, and opens a dialogue for finding a solution. Options 'A', 'C', and 'D' are dismissive and unhelpful, failing to address the underlying concern.
9 / 19
You're writing a summary of the sprint retrospective for the team's internal knowledge base. The key takeaway was that the team consistently underestimated the time required for user story acceptance tests. Which sentence best captures this insight?
This sentence accurately identifies the core issue – underestimation of testing time – and frames it as an area for improvement. Options 'A', 'C', and 'D' are too general or positive to highlight a critical problem that needs addressing.
10 / 19
John from the QA team just left a comment on your PR describing a critical bug. He says: 'This introduces a race condition – potential data corruption.' Which response is most appropriate to acknowledge his feedback and move the review forward?
Acknowledging the issue and requesting further clarification demonstrates professionalism and a willingness to understand the technical details. Options 'B' and 'C' are inappropriate as they shift responsibility or show a lack of understanding. Option 'D' deflects the problem without action; John has clearly identified a serious concern.
11 / 19
You're drafting a Slack message to announce that the 'Phoenix' API endpoint is now deprecated. The team uses this endpoint extensively. Which of these messages best communicates the change while minimizing disruption?
This message clearly states the deprecation, provides a timeframe (July 15th), and directs users to the alternative solution (falcon). Options 'A' is overly aggressive and unhelpful. Option 'C' lacks specifics, while option 'D' is too informal and directive.
12 / 19
During a sprint retrospective, the team identifies that their communication channels are fragmented, leading to duplicated effort. You want to propose a solution. Which of the following PR description snippets is most effective for documenting this action item?
A good action item description is specific, actionable, and includes the outcome you're aiming for. Option 'B' provides a vague solution; option 'D' is too informal. Option 'A' simply states the problem without offering a concrete step.
13 / 19
Sarah, a senior developer, says during a retro: 'I feel like I'm always being asked to fix other people's mistakes. It's frustrating and impacts my own productivity.' How should you respond constructively in the meeting?
This response validates Sarah's feelings, acknowledges the potential issue with workload distribution, and opens a dialogue for finding a solution. Options 'A', 'C', and 'D' are dismissive and unhelpful, failing to address the underlying concern.
14 / 19
You're writing a summary of the sprint retrospective for the team's internal knowledge base. The key takeaway was that the team consistently underestimated the time required for user story acceptance tests. Which sentence best captures this insight?
This sentence accurately identifies the core issue – underestimation of testing time – and frames it as an area for improvement. Options 'A', 'C', and 'D' are too general or positive to highlight a critical problem that needs addressing.
15 / 19
John from the QA team just left a comment on your PR describing a critical bug. He says: 'This introduces a race condition – potential data corruption.' Which response is most appropriate to acknowledge his feedback and move the review forward?
Acknowledging the issue and requesting further clarification demonstrates professionalism and a willingness to understand the technical details. Options 'B' and 'C' are inappropriate as they shift responsibility or show a lack of understanding. Option 'D' deflects the problem without action; John has clearly identified a serious concern.
16 / 19
You're drafting a Slack message to announce that the 'Phoenix' API endpoint is now deprecated. The team uses this endpoint extensively. Which of these messages best communicates the change while minimizing disruption?
This message clearly states the deprecation, provides a timeframe (July 15th), and directs users to the alternative solution (falcon). Options 'A' is overly aggressive and unhelpful. Option 'C' lacks specifics, while option 'D' is too informal and directive.
17 / 19
During a sprint retrospective, the team identifies that their communication channels are fragmented, leading to duplicated effort. You want to propose a solution. Which of the following PR description snippets is most effective for documenting this action item?
A good action item description is specific, actionable, and includes the outcome you're aiming for. Option 'B' provides a vague solution; option 'D' is too informal. Option 'A' simply states the problem without offering a concrete step.
18 / 19
Sarah, a senior developer, says during a retro: 'I feel like I'm always being asked to fix other people's mistakes. It's frustrating and impacts my own productivity.' How should you respond constructively in the meeting?
This response validates Sarah's feelings, acknowledges the potential issue with workload distribution, and opens a dialogue for finding a solution. Options 'A', 'C', and 'D' are dismissive and unhelpful, failing to address the underlying concern.
19 / 19
You're writing a summary of the sprint retrospective for the team's internal knowledge base. The key takeaway was that the team consistently underestimated the time required for user story acceptance tests. Which sentence best captures this insight?
This sentence accurately identifies the core issue – underestimation of testing time – and frames it as an area for improvement. Options 'A', 'C', and 'D' are too general or positive to highlight a critical problem that needs addressing.
What will I practise in "Sprint Retrospective Language"?
This module focuses on Meetings & Collaboration — real workplace phrasing you'll use on the job. It contains 19 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 19 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.