Succeeding with Agile: Software Development Using Scrum: A Roadmap to Agile Success

Mike Cohn's Succeeding with Agile is one of the more honest Scrum books on the shelf. It does not pretend that adopting Scrum is easy. It walks you through the real challenges -- resistance, role confusion, organizational friction -- and gives practical advice for each.

What works

Cohn draws a critical distinction most agile books skip: Scrum is a mindset, not just a process. You can follow every ceremony perfectly and still fail if the culture does not support collaboration, transparency, and iterative learning.

His breakdown of Scrum roles is clear and useful. The Scrum Master is not a project manager. The Product Owner is not just a requirements gatherer. The development team is not a group of task executors. Each role has specific responsibilities, and Cohn explains how they interact in practice, not just in theory.

The sections on handling resistance to change are the most valuable part of the book. Cohn is realistic about how hard organizational change is. He does not hand-wave it away with "just get buy-in." He offers concrete strategies for dealing with skeptics, managing stakeholder expectations, and building momentum incrementally.

Where I push back

The book is dated. Written in 2009, it predates the widespread adoption of Kanban, Shape Up, and the broader backlash against Scrum-by-the-book. Some of the practices Cohn advocates feel rigid by modern standards.

He also does not spend enough time on when Scrum is the wrong choice. Not every team benefits from sprints and story points. Some work -- infrastructure, platform, research -- fits better in other models. A more honest book would acknowledge the boundaries of Scrum's applicability.

The writing can be dry. This is a reference book, not an engaging read. Keep it on your shelf and pull it out when you hit a specific problem.

Who should read this

Scrum Masters and agile coaches who want depth beyond the Scrum Guide. Engineering managers leading agile transformations. Teams that are "doing Scrum" but not getting the results they expected.

If you have never done Scrum, start with the Scrum Guide itself. Come to this book when you hit the real-world complications.