These days, everyone knows that there's no point in trying to pick up an agile framework and dropping it into an organization without some kind of adjustments. Nobody believes in 'one size fits all' anymore. The good news is that Scott Ambler hasn't believed it for several years, and has written this guide to choosing a bespoke way of working that fits your organization's needs.
It starts, not from telling you what to do, but from identifying needs. On the basis of those needs, you can work through the book to make the 'Kanban vs Sprint' decision, whether to go DevOps or Lean, whether to appoint a product owner, or to embed a user in the development team.
This is not a book for novices, and if you need step-by-step instructions on implementing the design you come up with, then you're going to need to refer to other sources; the other sources recommended in this book are good starting points. Nor is it a book for people who need a lot of persuading in order to be willing to try something - there's no salesmanship here, just pragmatic, needs-driven assessments.
This is a landmark book, the first volume that I know of which truly moves us out of the 'off the shelf framework' space and into the 'design what's right for you' space. No software development process expert should be without it.