Agile To Go

A couple of simple check-in activities for retro Structure of retrospective How to run good retrospective? How to structure it in a good way? What to do to make people feeling that the time of retro session was spent in a good, productive way? And how to make changes, improvements from retrospective possible? There are many approaches to running retrospectives. There is certainly group of people who jump straight away to the main point - discuss last sprint, release, project, insights about it and proposed improvements. Others prefer to use more structured approach.  There are many structures which will work well. Majority of them has the following common points in agenda: Setting the stage   - introduction to retrospective, providing a context, setting up goal for session. In this part we often also review working agreements and prime directive for retro. It's important to take care of creating open and comfortable atmosphere for participants. This part also may cont

Retro for beginners with RetroKit! As you most probably noticed recently lots of my attention is focused on inventions created by colleagues from Spotify. I must say to on Spotify Labs you can find quite a lot of interesting ideas related to Agile or leadership. One of this very simple, yet very useful, ideas is RetroKit. Why RetroKit? I think we all agree that Retrospective is one of the most important ceremonies/events in Agile world. Retrospective supports inspect and adapt loop and facilitates continuous improvement. Unfortunately not everybody is lucky enough to either have instant access to Agile Coach or have necessary skills and experience to comfortably conduct retrospective by himself/herself. To help in such cases it's good to have tools helping teams becoming self sufficient. Colleagues from Spotify encountered this problem and came up with tool for teams to start running retrospectives on their own in energizing and easy way. This was the RetroKit was born.  W