Scan barcode
mrduane's review against another edition
5.0
This was my intro to the Agile process, and I read it with with the rest of the team at the start-up where I was working at the time, so I may not be separating the book from the experience here. We had developers, product managers & sales engineers go through the process of modeling users; and defining, scoring and prioritizing stories. Regular updates from the daily scrums kept the rest of us in the loop, and our next several release cycles were better than the previous ones:
- we shipped what we said we would, close to when we said we would
- we shipped features to meet goals that the entire team bought into (or at least understood)
- better communication meant everyone was on the same page
Had I read it in a vacuum, w/o a specific project to work on, this book may not have been as valuable to me. I still use what I learned during this experience.
- we shipped what we said we would, close to when we said we would
- we shipped features to meet goals that the entire team bought into (or at least understood)
- better communication meant everyone was on the same page
Had I read it in a vacuum, w/o a specific project to work on, this book may not have been as valuable to me. I still use what I learned during this experience.
wolvereader's review
4.0
This book is a classic of Agile requirements gathering. Everyone involved in Agile software development should read it. Just skip the middle section about estimating and planning, and read Cohn's [b:Agile Estimating and Planning|9267|Agile Estimating and Planning (Robert C. Martin Series)|Mike Cohn|http://photo.goodreads.com/books/1165877153s/9267.jpg|12141] instead. It's slightly newer, more in depth, and Cohn revises a few of his stances.
More...