- Amazon Student members save an additional 10% on Textbooks with promo code TEXTBOOK10. Enter code TEXTBOOK10 at checkout. Here's how (restrictions apply)
Agile Retrospectives: Making Good Teams Great Paperback – Aug 5 2006
|New from||Used from|
Special Offers and Product Promotions
Frequently Bought Together
Customers Who Bought This Item Also Bought
No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.
To get the free app, enter your e-mail address or mobile phone number.
""Two of the software industry's leading facilitators have taken their many years of retrospective experience and distilled them into an approachable reference for agile team leaders. For all of the self-made facilitators out there who have been winging it, this book will provide a solid foundation to improve the effectiveness of your iteration, release, and project retrospectives."" --Dave Hoover, Lead Consultant, Agile Practices Obtiva Corp.""Esther Derby and Diana Larsen have written the definitive book on agile retrospectives. You don't have to be an agile team to take advantage of their book; you only have to want to improve. Follow their advice and your teams will be more successful."" --Johanna Rothman, Author, speaker and consultant, Rothman Consulting Group, Inc.
About the Author
Esther Derby is one of the rare breed of consultants who blends the technical and managerial issues with the people-side issues. She is well known for her work helping teams grow to new levels of productivity and is recognized as one of the world's leaders in retrospective facilitation. Esther's articles have appeared in Better Software (formerly STQE), Software Development, Cutter IT Journal, and CrossTalk. She writes regular columns for stickyminds.com and Computerworld.com, and publishes the quarterly newsletter, insights. Esther is also a host and session leader at the Amplifying Your Effectiveness (AYE) conference. Diana Larsen partners with leaders of software development projects to improve project performance, support and sustain change, and build collaborative workplaces. Diana serves on the boards of the Agile Alliance and the Pacific Northwest Software Quality Conference, participates in planning for the XP 200x and Agile 200x conferences, and speaks at several software conferences every year. She's written articles for Software Development, At Work, Cutter IT Journal, and Cutter's Executive Update and e-Advisor series. Diana is a founder of the Annual International Retrospective Facilitators Gathering.
What Other Items Do Customers Buy After Viewing This Item?
Top Customer Reviews
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.
Most Helpful Customer Reviews on Amazon.com (beta)
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.
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.
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.
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.
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.
Look for similar items by category
- Books > Business & Investing > Processes & Infrastructure > Workplace
- Books > Computers & Technology > Computer Science > Software Engineering > Information Systems
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
- Books > Computers & Technology > Project Management > PMP Exam
- Books > Computers & Technology > Software
- Books > Textbooks > Computer Science & Information Systems > Computer Science
- Books > Textbooks > Computer Science & Information Systems > Software Design & Engineering