Android Robot

DnnForge - NewsArticles


Title: Agile Estimating and Planning Author:

Mike Cohn ISBN: 0131479415

I finally was able to finishing reading Agile Estimating and Planning today. Normally I’m able to read a book this size (368 pages) in a few days, but this one took me about a month to get through. As with all books, I read them thoroughly, dog earring pages and highlight interesting information for future use.

The book was great and contained a ton of information about estimation I plan to use in the future. The estimating portion, took me the longest to get though, It wasn’t the authors writing style, the subject was just dry and not very fun to read about.The book goes into detail about how to create stories, how to estimate them using ideal days, and how to estimate using points.

The book talks in detail about release plans, iteration plans and burn down charts . The book closes with a fictional case study, which walks the reader through the start of an Agile project, which is great for readers who are not familiar with the process. I recommend this book for new members of an Agile team, or someone looking to learn about estimating on Agile projects. During an Open Space session at CodeMash last week, I heard the term “fraken-gile” (I think it was James Avery that said it) which hit home to me. I’ve seen many teams try to adapt Agile processes and turn it into a mess. Many of them abandon the process because of the mess they have created. Most of the times, teams start to implement these processes after reading a book such as Agile Estimating and Planning.

For someone looking to introduce Agile process into their team, I recommend consulting with an Agile Coach. If your company is not willing to foot the bill to bring in an Agile Coach, I recommend shadowing an Agile team, attending conferences such as Agile Coach Camp, and reading as many books as possiable. The Agile Manifesto states “People over Process”, so in most cases Agile teams are more than willing to have you observer there process.