Finished Chapter 1: The Purpose of Planning. Nothing new there.
Finished Chapter 2: Why Planning Fails. Pretty obvious facts laid down with a bias against the traditional approach. I have prioritized features in traditional development as well as handled uncertainty - it's all part of risk management.

Finished Chapter 3: An Agile Approach - Mainly covers the Agile Manifesto
Chapter 4 looks very exciting - Estimating Size with Story Points

This was a very clearly written overview of various approaches to the topic. It was great to see clear terminology explaining things that I have practiced but not really understood in the past. I recommend this for tech leads, project managers, and development managers. Even if you are familiar with agile practices, you will probably learn something from this book.

Все ещё неплохая книга по agile планированию. Есть, конечно, много того, что уже сейчас решается более современными методами, но системный подход все тот же. В итоге неплохая книга, которой жутко не хватает картинок. Вообще, почему авторы так жмутся на подробные и понятные иллюстрации своих концепций, я не понимаю.

I'll try to update this later with a summary of what I learned in this book, but my overall impression is that this was a great book for learning the basics of Agile software planning. I especially liked the last chapter, which wrapped up the whole book in a fictional narrative based at a game software development company. Using this example to wrap up all of the concepts in the book was a great move, even if (as a work of fiction) it was horribly written.

I found Agile Estimating and Planning to be repetitive at times, and a lot of the examples weren't as helpful, so the last chapter really saved it for me.

However, I was inspired to try to move one of our projects at work to a more agile-planned method after reading this book, so that's pretty high praise in itself. Well, unless that project ends up being a total failure. I guess in that case it wouldn't be such high praise.
--------------------------------------
Update: I've upped my rating of this book from 3 stars to 4, since I've found the knowledge I gained from it to be pretty useful in day-to-day work. The "planning poker" and requirement gathering sections were particularly helpful. I'd say that it really is worth a read, and I'd actually like to go back for a re-read at some point.

Must read for anyone who is practicing Agile!!

Must read for anyone who is practicing Agile!! The sizing and estimation concepts are explained so beautifully that you can right away start practicing most of what is being suggested!

Well written, to the point.

Probably one of the best books I've read on software production management (with the caveat that I have not tried the techniques yet, but will be doing so for a current project).

Estimating and planning in software development with any sort of real confidence is a big challenge. Even more so in game development, where experimentation, the discovery of new features and new problems are all part of the process; meeting a set of specifications doesn't guarantee a good game.

Cohn describes a small set of simple techniques for breaking down large requirements into features and user stories, estimating them as a team using story points on a relative scale, and using velocity as a measure of progress. Iteration and release planning provide a way to plan development in a collaborative and sensible manner that provides visibility for tracking real progress in terms of features completed, as opposed to tasks completed. After all, do you ship completed tasks to your customers, or completed features?

While many of the techniques are not new in the Agile methodology, Cohn's presentation is simple, easy to understand and put into practice. He provides alternatives and recommendations that take into account incomplete requirements, uncertainties, and human behavior in a pragmatic approach. If you have been put off by agile development books that are almost militant or overcompensating, this book might be for you.

Cohn has a casual tone, a simple and clear writing style that is easy to read through quickly, and uses clear diagrams and charts to illustrate his points effectively.

If you are looking for different development techniques to get better visibility on your team's progress, give this book a try.

Valuable Reading for Software Estimating

Describes the balance of satisfying stakeholders and sensible software development. Emphasis on team building through performance. Demonstration of having clients collaborate on prioritizing what is possible and what is needed.

Exhaustive book about planning end estimations in agile projects.

Worth to read!

Good book that summarize the best approaches of applying estimation and planning in Agile projects. Even people with experience in project management will find it useful

This book details the process of estimation and planning in an agile environment very simply. It is an excellent read for any Product oriented employee or anyone struggling with planning. I would also recommend it to any Scrum master or Agile Coach