5 exercises on retrospective phrases. Choose the most natural and professional option.
0 / 10 completed
1 / 10
You are opening the 'what went well' segment of a retrospective. Which phrase invites honest sharing without putting anyone on the spot?
Option C is best because it does two things at once: it models the behaviour you want (sharing a specific observation) and ends with an open invitation for others to contribute. Simply asking 'What went well?' (A) can leave the room silent because no one wants to go first. 'Tell me what went well' (B) sounds like an interrogation. 'Let's start the retro now' (D) is not even an invitation — it is a procedural announcement. Experienced facilitators seed the discussion by volunteering a concrete example, lowering the social risk for everyone else.
2 / 10
You want to suggest a process improvement diplomatically during the retro. Which phrasing is most effective?
Option A is the professional standard. It frames the idea as something you would 'love to see us try' — collaborative, forward-looking, and specific (30 minutes, before merging to main). 'We should have reviews before merging' (B) is vague and preachy. 'The reviews were bad this sprint' (C) is backward-looking and critical without a solution. 'People need to review code better' (D) implies blame without naming a specific improvement. In retros, the best suggestions are concrete, future-focused, and framed as experiments rather than mandates.
3 / 10
The team has identified a problem and you want to turn it into a concrete action item. Which phrase works best?
Option D is correct because it follows the golden rule of action items: named owner, clear deliverable, time-bound deadline. 'We should fix this' (A) has no owner and no deadline — it will be forgotten. 'Somebody needs to do something about this' (B) is even vaguer — 'somebody' almost always means nobody. 'Let's discuss this more next time' (C) defers without committing. In agile retrospectives, every action item must answer three questions: who, what, and when. Option D answers all three.
4 / 10
During the retro, someone points out a problem with code you wrote. How do you respond most professionally?
Option B is the most professional response. It acknowledges the feedback ('fair point'), shows self-awareness ('I underestimated the complexity'), and immediately redirects to a constructive question ('What would have helped?'). This models psychological safety for the rest of the team. 'That's not fair — I did my best' (A) is defensive and shuts down conversation. 'I don't agree' (C) without elaboration sounds combative. 'Thanks for the feedback' (D) is polite but passive — it does not contribute to improving the team's process.
5 / 10
You are closing the retro and want to move from discussion to action. Which phrase closes the meeting most productively?
Option A is the professional standard for closing a retro. It confirms you will capture action items, ensures every item has an owner (preventing diffusion of responsibility), and promises a written summary. 'OK, retro is done' (B) closes without consolidating anything. 'That's enough for today' (C) sounds dismissive. 'We're finished, goodbye' (D) is abrupt. A strong retro close always includes a read-back of action items, owner assignment, and a commitment to a follow-up record. Without these, retrospectives rarely generate lasting change.
6 / 10
Sarah from QA just flagged a potential null pointer exception in the new API endpoint. You're reviewing her comment on the PR. Which phrase best acknowledges the issue while maintaining a collaborative tone?
The key here is acknowledging the feedback without immediately dismissing it. Option 2 expresses gratitude and invites further discussion. Options 1 & 3 are inappropriate for constructive criticism, while option 4 minimizes the significance of the issue which can discourage reporting.
7 / 10
David sends a Slack message to the team: 'The performance of the user_authentication service is noticeably slow during peak hours.' Which phrase best reframes this as a suggestion for improvement?
Option 2 is too forceful and creates defensiveness. Option 1 accepts a bad situation without proposing solutions. Option 3 presents the feedback as a constructive suggestion for investigation. Option 4 avoids addressing the problem entirely.
8 / 10
You're writing the description for a Pull Request that introduces a new feature: a rate limiting mechanism for API calls. The PR has received several comments highlighting potential complexity. Which phrase best summarizes this in the PR description to set expectations?
Honesty about potential complexity is vital. Option 1 is misleading. Options 3 & 4 downplay the issue and could lead to unexpected problems later. Option 2 acknowledges that testing will be required.
9 / 10
During a standup update, you mention: 'I spent yesterday debugging an issue with the payment_processing module.' A teammate asks, 'What was causing the problem?' Which phrase best responds to this question in a way that promotes further discussion?
Providing a concise explanation of the root cause is essential for understanding and preventing similar issues. Option 1 avoids sharing information, while option 3 shuts down discussion and option 4 deflects responsibility. This response encourages further investigation or learning.
10 / 10
You're leading the retrospective and want to transition from discussing problems to outlining concrete steps for improvement. Which phrase best signals this shift?
This phrase clearly indicates the transition from discussion to actionable steps. Options 1 & 2 are simply restatements of the problem and option 4 attempts to prolong unproductive conversation. Using 'formulating an action plan' provides a direct signal for moving forward.
What will I practise in "Retrospective Phrases: Giving Constructive Feedback"?
This module focuses on Phrasebook — real workplace phrasing you'll use on the job. It contains 10 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 10 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 Phrasebook exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasebook — 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 Phrasebook exercises?
See the Phrasebook 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.