Agile retrospectives have their own vocabulary. Knowing the right collocations — like facilitate the retro or surface issues — helps you communicate fluently in Scrum teams and write clear meeting notes.
0 / 5 completed
1 / 5
The scrum master will ___ the retrospective at the end of the sprint.
Facilitate is the standard collocation with retrospective. A scrum master facilitates a retro — meaning they guide the process neutrally without controlling the outcome. 'Organize' refers to scheduling, 'chair' is for formal meetings, and 'start' is too vague for this professional context.
2 / 5
A good retrospective helps the team ___ issues that have been invisible day-to-day.
Surface is the fixed collocation here: to surface issues means to bring hidden problems into the open for discussion. 'Discover' and 'find' imply searching from scratch. 'Expose' has a negative, accusatory tone. 'Surface' is the idiomatic Agile term.
3 / 5
Before the retro ends, every problem raised should produce concrete ___.
Action items is the fixed Agile collocation for specific, assigned, trackable outcomes from a meeting. 'Tasks' are work items in a backlog. 'Assignments' sound academic. 'Follow-ups' are vaguer and don't imply ownership. Action items are the standard retro deliverable.
4 / 5
After the retro, the team lead should ___ the loop by confirming which issues were resolved.
Close the loop is a fixed idiom meaning to follow up and confirm that a matter has been dealt with. 'Complete', 'finish', and 'end' can all mean to stop something, but none of them collocate with 'loop' in this professional communication sense.
5 / 5
The team decided to ___ a retrospective even though the sprint had gone well.
Run a retrospective is the most idiomatic collocation in Agile contexts. 'Hold' is also acceptable in formal settings. 'Do' and 'have' are too informal and imprecise for professional documentation or stand-up vocabulary. Run emphasizes active facilitation.