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.
Customer Reviews:
Avg. Customer Rating: 4.5 / 5.0
Read the 1st chapter ...:
Based on the first chapter I raced through the rest of the book. I was not nearly as impressed with the remainder of the book. It added value but the "AHA" moment was in first 20-30 pages. It was worth the purchase because of that first chapter but save some time and concentrate on the chapters up front then go and try some of the recommendations.
Full of really practical and fun advice:
This is one of those "common sense" books. It's full of really obvious practical advice. The difference I found however is in the multitude of simple and practical exercises it contains. The book is a really quick and easy read. It's now constantly on my desk as a reference. I plan to use a few of the exercises in our next retrospective in a week. Whilst this is an agile/scrum focused book, many of the exercises could be easily adapted to other "review" type situations in business and teaching.... more info
About emotional perception not enhancing the development of software...:
I have read at least 10 books of the Pragmatic Series and this is the first one I couldn't finish because it was so terrible (I actually threw it out). This book is exactly what is wrong with corporate culture. Placating overly sensitive employees who need emotional coddling instead of trying to improve the process of software development. I prefer to work with adults, that have the maturity to get their emotional needs fulfilled outside of work, so time at work can be spent being productive. This book... more info
Must-read for any scrum master:
This is a really useful book. Most practical. Being into scrum (sort of) for 3 months, we've tried to change our retrospective meeting agenda applying methods from this book. We did this just once as yet, and applied only a single combination of methods from virtually countless variants possible. The result is great: retrospective meetings became more meaningful and fun. Every scrum master (and anyone leading retrospective meeetings) should read this book.
Privacy policy: we don't collect information
about visitors except for the standard technical server logs. We don't send unsolicited emails. We don't
sell the information that we don't collect about you to anyone. When you follow
links to other sites, their privacy policies apply. Thanks for visiting!
