ππ§§ Year of the Horse Sprint
Gallop through our sprint like the spirited Year of the Horse, celebrating victories, confronting hurdles, and harnessing momentum for the next race.
Template Columns
ππ¨ Swift Successes
Highlight the fast wins and smooth strides our team made this sprint.
Base column: What Went Wellβ‘οΈ Stumbling Hooves
Identify the trips and obstacles that slowed our gallop.
Base column: What Went Wrongπ Harnessing Power
Plan how to channel our energy for stronger, steadier progress.
Base column: What We Want to ImproveAbout this template
A fastβpaced sprint retrospective that celebrates quick wins, surfaces obstacles, and channels the teamβs energy into actionable improvements.
When to use this template
Use when the team needs a highβenergy review that highlights rapid successes and quickly identifies blockers, especially after short sprints or timeβboxed work.
How to facilitate
Kick off by setting the theme β the Year of the Horse β and ask the team to think of sprint moments that felt fast and smooth.
In the Swift Successes column, have each participant write a short note about a win or smooth flow they observed, then place them on the virtual board.
Gather the notes, read them aloud, and briefly discuss why those successes happened, highlighting patterns.
Move to the Stumbling Hooves column, where everyone adds a brief description of a blockage or mistake that slowed the sprint.
Discuss each obstacle, focusing on root causes and whether they are repeatable, and capture key insights.
In the Harnessing Power column, collaboratively brainstorm concrete actions or experiments to turn strengths into repeatable practices and to remove or mitigate the identified obstacles, then assign owners and due dates.
Pro Tips
Use a timer for each column discussion to keep energy high and prevent overβanalysis.
Encourage the use of emojis or icons on sticky notes to visually differentiate wins from blockers.
After the session, create a oneβpage action board that stays visible in the team's channel for accountability.
FAQ
What if the team struggles to find fast wins?
Prompt them to consider any task completed ahead of schedule, a smooth handoff, or a bug fixed quickly; even small efficiencies count.
How do we prevent the discussion from turning into a blame session?
Focus language on the process, not the person, and frame each obstacle as a learning opportunity with a concrete improvement step.
Can this format work for longer releases?
Yes, you can treat each release as a sprint and adjust the timebox, or break the board into multiple phases to keep the pace lively.
Want a custom template?
Create a retrospective template tailored to your team's needs with our AI-powered generator
At a glance
- Duration
45β60 min
- Team Size
4-12 people
- Columns
3 columns
- Base Format
What Went Well, What Went Wrong, What We Want to Improve
Tags
Ready to get started?
Use this template to run your next retrospective