Seemed a bit dated with the training we had been taking

Fundamental of Agile estimating. Good that it have some patterns defined about how many possible way to estimate and plan.

Bridge the traditional world about what metrics usually use to estimate and the Agile world.

Think about revisit this book for the case study part at the end of the book.

Had a quick read on how to do estimates

A decent book that anyone in the industry should read , it gives a lot of insights into software development agenda I personally found it way more understandable and structured than xp or srcub .

Great all-round refresher with a lot of practical tips even for someone that read about Agile a lot. Recommended.

Almost 20 years passed since this book as written but it's still one of the best references on estimating and planning. While not everything in the book remains relevant or pertinent today (things change) most of the book is still on point. This was the second time I read it.

Recommended book for project manager/scrum masters or whoever interested in planning and estimating. The book gives guidelines and tools that can help to succeed in planning, estimating, and scheduling projects while having high level of uncertainties in the project. Mike gives detailed examples with practical approaches and techniques to increase agility and shows how to produce software of high business value.

3.5 stars
a bit outdated at times and not enough depth for myself at other

Probably one of the best books I've read about Agile software development. Cohn covers all the basics of what estimating and planning is like in an Agile methodology (actually, I think seems pretty Scrum-centric). More importantly, however, he includes a considerable amount of discussions on some of the more common points of confusion - e.g. story points vs ideal days, estimating size vs estimating duration, planning for multiple teams, etc. Also has a lot of helpful material for Product Owners, with tips on ways to identify and prioritize stories. And not just wish-washy stuff either, Cohn gets right down the the financial analysis if proposed feature-sets.

This is surprisingly useful book for a PM practitioner. Gives some good examples about proper ways to manage projects and estimate the work.

This book answered lots of things I've wondered about for years. The writing is a little dense at times but there's so much great info. DEFINITELY read the case study at the end. It made it all come together for me.

Clear and concise but I have to admit I did not read the last part. I have an aversion to technical writers entering the world of creative writing and therefore skipped this last section. My apologies to Mike Cohn, who may be a fine fiction writer but I could not overcome my phobia.

I found the preceding work admirable and as I have just become involved in a product development project (as nominal product owner) I hope to put what I have learned into practice and I am sure I will be revisiting the work more than once.