Skip to Content

The Power of Retrospectives

Written by: Dewire Agile Methodology Team

October 12, 2016

One of the standard meetings in the agile world is the meeting called retrospective that should be held at the end of a sprint. Compared to the demo where the product or sprint increment is shown and talked about, the retrospective is where the process is discussed and talked about.

A company that invests time in having retrospectives is a company that not only puts effort into building the right product, they also put effort into building it the right way. A standard procedure for Retrospective can be found in the book ”Agile Retrospectives – Making Good Teams Great”.

It consists of a meeting framework that helps inspire creativity and productivity and offers a varied way of coming up with good suggestions and ideas to avoid repeating mistakes and keeping best practices.

In the picture you can see an example of a result from one retrospective, the ”Low Hanging Fruit Tree” where improvement actions are noted on a post it and then valued by the parameters ”easy to do” and ”value/effect of doing it”. The team should work their way through the tree from lower right corner to upper left corner if they want to do the improvement action in the prioritized order.