How do you fit retrospectives into Kanban projects

[Gemma Wooden]

The company I have just started working for has decided that they want to move away from using Scrum to using Kanban to run their software projects.

Although I can definitely see the benefits of Kanban in their situation, I'm very keen to make sure my team carries on running retrospectives to ensure continued improvement, and to improve team moral.

Has anyone found a good way of fitting in retrospectives in Kanban projects?

[Nic Brough _Adaptavist_]

The most effective method I saw was that the team created a "story" which named a release.  That story could only be dealt with by getting the team together, having a retrospective to look at all the issues in the "done" column, and at the end of that meeting, clicking "release"