- ๐ Year in Review
- ๐ Achievements
- ๐ Lessons Learned
- ๐ฏ Goals for Next Year
- ๐ Gratitude
What is an end of year retrospective?
As another year draws to a close, it's time to step back and reflect on the bigger picture. The end of year retrospective shifts the lens from sprint-level improvements to annual patterns. It helps teams recognise achievements that might have been forgotten in the daily grind, learn from recurring challenges and align on priorities for the year ahead.
This format trades the tactical focus of sprint retrospectives for strategic reflection across 12 months. It's about connecting the dots, celebrating resilience through change and setting intentional direction for the new year.
When should you run an end of year retro?
Use this format in late December or early January, when teams naturally pause to reflect. It's particularly effective for teams that have delivered major projects, been through significant changes, or simply want to acknowledge their journey before planning ahead. This format complements your regular sprint retrospectives rather than replacing them; it works at a different altitude.
Want something lighter for the last sprint before the holidays? The Christmas retrospective is a festive alternative, and you can save this format for the first week of January.
How do you prepare for an end of year retrospective?
Block 90 to 120 minutes for this retrospective. The longer session is necessary because you're reflecting on a year, not a sprint. Send prep work ahead: ask team members to review their calendars, notes and key accomplishments from the past 12 months.
Consider gathering supporting data beforehand: quarterly goals, project timelines, team composition changes and key metrics. These memory joggers help ground abstract reflections in concrete events and prevent recency bias, where only the last few weeks get discussed.
How do you run an end of year retrospective?
A 90-minute agenda for a team of 5 to 15:
- Warm up (10 minutes). Set the mood with our icebreaker feature and play some music while the team gathers their thoughts. Then ask everyone to share a GIF that captures their year. It breaks the ice, surfaces different perspectives and often sparks laughter before the deeper reflection.
- Year in review (15 minutes). Build a shared picture of what happened before anyone judges it.
- Achievements (15 minutes). Celebrate what went well.
- Lessons learned (20 minutes). Look for patterns, not one-off problems. Keep cards anonymous during brainstorming so people feel safe being honest.
- Goal for next year (15 minutes). Vote on the ideas and agree one goal with an owner.
- Gratitude (15 minutes). End by sharing thanks out loud.
What goes in each column?
๐ Year in review
Major projects, changes and milestones
Start with facts before feelings. This column captures the objective events of the year: what shipped, who joined or left, what changed in the organisation and what external factors affected the team. Think of it as establishing a shared understanding of "what actually happened" before evaluating it.
Useful prompts: What were our major deliverables? How did team composition change? What technologies did we adopt? What metrics moved significantly? What external forces shaped our work?
This section prevents selective memory and ensures everyone's working from the same factual baseline.
๐ Achievements
What wins should we celebrate?
Here's where the team acknowledges what went well, without false modesty. This isn't just about shipped features; it includes improved practices, better team dynamics, professional growth and moments of breakthrough thinking.
Encourage specificity: not just "we delivered the project" but "we delivered despite changing requirements three times, and actually improved team morale in the process." Ask: What achievement exceeded our expectations? What challenge did we overcome that initially seemed impossible? What positive impact did we have on users or the organisation?
Many teams undervalue this column. Don't. Shared celebration strengthens team identity and reinforces the behaviours you want to continue.
๐ Lessons learned
What challenges taught us valuable lessons?
The counterbalance to achievements: what didn't go as planned, and more importantly, what did we learn? Frame this constructively. It's not about blame but about getting value from difficulty.
Useful angles: What assumption proved wrong? What challenge kept recurring? What trade-off do we now question? If we could advise our January selves, what would we say? What risk did we take, and what was the outcome?
Look for patterns across the year. A single missed deadline is tactical; missing deadlines consistently signals something systemic worth addressing.
๐ฏ Goals for next year
What's the one goal that would make the biggest difference?
Bridge reflection into action. Based on the year's lessons, what's the single most important goal the team should pursue next year? Not a long list. One focused commitment that would meaningfully improve how you work or what you deliver.
This could be a skill to develop, a process to improve, a relationship to build or a practice to establish. The key is focus: one goal the entire team can rally behind and support each other in achieving.
Useful prompts: If we could only improve one thing next year, what would it be? What capability would make the biggest difference? What change would reduce the most frustration? What would make us proud to look back on next December?
Assign an owner and set quarterly check-ins. One goal with real commitment beats five goals that fade by February.
๐ Gratitude
Who made our year better?
End on appreciation. This column acknowledges specific contributions that made the year successful: the colleague who mentored you, the teammate who stayed late, the person who brought some humour during a stressful week.
The key is specificity. Concrete appreciation resonates more deeply and reinforces the behaviours you value. Focus on what someone did and the impact it had.
Go around the room if needed to make sure everyone receives recognition. The ritual of public appreciation strengthens team bonds and is often the most memorable part of the retrospective.
End of year retrospective examples
A few cards to get your team started:
- ๐ Year in review: We moved from monthly to weekly releases in March.
- ๐ Year in review: Two people joined and one moved to another team.
- ๐ Achievements: We launched the mobile checkout and cut support tickets by a third.
- ๐ Lessons learned: Every big project slipped when we skipped the discovery phase.
- ๐ฏ Goals for next year: Get the test suite running in under ten minutes.
- ๐ Gratitude: Thanks to the whole team for covering on-call during the summer.
What should you do after the retrospective?
Share the summary. At the end of the retro, review the summary on screen with your team to make sure everyone's aligned on what was discussed and agreed. Then share it by email so everyone has a record to revisit. You can also download the summary image and share it in Slack or Teams. A visual recap helps the wider organisation see your team's journey and commitments.
Create accountability. For next year's goal, assign an owner and schedule quarterly check-ins. Put a reminder in your calendar for mid-year (June) to review progress and change course if needed. In between, Pulse Surveys help you track how the team is feeling.
Celebrate. Consider ending with a team meal, virtual celebration or shared activity. The retrospective itself is work; the celebration is the reward.
Related formats
- Christmas retrospective: a festive Naughty and Nice retro for the last sprint of the year.
- Santa's Workshop: gifts, repairs and bright ideas for next year.
- New Year retrospective: set goals and leave old problems behind in January.
The end of year retrospective is your chance to pause, reflect on what shaped your year and set intentional direction for what's next. It's one of the most valuable meetings your team will have all year. Make it count.
Start an End of Year Retro View all retro templatesFrequently Asked Questions
What is an end of year retrospective?
An end of year retrospective is a longer retro where the team looks back over the whole year instead of a single sprint. It covers what happened, what the team achieved, what it learned, one goal for next year and thanks for the people who helped.
How long should an end of year retrospective be?
Block 90 to 120 minutes. You're reflecting on twelve months, not two weeks, so the team needs more time to remember, discuss and agree a goal. Add a short break in the middle if you're running it remotely.
When should you run an end of year retro?
Late December, before people leave for the holidays, or the first week of January while the year is still fresh. Avoid the very last day before a break, when energy and attendance are lowest.
What questions should you ask in an end of year retrospective?
Useful questions include:
- What were our biggest deliverables this year?
- What achievement exceeded our expectations?
- What challenge kept coming back?
- If we could improve one thing next year, what would it be?
- Who made our year better?
How is an end of year retro different from a sprint retrospective?
A sprint retro improves how the team works in the next two weeks. An end of year retro looks for patterns across the year, celebrates progress people have forgotten and sets one bigger goal. It complements your sprint retros rather than replacing them.
What are good alternatives to the end of year retrospective?
For a lighter, festive session try the Christmas retrospective or Santa's Workshop. To focus on goals in January, use the New Year retrospective.