Good content but it's "philosophy shi**"

This book helped me develop the mindset how to succeed in planning, estimating, and scheduling projects with a certain level of approximation.
It also helped me know about the guidelines and tools that we need to succeed with limited Planning & scope Estimation that is just enough to deliver business value to the customer every Sprint.

The book emphasizes on accepting change late in the Release in Agile Manifesto and this book dwells into how to build such a mindset within a Team which I found quite enlightening and have used the knowledge gained in this book to share with Teams when we sit for Sprint Planning. especially with new Teams or members. It also underlines the value of estimating when it is needed & now rather than sitting over it for very long- which is another constituent of fail-fast approach.

The book, by providing real time examples & sharing workable solutions for Estimation & Planning software projects with some uncertainty provided me and other readers with improving my T skill set, providing with reasoning for various approaches and deepening my understanding Estimation process without diminishing any Business value. It also tackles Technical debt and introduced me to some novel of handling tech-Debts in Sprint that I use in my projects.

There is a great emphasis on making readers understand that the Estimation & Planning should be Agile & light footed as well and not just the Project that should Agile. This was a great distinction that took me some time to imbibe and I have used this insight to ensure stakeholders & Teams understand that all estimation & Planning, though essential, is only an approximation to predict future and should not be considered as written in stone even if the Team estimating it has the most stable velocity or is a seasoned Agile Feature team that always estimates correctly.
Using Fibonacci hence makes sense, it being non linear sequence, in sync with risk involved in estimation especially with larger backlog Items.

Is it an essential book for planning and estimations! I would recommend reading it for all participants of an agile team!
The last part of the book contains an example of a real situation when a team starts with a new project, create and estimate stories, plan releases and iterations. I enjoyed it the most as it was an exciting story.

As someone who finds much of the talk from the so called "Agile coaches" plainly useless, this book was surprisingly useful. If you want to read a book on the topic thats definitely it.

Right, this is a great agile planning book full of good ideas which talks through the basics, gives strategies on prioritisation, and ideas on syncing up multiple teams. There’s even a short story at the end to illustrate some of the basics.

So why have I only given it four stars? I have to admit, compared with other agile and/or DevOps books I’ve read this one was heavy going. It took a lot of effort to reach for it towards the ends and I found myself putting it down for months in end. Maybe personal taste but probably a book I’d use for reference rather than read cover to cover...

Essential reading for agilists.

Excellent book, I'm sure I'll go back to it quite often.

Автор розглядає під мікроскопом всі еджайл процеси, роздумує над ідеальними днями, пунктами, годинами та іншими болями цифрового робочого життя. Дуже кумедне завершення книги, де він наводить приклад гіпотетичної компанії, що мала попередній досвід каскадної організації праці й перейшла на еджайл. Описує як в них все класно, все вдається, все всім подобається, замовники щасливі, працівники теж, така собі еджайл утопія. Якщо не враховувати цієї кумедної прикінцевої реклами методу, то кн��га дуже класна й корисна.

This is book is written in a great way, which makes it very easy to read.
It is probably one of my favourite books on Agile Methodologies. I love the case study in the end!

The bible of agile planning. True classic. Even if personally I don't agree with some statements, this book is a MUST read for anyone who's interesting in REAL-LIFE aspect of agile approach. This book is exactly about the actual bread and butter of agile projects in the COMMERCIAL environment - where risk and predictability have to have some harness.

For me personally it's kind of a shame that I've read it so late and who knows - maybe even I'd skip it completely, but I've decided to read it as a part of my preparation to PMI-ACP exam. I think it was a good choice.

Must read for Agile development.

principal-dev