Agile Retrospectives: Making Good Teams Great and over one million other books are available for Amazon Kindle. Learn more
CDN$ 24.54
  • List Price: CDN$ 38.95
  • You Save: CDN$ 14.41 (37%)
FREE Shipping on orders over CDN$ 25.
In Stock.
Ships from and sold by
Gift-wrap available.
Add to Cart
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See all 2 images

Agile Retrospectives: Making Good Teams Great Paperback – Aug 5 2006

Amazon Price New from Used from
Kindle Edition
"Please retry"
"Please retry"
CDN$ 24.54
CDN$ 18.13 CDN$ 15.88

Join Amazon Student in Canada

Frequently Bought Together

Agile Retrospectives: Making Good Teams Great + Coaching Agile Teams: A Companion for ScrumMasters, Agile Coaches, and Project Managers in Transition + Agile Estimating and Planning
Price For All Three: CDN$ 91.93

Show availability and shipping details

Customers Who Bought This Item Also Bought


Product Details

  • Paperback: 200 pages
  • Publisher: Pragmatic Bookshelf; 1 edition (Aug. 5 2006)
  • Language: English
  • ISBN-10: 0977616649
  • ISBN-13: 978-0977616640
  • Product Dimensions: 23.4 x 18.8 x 1.3 cm
  • Shipping Weight: 422 g
  • Average Customer Review: 4.5 out of 5 stars  See all reviews (2 customer reviews)
  • Amazon Bestsellers Rank: #64,845 in Books (See Top 100 in Books)

Inside This Book (Learn More)
Browse Sample Pages
Front Cover | Table of Contents | Excerpt | Index
Search inside this book:

Customer Reviews

4.5 out of 5 stars
5 star
4 star
3 star
2 star
1 star
See both customer reviews
Share your thoughts with other customers

Most helpful customer reviews

2 of 2 people found the following review helpful By Gerard Meszaros on Aug. 6 2006
Format: Paperback
I have been facilitating project retrospectives since Norm Kerth's book "Project Retrospectives" first came out. I've applied many of those ideas to the bi-weekly retrospectives I've been facilitating for agile project teams over the last six years. The exercises in Norm Kerth's book are great but tend to be focused on the multi-day end-of-project retrospectives and are therefore too long for bi-weekly retrospectives. Esther and Diane's exercises are much shorter and many can fit into the 1 hour retrospectives that we tend to use on agile projects. Esther and Diane also provide a model for structuring the retrospective to get the maximum effect from the time invested as well as including some exercises to help the retrospective facilitator get feedback on their facilitation techniques. No agile retrospective facilitator should be without this book!
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again.
Format: Paperback
I recommend this book: be aware that it's CDN$ 19.75 and has 200 pages, so don't expect a dictionary.

In agile software development, you can have an ad hoc retrospection after an iteration, that's good.
The book gives you a good sense of what to think when preparing, leading and repeating retrospective meetings. That makes the purpose of retrospection to go beyond a simple "what went good; what went wrong" meeting.

The book does not guarantee you'll make the best retros in the world (after all, it's you that lead the meeting), but it's a really good start for thoughts on that subject.
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again.

Most Helpful Customer Reviews on (beta) 47 reviews
14 of 15 people found the following review helpful
Take your team to a new level with this book! Aug. 1 2006
By Lisa Crispin - Published on
Format: Paperback
My agile team has used retrospectives for years and thought we were pretty good at them. The activities and ideas in this well-written, well-organized book take our retrospectives to a whole new level. Now if we can't remember what we did in the previous two weeks (it's surprising how poor our memories can be!), or are stumped for ideas on how to address a prickly issue, we can just turn to the book for a way to jump-start a beneficial change.

I had no idea there were so many different approaches to getting value via retrospectives. The activities are all simple, and illustrated with many figures and examples. Even if you're not very experienced at leading these types of meetings, the book will give you confidence.

The authors also explain when and why to do different types of retrospectives. For example, I hadn't thought of having project retrospectives for our agile team, since we already have iteration retrospectives, but now I can see how they can be managed for good effect. Most importantly, the book explains how to use the information and ideas produced in a retrospective to effect real change. It's easy to get complacent and not strive to do better, and this book will help your team be proactive.

The book's organization makes it a good reference guide too. Anytime your team is in a rut or having a problem, you could pick an activity out of this book to kick start things. I love user-friendly books such as this one.
54 of 68 people found the following review helpful
Reality Check March 5 2007
By R. Williams - Published on
Format: Paperback Verified Purchase
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.
13 of 15 people found the following review helpful
It's not hype; their advice works. Sept. 18 2006
By Norman L. Kerth - Published on
Format: Paperback
Diana and Esther tell us how to make good teams great. It's not hype; their advice works!

From the first few pages we know the authors are speaking from their vast experience, sharing knowledge on how to install iterative retrospectives in a team's process. Their book is written in an easy-to-read manner and leaves nothing out: it includes examples from real retrospectives, a theory of iterative retrospective design as well as a number of carefully designed exercises.

I'm not surprised that the authors could make clear such a difficult topic, blending insight from a number of fields and writing specifically for software teams. For more than a decade, Esther and Diana have been teaching the techniques and helping leading edge companies from all over the world implement retrospectives.

This is a must read book for anyone serious about making the Agile approach work, and then work better and better. Why? Because an Agile approach deployed right out of the book or course is likely to be a poor fit for your specific environment. Agile needs to be fine-tuned for your teams strengths, skills, challenges and goals. The iterative retrospective is the widely proven technique to make these crucial adjustments. There is no better book on the topic.
10 of 12 people found the following review helpful
Great material for mixing up end-of-iteration retrospectives Sept. 2 2006
By David W. Smith - Published on
Format: Paperback
Since Norm Kerth's seminal book on Retrospectives, development cycles have gotten shorter, and many teams have gone Agile. Where Norm focuses largely on big, end-of-project retrospectives, Diana and Esther close the gap, providing an excellent set of exercises that can be done in short periods time (say, at the end of an iteration), with or without a formal facilitator. (If retrospectives are new for your team, facilitation can help you get started. If you're going to do regular retrospective, you'll probably want to learn to self-facilite.)

The healthiest team I was on did regular, short retrospectives, both for process adjustment and to keep small issues from simmering and turning in to bigger issues. Regular retros can get repetitive; the exercises in this book can help mix things up.
7 of 8 people found the following review helpful
Every agile team should have a copy of this book! Nov. 17 2009
By Declan P. Whelan - Published on
Format: Paperback
Does your team tune out during retrospectives? Is your team bored from weekly sessions of "what did we do well?" and "what could we do better"? This book can help.

Agile is really about building learning teams. It doesn't matter where you are at today. The crucial thing is to strive to do better next week. And the week after that. Retrospectives are the key tool we have to critically review where we are at and what we can do, as a team, to continually improve. Diana and Esther give us both a powerful structure for facilitating effective retrospectives and excellent activities to slot into that structure. The books is extremely well laid out with activities grouped into sections that provide concise descriptions of activities that you can use right away.

Using this book you can plan effective, fresh retrospectives in ten to twenty minutes.

Every agile team should have a copy of this book!

Product Images from Customers