Retrospectives
Put what you learned in the sprint on sticky notes and keep it as the team's knowledge. Pick the method that fits the team right now.
Does any of this sound familiar?
- It is KPT every time, and you keep landing on the same conclusion
- The same people speak every time
- It goes well in the room, but nothing is left in writing
- Facilitating is heavy work, so only a few people can do it
The actual screen
Five categories to choose from
No single format works for every team. Keep using one that does not fit and the retrospective turns into a ritual. Kizuna sorts methods by what they are for.
Issue finding
I want to find problemsBring problems and risks into the open and look for solutions
Action oriented
I want to drive improvementProduce concrete actions and keep improving
Communication
I want a better team atmosphereRaise psychological safety and strengthen relationships
Reflection
I want to sort out what happenedLook back at the facts and get on the same page
Learning
I want to deepen what we learnShare knowledge and support growth
What supports the facilitator
Every method comes with a running guide, so everyone can see which step you are on and what to do.
Tools for moving the session along are on screen too: a roulette and a draw for deciding who presents, and a hands game for splitting into groups.
How often you run them and how many sticky notes you write build up in the team report, and show up as badges.
How it goes
The host creates a session
The facilitator — often the scrum master — picks a retrospective method and gets a URL to share.
Share the URL with the team
Guests join without an account. They open the URL and pick a name and an icon.
Start once everyone is in
The host checks that everyone has arrived, then starts. The state is synced to every screen in real time.