A useful retrospective ice breaker does two jobs: it gets people talking, and it hands the retro a small shared event to examine before the real sprint. One five-minute bomb round does both. The team plays, then fills the usual three columns about the round, which warms up the habit of honest feedback on something with no stakes.
Why a retrospective ice breaker should produce material for the retro
A retrospective ice breaker should produce material for the retro because the hardest part of a retrospective is starting. People hesitate to name what went wrong in their own sprint. An event everyone just shared, with no consequences, gives them practice at saying "this broke down" before the topic is their actual work.
Most ice breakers are disconnected from what follows. A one-word check-in or a quick question about the weekend fills two minutes and is forgotten. The retro then starts cold, with the facilitator waiting for the first sticky note.
A bomb round is different because it is a tiny project. In Bomb Appétit, one player, the Defuser, sees a bomb. The others, the Experts, have the manual and cannot see the bomb. They have to agree on what is there, decide what to do, and act under a timer. Something always goes well, something always goes wrong, and both are fresh in everyone's mind.
That gives the retro a warm-up board to fill. Ten minutes later, the same columns apply to the sprint, and people have already practised using them.
One bomb before the retrospective: timing and mission
Play one bomb before the retrospective, and keep it to about ten minutes in total: two minutes to set up, five on the timer, three to fill the board. Choose a short mission the team can finish. First bite, one module on a five-minute clock, suits a team that has never played. Strange symbols suits one that has.
Setup is quick if the facilitator prepares. They open Play, create an online room and post its five-letter code in the call once people have arrived. Experts open the standard manual, rule seed 1, in their own tab. The game is free and needs no install or account, so nobody loses time signing up.
Pick the Defuser in advance. Rotate it sprint by sprint so it is not always the same person. One bomb holds up to five players, so a larger team either plays in two rooms or has the extra people watch the board instead.
Avoid missions with needy modules for this slot. Those modules wake up during the round and demand attention, and they stretch a five-minute warm-up into a longer, noisier game. Save them for a separate session.
How does one bomb fill the retrospective board?
One bomb fills the retrospective board when each person adds one note per column about the round: what went well, what went wrong, and what to try next time. Specific moments make the best notes. "Read the serial number before anything else" beats "good communication", and the facilitator can ask for that level of detail.
Here is an example board from one invented round of Strange symbols. The round, the strikes and the notes are all examples, not real results.
| Went well | Went wrong | Try next |
|---|---|---|
| The Defuser read all the edgework at the start | Two Experts gave different instructions for the button at once | One Expert owns each module and speaks for it |
| We agreed a name for the strange glyph in ten seconds | A strike when "second wire" was heard as "second blue wire" | The Defuser repeats the instruction back before acting |
| Nobody blamed anyone after the strike | Nobody watched the clock until the last minute | One Expert calls the time at each minute |
Notice that every row names a communication habit, not a person. That is the tone the facilitator wants for the sprint retro too.
Then move to the real board. Some teams find that a note from the bomb round reappears in the sprint column almost word for word: two people answering at once, or a detail that got lost in a handover. When that happens, the bomb has done its job.
For a deeper set of prompts, see the list of debrief questions after a team building bomb round. If you want to turn the "try next" column into specific changes for the next round, there is a short guide to changes worth trying in the next communication round.
When should the retro skip the ice breaker?
The retro should skip the ice breaker when the sprint went badly enough that the team needs the full time on it, or when something serious happened that a game would trivialize. A missed launch, a painful incident or a conflict inside the team all deserve a retro that starts with them, not with a bomb.
Skip it too if the team is short on time. A retrospective squeezed to thirty minutes cannot spare ten for a warm-up, and the real topics will suffer.
Make it optional for anyone who would rather not play. An ice breaker that half the team resents does not warm anyone up. People can watch and still add notes to the board.
Finally, skip it when it has become routine. If the team plays the same mission every sprint, the board fills with the same notes. Change the mission, rotate the Defuser, or drop the bomb for a few sprints.
Teams spread across regions can still use the format by running the bomb in each region's own slot; the guide to remote team building across time zones shows how. For other games that keep every person involved, see team building games for work where nobody sits out, and for the fuller debrief that follows a longer session, the guide to team building communication games and the bomb debrief.