All Aboard the Agile Express Retrospective

Find what drives your team and what's braking it.

Try this retrospective live

The Engine

What powered us forward this sprint?

Our daily standups were sharp and kept everyone aligned on priorities.
Pair programming on the payment module saved us hours of rework.
The product owner was super responsive, so we never got blocked on decisions.
The Brakes

What slowed us down or held us back?

Too many context switches between projects killed our focus.
We waited two days for environment access, which stalled testing.
Unclear acceptance criteria led to back-and-forth rework.
Obstacles on the Track

What risks or obstacles lie ahead of us?

The upcoming holiday period will reduce our available capacity.
We're dependent on the API team delivering before we can integrate.
Tech debt in the auth service could slow down the next feature.
Next Station

Where do we want to be by our next stop?

Set up a shared dashboard so blockers are visible to everyone.
Agree on definition of done before pulling stories into the sprint.
Reduce meeting load by trialing no-meeting Wednesdays.

What is the All Aboard the Agile Express retrospective?

All Aboard the Agile Express treats your sprint or project as a train ride. The metaphor gives the team a shared picture for the retro: an engine pulling you forward, brakes slowing you down, obstacles on the line ahead and a station you're heading for. With that picture in place, it's easier to say what's building momentum and what's dragging on it. The board has four columns. The Engine is for the practices and people that powered the team. The Brakes covers the friction and blockers that cost you speed. Obstacles on the Track looks ahead to risks and dependencies before they hit, and Next Station is where you agree on the actions to reach before the next retro. Because one column looks forward, the session covers what's coming as well as what already happened, which makes it a good fit for sprint ends, project milestones and quarterly check-ins. A themed retro like this is a good way to re-engage a team that's tired of the standard "what went well, what didn't" board. It gives a Scrum Master or agile coach a fresh way into the conversation, and the last column keeps everyone heading the same way.

All Aboard the Agile Express retrospective format

The Engine

What powered us forward this sprint?

The Engine is the practices and people that drove the team's progress. Ask what gave you momentum, whether that was strong collaboration, clear goals, a helpful tool or someone's individual effort. Celebrate what's worth keeping so the team keeps doing it.

The Brakes

What slowed us down or held us back?

The Brakes are the friction, blockers and drag that slowed the team. Keep it honest and blameless, focused on systems and processes rather than people. You can't remove a slowdown until someone names it.

Obstacles on the Track

What risks or obstacles lie ahead of us?

This column looks forward. Ask the team what might block progress in upcoming work, such as risks, dependencies or concerns. Raising them early gives you time to plan around them, so invite people to flag anything they can see coming, even if it's uncertain.

Next Station

Where do we want to be by our next stop?

Next Station is the destination: the goals and commitments the team wants to reach before the next retrospective. Turn the discussion into concrete actions with owners. Keep the list realistic so the train arrives on time instead of overloaded.

When to use this retrospective

  • When your team is tired of the standard retro format and needs a new way in.
  • At the end of a sprint or iteration, to see what's driving momentum and what's slowing you down.
  • At project milestones or quarterly check-ins, to agree on direction and upcoming risks.
  • When you want to celebrate wins and plan for risks in the same session.

Suggested icebreaker questions

  • If our team were a train, would we be a high-speed bullet train, a scenic steam engine, or a stuck-at-the-station local?
  • What's the best or most memorable train trip you've ever taken?

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

Ideas and tips for your retrospective meeting

  • Explain the train metaphor briefly before brainstorming so everyone knows what each part of the train stands for.
  • Give everyone quiet time to add ideas anonymously before discussion, so the first voice doesn't set the direction.
  • Keep The Brakes about systems and processes, not individuals.
  • Timebox each column to keep the train on schedule and reach Next Station with time for actions.
  • Group and vote on similar ideas so discussion goes to the themes that matter most.
  • Close by giving every action item an owner and a due date.

Frequently asked questions

How long does the All Aboard the Agile Express retrospective take?
Most sessions take 45–60 minutes for a team of five to eight. A bigger team or an eventful sprint may need a little longer, mostly for discussion and action planning.
When should I use this retrospective format?
At the end of a sprint, after a project milestone or for a quarterly review. It's most useful when your team needs a change from the standard retro format.
How is the Agile Express different from a Start, Stop, Continue retrospective?
Both cover what's working and what isn't. The Agile Express adds a forward look with Obstacles on the Track and Next Station, so you plan for risks ahead as well as reviewing the past.
Do I need agile experience to facilitate this retrospective?
No. The train metaphor is easy for any team to follow. Basic facilitation skills help you steer the discussion toward action items.
How many participants work best for this retrospective?
It works best with three to ten people. For larger groups, split into breakout rooms and bring the themes together afterward.

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