The Devops Handbook: How to Create World-Class Agility, Reliability, & Security in Technology Organizations Paperback – 25 Jan. 2022

This is the best book I’ve read on DevOps and it follows on nicely from Gene Kim’s other book The Phoenix Project.It’s quite easy to think that DevOps practices are just something that dev teams deal with and the value is simply just an increase in throughput, but the book provides clarity on the colossal value that adopting a DevOps culture and the principles can have on teams, the business, and customers.Throughout the book, Gene echoes the importance of having the whole product team (product manager, designer and several engineers)) involved in the transformation, as well as focusing on outcomes, and to achieve outcomes you need to collect data and learn through experimentation which is covered in the book too.Gene gives good advice that it’s important to avoid funding projects and instead you should fund services and products: “A way to enable high-performing outcomes is to create stable service teams with ongoing funding to execute their own strategy and road map of initiatives”.This is the most comprehensive and practical DevOps guide out there and the layout makes the content easy to digest. The book covers:– History leading up to DevOps, and Lean thinking– Agile, and continuous delivery– Value streams– How to design your organisation and architecture– Integrating security, change management, and complianceThe principles and tech practices of:1. Flow2. Feedback3. Continual Learning and Experimentation“Our goal is to enable market-oriented outcomes where many small teams can quickly and independently deliver value to the customer”

I read the review of this book and I recommend it for business owners and lead IT members. Book is useful for DevOps and securing your business.

As a DevOps manager overseeing both a university and a college estate, I grabbed the paperback of the second-edition DevOps Handbook to see whether the new case studies spoke to the sprawling, budget-conscious world of higher-ed IT. They do—mostly.The expanded material folds in 15 fresh stories (Fannie Mae, adidas, the USAF), and Nicole Forsgren’s updated research threads everything together with hard numbers rather than hopeful anecdotes. The big win for me is how clearly the authors now argue that DevOps isn’t an IT side quest; it’s a campus-wide culture shift. Swapping “feature flags” for “course-registration flags” made more than a few lightbulbs go off in my team’s heads.Print quality is solid—matte pages that survive high-lighter abuse—and the companion PDF (download link in the book) means I can clip graphs straight into faculty slide decks. The only drawback is heft: at nearly 500 pages, it’s more brick than handbook. The authors try to offset that with handy margin icons, but I still found myself flipping back to the practices summary in Part IV to keep the fire-hose of information organized.If you’re already knee-deep in Jenkinsfiles and Terraform, some chapters will feel like familiar territory, yet the new real-world war stories make the reread worthwhile. For anyone still arguing why DevOps matters outside the data centre, this second edition gives you the narrative ammunition and the metrics to win budget, hearts, and—crucially—academic board approval.

Not what I expected and I am sure others will feel the same after waiting this long and being an avid fan of The Phoenix Project. Not disappointed either! Fast-paced, simple to read, many concepts to thrown out on how to introduce the concepts of DevOps (Continuous anything), the values (CLAMS) and the principles (The 3 ways of flow, feedback and keep experimenting and learning).This is a handbook, not a step-by-step guide. As a handbook it provides ideas on how to look at the work you perform for your organisation that is reliant on technology (so almost everything) and via a collaborative approach strongly supported by leadership to make things better, faster and safer. Think of the outcomes of impressed customers, happier staff and less cost.DevOps Handbook is packed with extra information and guidance to keep you learning for years and the variety of webinars and blogs beginning to materialise around this book, will ensure that the technology community can keep this movement alive for some time to come. Have a read, learn, and join the DevOps party.

This is an amazing work! There is so much detailed content and it is wall to wall with insight from real world implementations. I must admit though that personally I would have preferred a lot more diagrams to consolidate many of the points being made, as the ideas got swamped by the detail for me.I think it makes for better reference material than a step by step guide through what to do and the rationale for why. At the end of the book I'm not sure I could really summarise what I learned beyond the few glib phrases I already knew - but judging by the other reviews this probably says more about me than the suitability of the book.It might help to just have a summary at the start or the end of each chapter?

Over the last few years I have worked as both a developer and a DBA (database administrator). DevOps has become a buzz word in recent years and, on recommendation, I brought this book to help increase my knowledge of this area.A trend with modern IT related books is to be over verbose and repetitive. I have a 1000+ page database tome that could be reduced to 300 pages without loss of content. This is the same it could be easily halved. The book has improved my understanding of DevOps but was disappointing at the same time. Is there a really good book on DevOps out there?