Glossary
What is a retrospective?
A retrospective examines how the team worked, not what it produced. Format, purpose, and the condition without which it achieves nothing.
A retrospective is a regular meeting in which a team examines its own way of working — not the result, but the path to it. It typically sits at the end of a sprint and ends with one or two concrete changes.
Format
The common one: what went well, what went badly, what will we change. The last part matters more than the format. A retrospective without a decision is a discussion group — and after three of those nobody turns up.
The condition
Candour requires that none of it becomes an assessment of individuals. The moment someone expects consequences, the team stops naming problems and the retrospective becomes an obligation. That is why in many teams managers deliberately do not attend.
In Zuuna
Decisions get created as cards so they are visible in the next sprint — that is the difference between a retrospective and a chat.
FAQ
How often?
At the end of every sprint; in Kanban, on a fixed rhythm of roughly every two weeks. Less often than monthly and it loses touch with the work.
How many actions should come out?
One or two that actually happen. Ten actions are a wish list, not a change.