Making retro work as a gif exercise is more than fun. It also gives you an idea of how the team feels after the retrospective. You can use this information to improve yourself next time. Some of the most useful charts for the retrospective meeting are those that show you how maps age on your map, cumulative flowcharts (CFDs), edge charts, blocker grouping diagrams, and cycle trends. 2. It promotes participationAfter the information provided by Marc Loeffler in his book Improving Agile Retrospectives, “someone who is silent at that time will probably stay that way for the rest of the retrospective.” 😶If you want more people to participate in the rest of the retrospective, now is your chance! Make sure everyone says at least one word at this point. Thanks to this approach, the most important story for each sprint is the highest priority element of the previous retrospective. It`s to encourage people to open up about what may have gone wrong during the sprint and to be open about how they felt and the problems that arose for them. This meeting can be emotional, and the intimacy of a private team environment provides a more bearable context. We agree on the cards to be put into operation during the week and synchronize their priority. If there is nothing unexpected, we stick to the plan.

Of course, over the course of life, we do not wait for the next meeting to deal with an emergency. Yet, at the next retrospective meeting, we will look at the damage done to our river. Starting the daily scrum by questioning the progress of retrospective action points is another way to keep the retrospective in the team`s mind.