Because the project of writing this book began about ten years ago, many parts of the book are already quite dated. Worth a read for some interesting details, gobs of “case studies,” and holistic, humane perspectives on work.

i had high hopes for this book since the authors have been very influential for me, especially gene kim - i've listened to every episode of the idealcast and follow anything he works on.

On page 8 i felt a keen sense of disappointment when the book stated that it would be focusing on lead time to deploy (or similar), as that's only one facet of DevOps. I was worried that it was going to just be about CICD, which seemed out of character, given how much Gene focuses on organizational health, structure and dynamics, leadership, etc.

That fear passed very quickly in the following pages when I saw what they were doing - it isn't only focusing on shipping faster, it's about *all* the things you need to do before you can deliver value quickly, safely, and sustainably.

This includes value stream thinking, cross functional teams, testers embedded with teams and acting as enablers, shifting compliance and security left, reducing batch size, building psychological safety, measuring team health (eNPS, SPACE, etc), identifying types of waste (Making Work Visible is also good for this), types of work (flow framework), OKRs, coaching katas, fast bidirectional feedback, reducing planning overhead and coordination overhead, feature flags, dark launches, A/B testing, Gemba walks, non-functional requirements (the ilities), elevating the improvement of daily work over the work itself, and a discussion of trunk-based work vs feature branches (I prefer short-lived feature branches that are continually updated from main)

I've read all of these subjects before, but having them all as part of a single narrative was valuable for collecting my thoughts.

It's a good book for starting out in dev-ops or agile methodologies. It's very focused on why and how to do it, so if you have experience setting it up or working with it already, someone else probably read this already and provided that information to you.

Good work book, although I didn't finish it - as I went along it started to feel as more of a reference book than one that is worth reading cover to cover. I read the first half though and enjoy what they put down, it's definitely more of a philosophy book but it does a good job of selling their worldview as it relates to software development.

This book took a long time to get to the meat of the discussion, but once it did, I couldn't put it down. The first few chapters which seemed horribly slow at the time, made up for it as the examples for why you needed Dev-Ops they provided earlier, were used to show how they went from situations that needed help, to how they went and innovated.

This book answered a lot of the questions that had been brewing in my mind, and I'm so grateful to the colleague of mine who recommended it to me. DevOps is a culture/mindset of unifying development and operational activities. I personally think it's one of the greatest and most influential inventions of this century so far. The treasure trove of lessons/ideas in this book are applicable to any technology company, not just software houses. I particularly like the way the author uses case studies to demonstrate the problems that you can have without DevOps. Highly recommended to anyone who cares about continuous improvement, organizational learning, maximizing productivity and most of all - staying in business.

Well written, good content. Lack of fifth star is more about me than the book itself. It wasn't too engaging and it's probably due to my familiarity with the ideas discussed.

This is no Phoenix Project in terms of equally captivating the reader, but for its nonfiction and reference focus it is a trove of useful recommendations outlined clearly and (mostly, I'd say) concisely.

Your challenges after reading this book will be to identify and prioritise the next steps in your own work to reduce lead times and improve the flow of work.

My challenge will be to read this again while simultaneously take notes and scribble questions, because there's a lot of material, and my head will only remember (if lucky) the gists.