|
| 1 | +--- |
| 2 | +layout: writeup |
| 3 | +title: Agile Retrospectives |
| 4 | +categories: |
| 5 | +- writeup |
| 6 | +--- |
| 7 | + |
| 8 | + |
| 9 | +[Agile Retrospectives: Making Good Teams Great][link] |
| 10 | +Esther Derby, Diana Larsen |
| 11 | +ISBN: 0977616649 |
| 12 | + |
| 13 | +--- |
| 14 | + |
| 15 | +**What's the point?** |
| 16 | +Like the title suggests, this book drills down into retrospective meetings conducted by agile |
| 17 | +software teams. Retrospective meetings are really important, but are often either overlooked |
| 18 | +or poorly facilitated. |
| 19 | + |
| 20 | +**How was it?** |
| 21 | +Awesome. This book made me want to try leading the next retrospective meeting for my team. |
| 22 | + |
| 23 | +An important focus of the book is on how to *design* a retrospective. There is more to it than |
| 24 | +just getting the team in a room and complaining for an hour. |
| 25 | + |
| 26 | +I really liked the list of activities and exercises, especially because the book clearly explained |
| 27 | +WHY to do each activity and what you, as a facilitator, should be trying to gain from them. It's |
| 28 | +one thing to say "have everyone write Explorer, Shopper, Vacationer, or Prisoner on a card" - |
| 29 | +but the book explains that you can use this to set understand people's attitude toward the meeting |
| 30 | +and adjust your tone/agenda accordingly. |
| 31 | + |
| 32 | +For someone like myself who has never lead a retrospective, this book is a great resource. There |
| 33 | +are step-by-step actions to take, with lots of examples and even guidelines for how to time-box |
| 34 | +each section. |
| 35 | + |
| 36 | +**Who should read it?** |
| 37 | +All team leads, those looking to become team leads, anyone leading retrospectives - if you |
| 38 | +haven't read this book, I think you are really missing out. |
| 39 | + |
| 40 | +[link]: http://pragprog.com/book/dlret/agile-retrospectives |
0 commit comments