The DevOPS Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations Paperback – 6 Oct. 2016

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”

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.

Perfect companion to the Phoenix Project (as it shares one of the same authors and is more of an entertaining 'horror story with a happy ending' about how badly managed IT projects can fail!) which I also bought at the same time. Agile infrastructure and lean IT, in the future people will look back on the history of IT management and DevOps and wonder how and why we ever delivered infrastructure and software projects using individual team silos, just throwing barrels of code down the waterfall without talking back to whoever started throwing them! If you really want to get ahead, start with the third section for practical implementation advice.

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?

I read this book after it was recommended during a LinkedIn hosted training course (DevOps Fundamentals). Unsurprisingly, it's tightly aligned with the advice in that course, but the book is exceptional in being easy going and a "light" read despite the serious topic. It uses cases studies with an usual degree of honest insight (many of the case studies being major companies including FaceBook, LinkedIn, Etsy, NetFlix.A great read for anyone wanting to "catch up" on modern DevOps (even from scratch). I'm off to buy it's accompanying novel, The Phoenix Project...

Excellent overview of DevOps, with the pros and cons along with real world examples of businesses that transformed themselves using the techniques in this book.

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?

If you are new to Devops this is a highly recommended item. Comes well packaged and it is quite informative ! Go ahead and order !

For you, like me, believe it is possible to work as a human been within IT, this book is a must read!

Una excelente referencia para entender la simbiosis entre Desarrollo-Seguridad-Operaciones para hacer más ágil los procesos de lanzamiento de nuevos productos y servicios

-

I loved this book. I recommend the reading of it to everyone involved in IT software delivery. It is not technical, so it is easy to understand for everyone, business people too.

As CTO, I'm glad I read this book through. Implementing the devOps principles has enabled my team to greatly improve product quality, and thus customer satisfaction.