Rugby Retrospective

Work your way up the pitch toward your team's goals.

Try this retrospective live

Halfway Line

What will help us start moving forward?

We need to establish clearer communication channels between dev and QA
Regular stand-ups would help keep everyone aligned
Creating a shared knowledge base could prevent repeated issues
10M line

What are the immediate challenges?

Technical debt is slowing down new feature development
We're spending too much time in meetings
Dependencies between teams are causing delays
22M line

What will help us accelerate?

Implementing automated testing would save time
A dedicated DevOps engineer could improve our pipeline
More pair programming sessions would spread knowledge
Try Line

What will help us reach our goal?

Building a scalable architecture for future growth
Achieving 99.9% uptime for all critical services
Implementing continuous deployment across all projects
Deadball line

What should we take out of play?

Unplanned urgent requests disrupting sprint work
Manual deployment processes prone to errors
Lengthy approval chains slowing down decisions

What is the Rugby Retrospective?

The Rugby Retrospective lays your team's reflection out on a rugby pitch. You start at the halfway line and work toward the try line, so the conversation moves from what will get the team going, through the challenges in front of it, to the long-term goals it's playing for. The board has five areas. The Halfway Line is for quick wins that build momentum. The 10M line covers the immediate obstacles, and the 22M line is for the processes and tools that would help the team go faster. The Try Line holds the long-term goals, and the Deadball line is for the practices and habits the team should take out of play. Because it covers today's blockers and next quarter's goals on one board, it suits quarterly planning as well as a regular sprint retro. Sports fans will pick up the metaphor straight away, and everyone else only needs to know that the try line is where you score.

Rugby Retrospective format

Halfway Line

What will help us start moving forward?

The halfway line is where improvement starts. Ask the team for quick wins it could pick up straight away to build momentum.

10M line

What are the immediate challenges?

Name the obstacles slowing the team down right now. Keep them specific enough that the team could act on them.

22M line

What will help us accelerate?

This zone is about going faster. Ask which processes, tools or practices would speed up delivery once the immediate blockers are out of the way.

Try Line

What will help us reach our goal?

The try line is where the team scores. Talk about long-term goals and what the team would need to reach each one.

Deadball line

What should we take out of play?

In rugby, the ball is out of play once it crosses the deadball line. Use this area for the practices and habits the team should stop or change, and ask people to be honest about what isn't working.

When to use this retrospective

  • When your team enjoys sports metaphors and a change of format would lift the energy
  • When you need to balance immediate challenges with long-term goals
  • During quarterly planning, to map improvements from quick wins to bigger goals

Suggested icebreaker questions

  • If your team were a rugby team, what position would you play and why?
  • What's your most memorable sporting moment that taught you about teamwork?

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

Ideas and tips for your retrospective meeting

  • Show the rugby field so everyone can see how each area moves the team toward the try line
  • Ask for short-term fixes and long-term improvements, so the board covers both
  • Use rugby terms during the session to keep the metaphor alive
  • Set a timer for each position to keep the session moving
  • Finish with a game plan: specific actions, each with an owner

Frequently asked questions

What is a Rugby retrospective?
It's a sports-themed retrospective that lays your team's reflection out on a rugby pitch. The team moves from quick wins at the halfway line, through immediate challenges and ways to go faster, to long-term goals at the try line, then decides what to take out of play.
How do you run a Rugby retrospective?
Introduce the pitch, then give everyone a few minutes to add ideas to each of the five areas on their own. Timebox each position, vote on the items that matter most, and finish with a game plan of actions and owners.
When should you run a Rugby retrospective?
Use it when you want to weigh this sprint's blockers against longer-term goals, during quarterly planning, or with a team that likes sports metaphors.
Do you need to know rugby to take part?
No. The only thing to know is that the team moves toward the try line to score. Each area has a plain question, so people who've never watched a match can still join in.
How long does a Rugby retrospective take?
Plan for about an hour. With five areas, give each around 8 minutes so there's time left to agree on actions.

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