Kudos Retrospective
A retrospective that opens with gratitude before getting down to business. Kudos lets the team recognize each other first, then it reviews what went well, what to improve and the action items to follow up on. Starting with appreciation sets a positive, psychologically safe tone for the harder parts of the conversation.
Thank a specific person for something specific
Roman
Kudos to Ana for taking the 3am page and writing it up
Maria
Kudos to the design pair who unblocked the checkout flow
What worked and should be protected next sprint
Anna
Zero rollbacks this sprint
Daria
The new hire shipped to production in week one
Where the team lost time or quality
Maria
Tickets sat in review for two days on average
Kirill
Sprint goal changed twice after planning
Steps with an owner, taken out of the column above
Daria
Review SLA: pick up any open PR within 4 hours — whole team
Roman
Scope changes go to the next sprint unless it is an incident
Introduction:
This retrospective technique is a variation of the basic retrospective template that adds an extra column for the team to create Kudo Cards. The Kudo Cards serve as a way to give recognition to a team member for something they have contributed to the team.
Template:
- Kudos: In this column, team members can write down the name of a colleague they would like to recognize and the reason for their recognition.
- Went well: In this column, team members can reflect on what went well during the iteration phase.
- To improve: In this column, team members can identify areas where they believe the team can improve.
- Action items: In this column, team members can list action items that they believe will help improve the team's performance.
Benefits:
- Encourages team members to recognize each other's contributions
- Improves team morale and motivation
- Provides a positive focus for the retrospective
Usage:
This template can be used in any team that wants to incorporate recognition and appreciation into their retrospectives. The team can write their Kudo Cards on sticky notes and place them on a board or wall. The team can then discuss the Went well, To improve, and Action items columns as part of their retrospective.
Similar templates
Other formats teams pair with this one — open any of them as a board in one click.
Pros and Cons
The simplest possible way to weigh a decision, a change or the sprint as a whole. The team lists the pros on one side and the cons on the other, making trade-offs visible at a glance. Its bare-bones structure makes it a versatile choice whenever a balanced view is needed quickly.
Sprint Diagnostics
A diagnostic format that combines a quick rating with focused discussion. The team scores the sprint on dimensions like communication, collaboration, quality and pressure, then names a standout like or dislike and what could be done differently before agreeing on actions. The numbers give an easy way to track how the team's health changes over time.
3 L's
A lightweight three-column retrospective for teams that want quick, honest feedback. Participants capture what they liked, what they learned and what they lacked during the sprint. Stripped down to the essentials, it's an easy starting point for teams new to retrospectives or short on time.
DAKI
DAKI gives the team four clear levers for change in a single view. Participants decide what to drop because it no longer helps, what to add that's missing, what to keep that works well and what to improve. The crisp structure makes it easy to leave the session with a concrete, balanced set of adjustments.
SWOT Analysis
A strategic format borrowed from business analysis and adapted for team reflection. The team maps its strengths and weaknesses against external opportunities and threats to see the bigger picture. It works especially well for longer horizons — a quarter, a release or a project — where strategy matters as much as day-to-day fixes.
The Good - The Bad - The Ugly
A vivid three-part format that makes room for things the team can't simply fix. The good is what worked well, the bad is what went off plan, and the ugly is what lies outside the team's control but still deserves to be named out loud. That third column is what sets it apart, surfacing systemic issues that other formats tend to skip.
