Agile Thanksgiving Retrospective

Thank your teammates and decide what to carry forward.

Try this retrospective live

Grateful For

Who or what are you most thankful for this sprint?

I'm grateful for Maria jumping in to pair with me when I was stuck on the auth bug.
Thankful the whole team stayed calm during the release crunch: no panic, just teamwork.
Really appreciate our PO shielding us from scope creep this sprint.
What Nourished Us

What practices or wins fed the team and kept us strong?

Our daily standups stayed short and focused, and they actually helped.
Shipping the new dashboard on time gave us all a real morale boost.
The mid-sprint check-in helped us course correct early.
Leftovers to Reheat

What unfinished items should we carry into next time?

We never finished documenting the new API, so let's prioritize it next sprint.
That refactor we keep pushing back still needs doing.
The onboarding guide is half-written; worth completing.
Room for Seconds

What would you like more of going forward?

More dedicated focus time without meeting interruptions.
I'd love more cross-team knowledge sharing sessions.
More celebrating of small wins, not just big launches.

What is the Agile Thanksgiving Retrospective?

Thanksgiving is a natural time to stop and thank the people you work with. The Agile Thanksgiving Retrospective builds that into a retro: your team looks back on the work you've shared, thanks the people behind it, and still comes away with a few things to change. It makes a change from the standard sprint retro without losing the follow-through. The board has four holiday-themed columns. Grateful For is where people thank specific teammates and moments. What Nourished Us covers the habits, tools and wins that kept the team going. Leftovers to Reheat collects unfinished work and ideas that didn't get attention, and Room for Seconds asks what people want more of next time. The first two show you what to protect, and the last two give you something to act on. Thanks said out loud, with names and specifics, does more for morale and trust than a generic thank-you at the end of a meeting. Run it in the lead-up to Thanksgiving, at the end of a long sprint or as a year-end wrap-up, and close by turning the leftovers and seconds into actions with owners.

Agile Thanksgiving retrospective format

Grateful For

Who or what are you most thankful for this sprint?

This is the heart of the session. Ask people to name specific teammates, moments or outcomes they're thankful for. Thanks said out loud, with detail, builds trust, so invite everyone to be generous and specific.

What Nourished Us

What practices or wins fed the team and kept us strong?

Like a good Thanksgiving meal, ask what kept the team going this period: the habits, tools and wins that gave people energy. These are the things that deserve a regular place at the table.

Leftovers to Reheat

What unfinished items should we carry into next time?

Every Thanksgiving leaves leftovers. Use this column for unfinished work, lingering tech debt or good ideas that got dropped. Write them down so nothing worth keeping gets thrown out before the next sprint.

Room for Seconds

What would you like more of going forward?

Close on what people would happily go back for, like more pairing or more focus time. Turn the most popular wishes into actions the team can commit to.

When to use this retrospective

  • Around Thanksgiving, or in a November sprint, when you want the retro to match the season.
  • At the end of a year or quarter, to look back on what the team achieved and thank the people who made it happen.
  • When morale is low and the team would benefit from hearing specific thanks from each other.
  • After an intense sprint or major release, when the team deserves a pause to acknowledge the effort.

Suggested icebreaker questions

  • If your sprint were a Thanksgiving dish, what would it be and why?
  • What's one thing (work or non-work) you're especially thankful for this year?

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

Ideas and tips for your retrospective meeting

  • Set a warm tone at the start: no thanks is too small to share.
  • Go around the team so quieter members get a chance to thank someone too.
  • Don't let the theme stop you from capturing real improvements. Leftovers to Reheat and Room for Seconds are where they come from.
  • Ask for specific, sincere thanks over blanket ones, and don't make recognition feel compulsory.
  • Turn Leftovers to Reheat and Room for Seconds items into action items with owners so they don't get forgotten.
  • A seasonal touch like a virtual gratitude wall is fine, but keep the session timeboxed.

Frequently asked questions

What is an Agile Thanksgiving Retrospective?
It's a Thanksgiving-themed retrospective in four columns: Grateful For, What Nourished Us, Leftovers to Reheat and Room for Seconds. Your team thanks each other, looks at what kept it going and picks a few things to carry forward.
When should I run an Agile Thanksgiving Retrospective?
During Thanksgiving week, at the end of a November sprint, or as a year-end wrap-up when you want to celebrate what the team achieved.
How long does an Agile Thanksgiving Retrospective take?
Most sessions take 45–60 minutes, depending on team size. That's enough time to share thanks, discuss the themes and agree on a few actions.
How is it different from a standard sprint retrospective?
It covers strengths and improvements like any retro, but it starts with appreciation, so the tone is lighter and the recognition is more specific.
Does a fun, themed retrospective still produce useful outcomes?
Yes. People tend to speak up more when the mood is warm, and the Leftovers to Reheat and Room for Seconds columns give you concrete actions to take away.

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