Throughout my agile journey I’ve experienced and facilitated many retrospective meetings for agile teams but also for long running projects. Often I’ve experienced that teams and sometimes even facilitators are not familiar with common basic structure of activities that an agile retrospective meeting should follow in order to make the meeting go smoothly and to generate qualitative action items for improvement. From my experience it helps teams a lot to when retrospectives are created along this structure of activities. The structure is published in the book Agile Retrospectives: Making Good Teams Great by Esther Derby and Diana Larsen, which I strongly recommend for anyone who is new to the subject.

Recently I’ve written a post about The Ball Point Game and about variations of the game, a game that simulates Scrum with all the sprint ceremonies, such as planning, sprint, review and retrospective. This post emphasizes the learning from a Scrum Master perspective.

Recently I’ve written a post about The Ball Point Game, a game that simulates Scrum with all the sprint ceremonies, such as planning, sprint, review and retrospective. Here is an addition to that post which offers interesting variations to the game.

When coaching scrum teams it is alway a good idea to combine theoretical teachings with some exercises that simulate what you’re teaching in a short time. When thinking of which exercises I could use to simulated the methodology, “The Ball Point Game” I’ve done in a training class by Boris Gloger many years ago came to my mind. The game had a prompt impact on me in regards of Scrum. The game simulates all the sprint ceremonies, such as planning, sprint, review and retrospective.

Edward De Bono’s Six Thinking Hats is a method that helps to reduce meeting times and make meetings more effective. The method is nowadays widely spread since it is simple, robust and effective. With this post I want to introduce the method briefly and also tell you about some experiences I’ve made using it.