Roller Coaster Retrospective

Ride back through the ups and downs of your sprint.

Try this retrospective live

Ups

What were the high points of our last sprint?

Successfully launched the new feature ahead of schedule
Our daily standups have become much more focused and efficient
Great collaboration with the design team on the user interface
Downs

What were the low points of our last sprint?

Technical debt slowed down our feature development
Communication breakdown with the client caused delays
Too many unplanned tasks disrupted our sprint flow
Loops

What surprised us?

The new framework was much easier to learn than we expected
Didn't anticipate how much users would love the beta feature
Security review took twice as long as planned
Again, Again

What do we want to continue doing?

Keep doing our weekly knowledge sharing sessions
Continue with the new code review process. It's working great
The daily quick wins celebration really lifts morale
Next Ride

What do we want to try next?

Let's try mob programming for complex features
Could we implement automated performance testing?
Want to experiment with trunk-based development

What is the Roller Coaster Retrospective?

The Roller Coaster Retrospective treats your last sprint like a ride: there were climbs, drops and a few loops nobody saw coming. Most sprints feel like that from the inside, so the metaphor gives people a simple way to talk about the highs and the lows in the same conversation. The board has five areas. Ups is for the high points and Downs for the low ones. Loops captures the surprises, good and bad. Again, Again is for the practices the team wants to keep, and Next Ride is for the experiments to try in the coming sprint. It works best after a sprint with clear highs and lows, or when the team is tired of the usual format. Talking about drops and loops makes hard topics feel less personal, and the last two areas make sure the session ends with something to keep and something to try.

Roller Coaster retrospective format

Ups

What were the high points of our last sprint?

Ask the team for the moments of success and the breakthroughs from the sprint. Push for specific examples over general statements. Naming the highs lifts morale and shows which practices are worth continuing.

Downs

What were the low points of our last sprint?

Make it safe to be honest about setbacks. Look for problems in the process, not people to blame, and ask each person to describe their low point in a way that suggests what might fix it.

Loops

What surprised us?

Ask for the events and realizations nobody expected, good and bad. Surprises often expose a blind spot in planning or an assumption that was wrong. Talk about how the team could see the next one coming.

Again, Again

What do we want to continue doing?

This area is for the practices that worked and should become part of how the team always works. Look for patterns in what's going well, and talk about what it would take to keep each one going after the novelty wears off.

Next Ride

What do we want to try next?

Ask for improvements and experiments to try next sprint. Help the team pick the most promising ones and turn them into specific actions with an owner, not vague intentions.

When to use this retrospective

  • When team morale needs a lift and you want to keep the energy up during the retro
  • After a sprint with clear highs and lows
  • When your team has meeting fatigue and the standard format has stopped getting people talking
  • For teams that like working through problems with a metaphor

Suggested icebreaker questions

  • What's your favorite amusement park ride and why?
  • If your last sprint was a roller coaster ride, what would you name it?

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

Ideas and tips for your retrospective meeting

  • Open by explaining how a roller coaster maps to a sprint: the climbs, the drops and the loops you didn't see coming
  • Use roller coaster sound effects or images to set the theme
  • Ask for specific moments, not general feelings
  • Timebox each topic to 5–7 minutes to keep the session moving
  • End with concrete improvement actions, each with an owner
  • For remote sessions, invite people to use a roller coaster virtual background

Frequently asked questions

What is a Roller Coaster retrospective?
It's a themed retrospective that treats a sprint like a ride. Your team sorts its experience into Ups, Downs and Loops (the surprises), then decides what to do again and what to try on the next ride.
How do you run a Roller Coaster retrospective?
Explain the metaphor, then give everyone a few minutes to add ideas privately to each of the five areas. Group and vote on them, give each area 5–7 minutes of discussion, and finish with a few actions from Next Ride.
When should you use a Roller Coaster retrospective?
Use it after a sprint with clear highs and lows, when morale needs a lift, or when your team is tired of its usual format.
How long does a Roller Coaster retrospective take?
Plan for 45 to 60 minutes. Five areas at 5–7 minutes each, plus time to add ideas, vote and agree on actions, fits in that window.
What are the stages of the Roller Coaster retrospective?
There are five: Ups for successes, Downs for setbacks, Loops for surprises, Again, Again for practices to keep, and Next Ride for experiments to try.

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