Dream Goals

What shared goals are we chasing together?

We were all crystal clear on the launch deadline and it kept us aligned the whole sprint.
I think a few of us had different ideas about what 'done' actually meant for this project.
Our shared goal of delighting the customer really helped us prioritize the right things.
Working Together

What helped us collaborate effectively as a team?

Pair programming on the tricky feature saved us hours of back-and-forth.
Our daily check-ins kept everyone in the loop without being a burden.
People jumped in to help without being asked when I was overloaded.
Out of Sync

Where did teamwork break down or cause friction?

Handoffs between dev and QA felt rushed and we missed a few things.
Some decisions were made in side conversations and the rest of us found out late.
We stepped on each other's work because ownership wasn't clear.
Make the Dream Work

What will we do to strengthen teamwork going forward?

Let's create a simple ownership map so we always know who's responsible for what.
We'll add a quick handoff checklist between dev and QA.
I'll start sharing decisions in the main channel so everyone stays informed.

What is the Team Work Makes the Dream Work retrospective

The Team Work Makes the Dream Work retrospective puts collaboration at the center. Instead of reviewing tasks and deliverables, your team looks at how it worked together: whether everyone was chasing the same goal, what made teamwork flow and where it broke down. The board has four columns. Dream Goals checks that everyone has the same picture of success, and surfaces it when they don't. Working Together is for the habits and moments that made collaboration easy, like people jumping in unasked or shared docs that smoothed a handoff. Out of Sync holds the friction: decisions made in side conversations, unclear ownership, rushed handoffs. Make the Dream Work turns all of that into two or three commitments. Most retros spend their time on the work itself, so problems in how people work together can go unmentioned for months. This format gives those problems a name and a column. Use it with a newly formed team finding its rhythm, with an established team that senses silos or friction, or after a big project to look at how the team held up.

Team Work Makes the Dream Work retrospective format

Dream Goals

What shared goals are we chasing together?

This column checks that the team is aiming at the same thing. Ask whether everyone has the same idea of what success looks like, and draw out any differences so the team can agree on one goal.

Working Together

What helped us collaborate effectively as a team?

Focus on the habits and practices that made teamwork flow. Ask for specific moments where collaboration, communication or support made a real difference, so the team knows what to keep doing.

Out of Sync

Where did teamwork break down or cause friction?

This is the place to raise friction honestly. Ask people to describe situations rather than name individuals, and treat each issue as a problem the whole team shares.

Make the Dream Work

What will we do to strengthen teamwork going forward?

Turn the discussion into commitments. Agree on a small number of concrete actions that will change how the team works together, give each an owner and check on them at the next retrospective.

When to use this retrospective

  • When a newly formed team is finding its rhythm and wants good collaboration habits from the start.
  • When an established team senses friction, silos or communication problems slowing it down.
  • After a major project or milestone, to look at how well the team worked together.
  • As a periodic team-building check-in on trust and shared goals.
  • When new members join and you want everyone to agree on how the team collaborates.

Suggested icebreaker questions

  • If our team were a sports team, what position would you play and why?
  • What's the best team you've ever been part of, and what made it work?

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

Ideas and tips for your retrospective meeting

  • Set a blame-free tone from the start so people feel safe being honest about teamwork.
  • Use anonymous brainstorming before grouping and voting, so quieter members contribute.
  • Talk about behaviors and situations rather than individuals when you discuss friction.
  • Limit actions to two or three commitments so the team can follow through.
  • Open by checking the previous retrospective's actions.
  • Call out good collaboration when you see it. Recognition gets you more of the behavior you want.

Frequently asked questions

How long does a Team Work Makes the Dream Work retrospective take?
Most teams finish in 45 to 60 minutes. Allow up to 90 minutes for a larger team or one with a lot to work through.
When should I use this retrospective instead of a standard sprint retrospective?
Use it when you want to focus on how your team collaborates rather than on what it delivered, for example after a major milestone, when new people join, or when you sense friction.
Who should facilitate this retrospective?
A Scrum Master, team lead or any neutral facilitator. Their job is to keep the discussion constructive, make sure everyone contributes and steer the team toward concrete actions.
How is this different from a team health check?
A health check scores the team against the same fixed areas each time, so you can track trends. This retrospective is an open discussion of recent teamwork that ends in actions.
How do we make sure the action items actually happen?
Agree on two or three specific actions, give each an owner, and review them at the start of your next retrospective.
Ready to run this retrospective?Try this retrospective live