|
||||||||||||||||||
|
||||||||||||||||||
|
||||||||||||||||||
Frequently Bought Together
Product Details
|
Product Description
Product Description
See how to mine the experience of your software development team continually throughout the life of the project. The tools and recipes in this book will help you uncover and solve hidden (and not-so-hidden) problems with your technology, your methodology, and those difficult "people" issues on your team.
Project retrospectives help teams examine what went right and what went wrong on a project. But traditionally, retrospectives (also known as "post-mortems") are only helpful at the end of the project--too late to help. You need agile retrospectives that are iterative and incremental. You need to accurately find and fix problems to help the team today.
Now, Derby and Larsen show you the tools, tricks, and tips you need to fix the problems you face on a software development project on an on-going basis. You'll see how to architect retrospectives in general, how to design them specifically for your team and organization, how to run them effectively, how to make the needed changes, and how to scale these techniques up. You'll learn how to deal with problems, and implement solutions effectively throughout the project--not just at the end.
With regular tune-ups, your team will hum like a precise, world-class orchestra.
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.
Suggested Tags from Similar Products(What's this?)Be the first one to add a relevant tag (keyword that's strongly related to this product)
|
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most helpful customer reviews
2 of 2 people found the following review helpful
5.0 out of 5 stars
Great stuff,
By
This review is from: Agile Retrospectives: Making Good Teams Great (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!
4.0 out of 5 stars
Used as a reference for retrospective meetings,
By
This review is from: Agile Retrospectives: Making Good Teams Great (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.
Share your thoughts with other customers: Create your own review
Most Helpful Customer Reviews on Amazon.com (beta) Amazon.com:
4.4 out of 5 stars (27 customer reviews) 40 of 49 people found the following review helpful
3.0 out of 5 stars
Reality Check,
By R. Williams "code slubber" - Published on Amazon.com
Amazon Verified Purchase(What's this?)
This review is from: Agile Retrospectives: Making Good Teams Great (Paperback)
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. 10 of 11 people found the following review helpful
5.0 out of 5 stars
Take your team to a new level with this book!,
By Lisa Crispin - Published on Amazon.com
This review is from: Agile Retrospectives: Making Good Teams Great (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. 7 of 8 people found the following review helpful
5.0 out of 5 stars
Great material for mixing up end-of-iteration retrospectives,
By David W. Smith - Published on Amazon.com
This review is from: Agile Retrospectives: Making Good Teams Great (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. |
|
Listmania!
Look for similar items by category
- Books > Business & Investing > Management & Leadership > Management
- Books > Business & Investing > Organizational Behaviour > Workplace
- Books > Business & Investing > Skills
- Books > Computers & Internet > Computer Science > Software Engineering > Information Systems
- Books > Computers & Internet > Programming > Software Design, Testing & Engineering > Software Development
- Books > Computers & Internet > Project Management > PMP Exam
- Books > Computers & Internet > Software
- Books > Professional & Technical > Business Management > Management & Leadership > Management
Look for similar items by subject
Feedback
Would you like to update product info or give feedback on images?
|
