Tennis Retrospective

Review your sprint like a tennis match

Try this retrospective live

Ground Strokes

What set us up for success?

Our daily stand-ups helped us maintain clear communication throughout the sprint
Having updated documentation made onboarding new team members much smoother
Regular code reviews helped us maintain quality standards
Aces

What great wins did we deliver?

We delivered the new feature three days ahead of schedule.
Customer satisfaction scores increased by 15% after our latest release
Successfully migrated the database with zero downtime
Unforced Errors

What mistakes did we make?

We didn't properly test the mobile version before deployment
Communication breakdown led to duplicate work on the same feature
Missed including key stakeholders in important decisions
Deuce

What things could go either way?

Should we prioritize new features or technical debt reduction?
The impact of switching to a new technology stack isn't clear yet
We're unsure if our current approach will scale with user growth
Wild Cards

What unknowns did we encounter?

Sudden change in project requirements from the client
Unexpected system dependency issues emerged mid-sprint
A key team member had to take emergency leave

What is the Tennis Retrospective?

The Tennis Retrospective reviews your last sprint or project the way a player reviews a match. Your team looks at the basics that held up, the winners it hit, the points it gave away, the calls that could still go either way and the surprises nobody saw coming. The board has five columns. Ground Strokes covers the foundational practices that kept you steady, like code reviews and stand-ups. Aces are the clear wins. Unforced Errors are the preventable mistakes, such as skipping a test or leaving someone out of a decision. Deuce holds the open questions where the team is split or unsure, like refactor versus rebuild. Wild Cards are the unexpected events, from a sudden change in requirements to a competitor's launch. The Deuce column is the unusual one. Most formats only look at what already happened; Deuce gives the team a place to air decisions it hasn't made yet. Use the format after a release or milestone, or when your regular retro has gone stale and the team would enjoy a sporting frame.

Tennis Retrospective format

Ground Strokes

What set us up for success?

Ground strokes are the basic practices the team relies on, like a player's forehand and backhand. Ask which everyday habits kept performance steady this sprint.

Aces

What great wins did we deliver?

Aces are the team's clearest wins. Ask for the moments where the team delivered outstanding results with an immediate payoff.

Unforced Errors

What mistakes did we make?

Unforced errors are mistakes the team could have avoided. Talk about them without blame, and ask what would prevent each one next time.

Deuce

What things could go either way?

At deuce, the point could go either way. This column is for decisions or situations where the team is unsure or split. Talk through the options and agree who decides, or what you'd need to know to decide.

Wild Cards

What unknowns did we encounter?

Wild cards are the surprises, good and bad, that turned up during the work. Ask how the team handled each one and what it would do differently if something similar happened again.

When to use this retrospective

  • When your regular retrospective has gone stale and the team needs a different format
  • After a major milestone or release, when there's a lot to review
  • When you want successes and mistakes to get equal time
  • When the team has open decisions it keeps putting off and needs a place to air them

Suggested icebreaker questions

  • If your last sprint was a tennis match, what would the score be and why?
  • Which tennis player's qualities (persistence, precision, adaptability) best describe your team's current strengths?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Use tennis language throughout the session to keep the theme going
  • Ask people to think about individual and team performance, the way tennis has singles and doubles
  • Encourage a rally: let people build on each other's ideas before moving on
  • Set a match length for each column so all five get time
  • Try tennis scoring (15, 30, 40) to rank action items
  • Keep Unforced Errors blame-free so people own up to mistakes

Frequently asked questions

What is a tennis retrospective?
It's a retrospective that uses tennis terms as prompts: Ground Strokes (what set you up for success), Aces (wins), Unforced Errors (mistakes), Deuce (things that could go either way) and Wild Cards (surprises).
When should we use the tennis retrospective template?
Use it when your team wants a lighter, sports-themed way to review a sprint or project, especially after a release when there are wins, mistakes and open questions to cover.
How long does a tennis retrospective take?
With five columns, plan for 60 to 75 minutes. If you're short on time, combine Deuce and Wild Cards into one discussion.
What's the difference between Deuce and Wild Cards?
Deuce is for open decisions the team hasn't settled, like whether to refactor or rebuild. Wild Cards are things that happened to the team unexpectedly, like a requirement change or a key person on leave.

Related templates

WWE Smackdown Showdown Retrospective

Tag-team your sprint review with a wrestling theme.

Working, Not Working Retrospective

Sort what's working from what isn't, then fix it.

Quarterly Retrospective

Step back from the sprints and review the whole quarter.

Baby Steps Retrospective

Pick one small change your team will actually finish.

Ready to run this retrospective?Try this retrospective live