Hi guys, this blog is part of our book: “Getting Value out of Agile Retrospectives”, a book written by Ben Linders and me with the foreword from Esther Derby. The book can be downloaded by free in LeanPub.comor, please download it and spread it within your colleagues.

Like Rachel Davies and Liz Sedley refers in their book: “Agile Coaching”, retrospectives provide a way to engage with team members in improving their processes in direct response to problems they face. Unfortunately, it is not uncommon to meet teams that have already tried retrospectivesand have given up. So where is the problem? To run successful retrospectives, there are several items that need to be present, and this is the topic we want to tackle.

Norman L. Kerth refers in his book: “Project Retrospectives” five important ideas to have a successful retrospective: “The need for the ritual”, “Naming the process”, “Prime directive for a retrospective”, “The darker side of the retrospectives” and the “Retrospective Facilitator.

The need for ritual

Usually, humans do not stop to reflect on any project; this is not a natural activity, that’s why it´s so important to formalise a behaviour and make it a ritual. Rituals are important because they serve to bring people together, allowing them to focus on what is important and to acknowledge on significant events or accomplishments. It is extremely important to not use a retrospective to identify only negative parts of a project. In each project there are positive outcomes and these should be celebrated like any other small victory.

If you want to continue you can see the rest of the article on my blog:

My name is Luis Gonçalves and I am an Organisational Transformation Coachand I love to write about Agile Retrospectives, Agile Retrospectives Ideas, Scrum, the role Scrum Master, and Agile in general.

I have been creating Scrum Master Training for the agile community. If you are interested in knowing more or even working with me you can find me here: Agile Coach München.