Kanban is a change management method and without reflecting how we work and
what we work on, change will be random, inexistent, or even towards worse.
But why teams forget to retrospect? Why do they postpone retrospectives? From consulting and coaching more than 20 teams, I discovered some patterns I want to share with the audience.
Here one example: Improvement task identified in the retrospective are put into the product backlog. There, they remain forever. What a frustration for the team: they identified an issue, found a solution, agreed on the importance but they don’t work immediately on it. Why then wasting time in retrospectives?
Talking to the teams, sometimes providing a refresh of some agile basics, most of the teams started thinking about how they want to reestablish a reflecting culture.
(Everyone is welcome to leave a comment on this submission! Click on headline to do so)