Basketball Retrospective
A team-sport metaphor built around a possession, not a scoreboard: who set someone up, where the team lost control, and how it recovered.
Free · No credit card · Guests join by link
The board
01
ASSIST
Who set someone else up to succeed this sprint?
02
TURNOVER
Where did we lose control or drop the ball?
03
REBOUND
How did we recover after something went wrong?
Basketball retrospective follows the flow of a single possession instead of a final score: an Assist sets a teammate up to succeed, a Turnover loses control of the ball, and a Rebound wins it back after a miss. Where a lot of sport-themed retros are really just Strengths/Risks/Learnings wearing a jersey, Assist asks a genuinely different question — not 'what went well', but 'who helped someone else succeed', which most retro formats never single out on its own.
Rebound does similar work for recovery: it's not a generic Learnings column, it's specifically 'how did we bounce back after this went wrong' — which keeps the retro forward-looking and action-oriented instead of just cataloguing what broke. Together the three columns map a complete possession: help, lose, recover.
When to use a Basketball Retrospective
- Teams that want collaboration itself named and credited, not just bundled into a general Strengths column
- After a sprint with a visible recovery story — a bad start turned around, an outage resolved well
- Sports-minded teams or companies where a shared basketball vocabulary already exists informally
- Any sprint where you want the same balance as Strengths·Risks·Learnings with a livelier, possession-based framing
How to run a Basketball Retrospective
- 1
Call the possession
Before writing, the facilitator names what the team was actually playing for this sprint — the release, the milestone, the deadline. In Retromik, put it in the board's focus question so it stays visible above every column.
- 2
Let assists name people
Assist is the one column where naming a teammate is the point: it's recognition. Cards stay anonymous, so people can give credit without it feeling awkward.
- 3
Talk about plays, not players, on turnovers
A turnover is where the team lost the ball: a duplicated fix, a missed hand-off. Ask what happened, not who dropped it.
- 4
Find out what made the rebound possible
For each strong Rebound card, ask what let the team recover so quickly. That's the habit to keep.
- 5
Draw up one play for the next game
Turn the biggest turnover into one concrete change with an owner.
Anonymous writing, voting, grouping and action items work the same as in any Retromik retro.
Example cards
What good cards look like for a software team. Specific, about the work, never about a person.
ASSIST
- Priya paired with the new joiner on their first release.
- QA wrote test cases before development started.
TURNOVER
- Two people fixed the same bug without knowing.
- Release notes went out with the wrong version number.
REBOUND
- We caught the bad migration in staging and rolled back in minutes.
- After the missed demo, we replanned the sprint in one meeting.
A 45-minute agenda
- 0–5 minCall the possession
- 5–15 minWrite cards silently
- 15–20 minVote, three votes each
- 20–35 minDiscuss the top turnovers and rebounds
- 35–45 minDraw up one play for next sprint
Common mistakes
- Turnovers that name a person. Rewrite them as the play that went wrong.
- Assists only coming from team leads. Everyone can credit everyone.
- Skipping Rebound. Recovery is a skill worth naming.
- Actions only about turnovers. A good rebound habit is worth protecting too.
Frequently asked questions
What is a Basketball retrospective?
A team-sport-themed retrospective with three columns: Assist (who helped a teammate succeed), Turnover (where the team lost control of something), and Rebound (how the team recovered after a mistake). It follows the flow of a possession — help, lose, recover — instead of a static win/loss list.
What makes Assist different from a normal Strengths column?
A Strengths column collects anything that went well, usually credited to no one in particular. Assist asks specifically who helped someone else succeed — a pairing session, a timely review, a heads-up that saved someone hours. It's a collaboration column, not a general wins column.
How is this different from Match Day, Retromik's football template?
Match Day is built around a single event: goals scored, fouls committed, standout plays. Basketball follows a possession instead — an assist leads to a score, a turnover loses it, a rebound wins it back. Pick whichever sport your team actually follows, or whichever flow feels more natural.
Is the Basketball template free?
Yes. Retromik is free — create a board with the Basketball template and share the link. Guests join without an account, and cards stay anonymous while people write.
Is it okay to name people in the Assist column?
Yes. Assists are recognition, and that's one of the reasons to use this format. Keep names out of the Turnover column, though: it's about what went wrong, not who.
Related templates
Match Day Retrospective
Goals · Fouls · MVP Moves
A football-flavored retro for teams who'd rather talk goals and fouls than strengths and risks — same substance, more fun to say out loud.
ViewBoxing Ring Retrospective
Jab · Sucker Punch · Corner
A combat-sport metaphor built around a single round: what steadily scored points, what hit you blind, and what your corner tells you before the bell.
ViewTV Drama Retrospective
Hero · Villain · Plot Twist · Cliffhanger
Run the sprint like a season finale: the hero, the villain, the twist nobody saw coming, and the cliffhanger you carry into next season.
ViewAchilles' Heel Retrospective
Achilles' Heel · Trojan Horse · Shield
Two of the oldest stories about hidden weakness, turned into a sprint retro: the vulnerability everyone knows about, and the risk that got in looking like a gift.
ViewRun a Basketball Retrospective with your team
Create the board in under a minute, share the link, and your team joins anonymously — no accounts needed for participants.
Start free