KALM Sprint Retrospective Format
As calming as it sounds, the KALM retrospective does what it says on the tin: keeps you and your fellow retro-mates calm, while helping to move along the business at hand.
Here’s GoRetro’s all-in guide to keeping your sprint retrospectives calm and flowing with the KALM retro!
What is the KALM sprint retrospective?
This sprint retrospective is one to facilitate conversations among team members about the current activities being used and what their value is.
The KALM , very much like the starfish retrospective, can be done in a number of ways, but a great way is by dividing a whiteboard into different sections: Keep, Add, Less, and More, giving each team member a stack of sticky notes to write down ideas they have for each category.
The categories include:
● Keep: Things that the team recognizes as having value and adding to their process.
● Add: These are ideas that the team comes up with that can help the team accomplish their goals and get to where they want/need to be.
● Less: The team writes out things that are being done that hold value but could possibly be done less. Perhaps things that hold value in one area but hold the team back in others.
● More: These are things that the team is already doing that could be done more often. Perhaps actions that are helping the team get where they need to be and can be incorporated in other areas of their work.
How to Keep a KALM Retro (and Carry On!)
The easiest way to run a KALM retro is to -
- Divide your board into the four areas listed above.
- Give your retro-mates a stack of post-its, and get them to write down their thoughts across each category (Keep, Add, Less, More)
- Get participants to add their post-its to the right section of the board.
- Discuss away! You may even notice that some of the notes’ subjects keep repeating themselves...and if so, we suggest you start with these topics first, as they're clearly the hottest! Other post-its and issues can be discussed via vote if there are too many to get through.
The Benefits of the KALM Retro
Not only do you get to ‘keep calm and carry on’ with this style of retrospective, but it's also a great way of getting those more hesitant team members to come out of their shells and open up (see also: Icebreaker Questions to Really Get Your Dev Team Talking).
- It's interactive. While some sprint retrospective formats seem to be inviting team members to share their thoughts, more rigid forms of sprints can be pretty top-heavy...which is never a good thing. See also: Your Ultimate Guide to Fun Retrospective Ideas
- It's value-based. Rather than trying to point blame at certain team mates, or encouraging a blame-heavy/uncomfortable environment, the KALM retro makes everything about the world, and the elements that bring value (or not). See also: How to Run a (Truly) Blameless Sprint Retrospective.
- It's polite, and promotes dialogue. It puts your teammates in the driver’s seat, allowing them a sense of agency and ownership.
Quick Tips for Running a KALM Retro
Here are a few quick tips to get your KALM Retro off to a calm start!
- Sense a high-stress sprint? The KALM retro is a perfect (and calming) solution, equalizing parties and balancing workloads for all stakeholders.
- Set specific boundaries or rules for what is to be discussed.
- Keep things anonymous to keep everyone feeling safe and engaged.
- Follow-up. It's great to talk about things, but actually executing them will do wonders for your sprint, and team’s morale!
Keep Calm (and KALM) with GoRetro
Or, you can quickly and easily run your entire sprint with GoRetro.
This forever-free sprint retrospective tool helps to keep your retros productive, engaged, and blame-free, all while anticipating any future issues, and eliminating them entirely.
GoRetro is loved by masses of software devs worldwide, including those from the likes of Netflix, Adobe, Lyft and more. We just know you're going to love it!
See for yourself. Start and continue for free right here, and enjoy a calmer, KALMer approach to your retros immediately!
When should the KALM agile retro be used?
This retrospective format can be used after a sprint, or just as a quarterly check-in to see how their goals are being worked towards and achieved.