I have yet to regret a purchase from the Pragmatic Bookshelf. The books are clear and concise with pretty easy to implement action plans, and this one is no exception.

If you are like me, you have found that traditional "lessons learned" meetings after projects were held rarely, and a rarer number of these actually generated anything of any impact on future work. In some of my readings about Agile Software Development, I read that Agile Teams have retrospectives regularly with each iteration. I thought this was interesting, but didn't really know what to do. Enter this book.

The authors do a great job of outlining how the process should work and why each of the phases of are important. The give good coverage of

* Setting the Stage

* Gathering Information

* Generating Insights

* Deciding What to Do

* Closing the Retrospective

Not only do they explain the general process, but they give a fairly extensive list of activities to use for each phase with suggestions about which ones work in different situations. After reading this book, I was able to immediately turn around and facilitate a rertrospective for my team's latest project release.

This book is about all that you could ask for. The material is rich, but the amount of material is fairly short and quick to read. It is very focused and clear on how to take action. I would recommend investing in this book to anyone who wants to do a better job of *truly* learning from past project experience.

This book has a lot activities to manage a retrospective meeting in software development, but I think some of techniques are not only effective in agile projects, you can use some of them in team management to give and receive feedback. Sadly the book has few examples about retrospective meetings and I expected to know more about how to manage different situations than what activities I should use.

Have zombies taken over your retrospective? Maybe the Sprint teams seems more like hungry mastiffs that won’t stop barking? Perhaps you are wondering if ESVP is a misspelling of ESP? If you have answered yes to the above questions, this is the retrospective book for you!

I’m a Scrum Master. I have encountered all sorts of outcomes, outbursts and out-of-this-world scenarios in retrospectives. This book was a lifesaver when I needed more ideas how to engage my Sprint teams. Every chapter has a take away. For example, in the very first chapter, a retrospective is described, start to finish, with activities included, and closes with a make-believe but real-world outcome. The authors offer a prescribed structured format that keeps people engaged, focused and ontrack.

The chapter on “Setting the stage” is a great kick-off to a retrospective that keeps your Sprint team members from turning into the undead. The game “ESVP” is when the team members say whether they are “Explorers”, “Shoppers”, “Vacationers” or “Prisoners.” It can be really telling where the Sprint team is based on their answers.

The book also gives advice on dealing with dominating people and toxic people. Ever have someone just start barking at people in a retrospective? I have copied the authors’ exact phrasing when speaking to someone who will not lower their voice. There are more great “go-to-phrases” when you are at a loss for words or don’t know how to respond to an unfamiliar situation.

The only thing I would add to this book is a chapter on dealing with remote teams. How do you keep people awake with the sound of your voice when they are an ocean away? Use real-time tools like google draw/google forms to re-create these games. It’s not rocket science to build a fishbone diagram online. I have discovered that any interaction with remote tools, even just voting “thumbs up”, makes a huge difference in the engagement of a remote team. And, can keep team members from impersonating the walking dead.

This book is a must have for any Scrum Master or Aglie coach. It is a valuable resource that you can draw from while preparing the best retrospectives

This book is one that is recommended by the Project Management Institute (PMI) to read for understanding of agile software development and to prepare for the PMI Agile Project Manager certification. It provides valuable information to guide agile team retrospectives. While not every technique may apply to every development team, some can and will. Good reference source.

Forget about this book if you wan't to learn theoretical stuff. There is some tiny theory in it, of course, but most of it is a pure practical guide for you to lead better retrospectives.

As a practical guide it is a must-read. At the beginning the authors lay the foundation of what they believe makes great retrospectives. The they tell us about each different phase of a retrospective. Finally, there is an impressive list of activities, for each stage of the retrospective. Each activity in this list is very well described: its purpose, time needed, a brief description, a step-by-step guide for the leader, and a list of materials needed.

Bottom line: if your leading agile retrospectives, you really should take a look at this book.

The book was as advertised. Very Good.

After the first 100 pages, I was ready to give this book a single star. Then it made its way back by producing some stimulus in the center of the book, basically talking about some techniques for eliciting and then analyzing feedback (made it back to a 4, 5 is ludicrous just from the content perspective, this thing is thin in every sense of the word). But then, it fell back to a 3 because ultimately the many examples are laid out as if they were patterns, but there is little to no structure. Finally, the conclusion section goes back to some of the silliness of the beginning. What I am referring to as silliness is the constant enveloping of process suggestions with new agey psychobabble. I found that 80% of the time, this additional stuff was noise.

Ultimately, I was left convinced (as probably all who have done iterative could easily be) that retrospectives are a good thing, but a strong conviction that they could be done better than what is being espoused here. There are a few good ideas, and the overall presentation is good. That's all.

It was a gif for a friend of mine. I readed this book a few years ago and I think it's one of the referral book you must read and understand to improve your retrospectives.

Just finished reading the book to the end. The writers have provided a lot of examples how Agile Retrospectives could and should be done. She also gives bulleted points so that it would be easy to navigate to the page when it will be implemented. I had been looking for this book since a long time.

I liked the simple layout of the book and it articulated with examples where appropriate. It’s a good starting point, but not an exhaustive one.

This is my go to reference book for facilitating retrospectives. So many great retro activities to choose from for getting to the bottom of things and figuring out what to do next.

As a Scrum Trainer and Contract Scrum Master, I regularly look for new ways to enliven Scrum Retrospectives. This book is my start point. It not only contains some fantastic ideas, it sets my mind free to think of alternatives that I can use.

Keeping Sprint Retrospectives engaging and useful is pivotal to helping a Scrum Team to continuously improve. This book will help you do that.