Category: Books

When I wrote about Alexey Krivitsky’s book Agile Retrospective Kickstarter a month ago, I mentioned that much of his work is based on the work of Esther Derby and Diana Larsen (as he openly acknowledges in his book). At that time, I also promised to write separately about the book by these women facilitators. So here I am, fulfilling that promise.

I read the book in English, although in 2017, it was also published in Russian by Dmitry Lazarev Publishing under the title “Agile Retrospectives: Turning Good Teams into Great Teams.”

Why do teams need retrospectives? I’ve already written about this in detail elsewhere, but here’s a brief reminder: retrospectives help teams learn from their mistakes and grow. Without them, no Agile methodology can operate at full capacity.

Esther and Diana explain how to make such meetings as productive as possible, drawing from their many years of experience and unique insights. It is in this book that they propose the five-stage format for retrospective meetings, which Alexey Krivitsky actively adopts and promotes in his own book.

Lately, I have been actively rereading various books and articles about Agile, and sometimes even exploring new material. In my opinion, Agile methodologies offer a lot of valuable practices, but one of the most useful ones is retrospectives—meetings where the team can look back, reflect on what has been done, analyze their experiences, and choose a few experiments to improve how things are done.

When people implement different Agile methodologies, they often forget that flexibility is not just about introducing daily stand-ups and breaking tasks into short sprints. It is fundamentally about learning from experience, adapting, and evolving. Without retrospectives, this does not work. That is precisely why retrospectives are so important. However, even these meetings can either be conducted properly and effectively or simply for the sake of formality (“because it is required”). For this reason, retrospectives are sometimes the subject of not only individual articles but even entire books.

Agile Retrospectives Kickstarter is one such book. Although it was written by a Russian-speaking author, Alexey Krivitsky, it was originally written in English, with the Russian version created later with the help of his colleagues.

The book itself is relatively short, just over 50 pages. The author, a practicing Agile coach, shares his experience in conducting retrospectives. However, he does not do this by providing an extensive set of examples or academic knowledge. Instead, he has compiled experiences from many sources into a highly condensed “retrospective cheat sheet,” offering a collection of possible exercises for conducting effective retrospective meetings. Alexey candidly admits from the outset that he did not invent any of these exercises (or at least does not remember inventing any) and even borrowed the methodology for breaking a meeting into several stages from other coaches. His contribution was to compile all of this into one relatively short guide that can be kept handy and used whenever preparing for a retrospective.