Accelerate: The Science of Lean Software and DevOps

288 pages

Published March 27, 2018 by IT Revolution Press.

ISBN:: 978-1-942788-33-1
Goodreads:: 35747076

(1 review)

This book goes into depth on research that shows how DevOps techniques can make technology organizations more effective. Fundamentally, they can help create generative team cultures which in turn leads to higher performance, better retention and better outcomes. The book shares multiple years of research from the State of DevOps reports.

3 editions

dozens reviewed Accelerate: The Science of Lean Software and DevOps by Gene Kim

Review of 'Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations' on 'Goodreads'

4 stars

three stars for content
five stars for delivery (organization / being well written)

This did in fact end up feeling very much like a magic bullet. The thing is, based on personal experience, and the science and methodology laid out in the book, I guess I'm not convinced that it isn't a magic bullet: continuous delivery and lean processes (together with "Transformational Leadership) are big, powerful concepts. I have no doubt that together, they drive performance.

I liked the bits on measuring culture, and burnout. There were some good tips about leadership and coaching.

I recoiled initially whenever the author insisted that Trunk Based Development is part of the magic bullet, but I think now that I had a different understanding of the term. Whereas I was imagining a no-branch flow and committing directly to Master, the author was describing few, short-lived branches. And I think I agree with that …

three stars for content
five stars for delivery (organization / being well written)

This did in fact end up feeling very much like a magic bullet. The thing is, based on personal experience, and the science and methodology laid out in the book, I guess I'm not convinced that it isn't a magic bullet: continuous delivery and lean processes (together with "Transformational Leadership) are big, powerful concepts. I have no doubt that together, they drive performance.

I liked the bits on measuring culture, and burnout. There were some good tips about leadership and coaching.

I recoiled initially whenever the author insisted that Trunk Based Development is part of the magic bullet, but I think now that I had a different understanding of the term. Whereas I was imagining a no-branch flow and committing directly to Master, the author was describing few, short-lived branches. And I think I agree with that strategy. I definitely agree with preventing code lock, and long-lived, divergent branches (and merge conflicts).

I lacked the context / experience to appreciate other parts. I have only ever worked at lean / agile companies and never at huge bureaucratic or pathological organizations, so i often found myself thinking, "Of course the generative way is the correct way, why would you ever do it any other way?"

I recommend readers skim part one, glance at part two, and read part three. Read the table of contents, the quick reference, and the conclusion. This book was so well organized that you can read it very quickly. It was written to be an easy to use reference, and I will keep it on the shelf and refer back to it.