27 books like The DevOps Handbook

Accelerate is a book about data. The authors used data collected during their PhD projects in order to prove The DevOps is effective.

They have all sorts of different ways to measure DevOps, it sufficiency, and the fact that way more projects succeed when you do DevOps, rather than waterfall methodology.

The book essentially show can be used as evidence of return on investment when modernizing your IT department. I am a person who loves data, and thus I absolutely love this book. Also, if you listen to the audiobook version, one of the authors reads it to you and her personality really shines through in a fun way.

I really enjoyed listening to Nicole read a book about to me about data!

The Phoenix Project is a storybook about affect fictious company called parts unlimited.

I swear I must have worked at this company at some point in my career, it feels so familiar! It follows a story of an organization that used waterfall in order to make software and all the problems that happened from using this very old software development methodology.

Throughout the story they ‘discover’ how to do DevOps, slowly improving all of their process is until they have a smooth-oiled software creation machine. This includes many stories about security and why the old ways of doing information security just don't work within a DevOps environment.

The characters in this book are both lovable, and relatable. I would never have thought a fictitious story about an IT department could be so fun to read!

The Unicorn Project book picks up where The Phoenix Project book ended.

There is a new character introduced named Maxine, and I want to be Maxine when I grow up! Her character is brave, fun, and endlessly patient as she transforms the way they build software to more effective and productive methods.

She has a family, and life outside her org, which is something I feel all of us can relate to, balancing life and work. She really saves the day, over and over again, as the book proceeds to change, update, and improve every single thing they do within parts unlimited, the fictitious company in this story.

It was a very fun sequel to The Phoenix Project.

This book is set in the same universe as The Phoenix Project and The Unicorn Project, but it's at a new company named investments unlimited.

It's also a fictitious story, but with all brand new characters, and brand new problems! In this book they cover security much more deeply than any of the other previous books, talking about how compliance and audit can work together with the information security and DevOps teams.

They talk about common problems that I have faced in many organizations, and a lot of the stories feel so familiar I wonder if the authors have followed me around throughout my career.

Although of course they save the day in the end, there are many parts of the book where we're not quite sure if they're going to make it or not with various characters learning to see things in new ways, so that they can make… show more.

Before Agile and Lean had rocked the software development industry, William Deming was busy forging this new world of work.

Out of the Crisis is predominantly a management book, but it’s really the spark that started the lightweight movement in software delivery. A key concept in the book is how to identify the work system's performance, separate from the performance of individuals.

We all know how important culture is to DevOps.

Well, Doug McGregor was one of the earliest proponents of healthy workplace culture. The Human Side of Enterprise was written during the 1950s and contains the kind of advice you might associate with Dan Pink’s more recent book, Drive.

If you want to read a book from the pivot point between command and control management and modern theories of motivation, this is the place to start.

In addition to Java, you need to know about the Java ecosystem.

Each chapter covers a type of tool like version control, securing binaries, or mobile. Some chapters cover a variety of tools. I particularly liked the overview of Quarkus and Micronaut. I also liked the emphasis of tools vs a role. The analogies were great such as comparing identify/fix/deploy to an oil spill.

The book is 300 pages and easy to carry around. Despite having four authors, the book is very cohesive and reads well.

I was a long-time skeptic about the business novel format, but The Goal changed my mind.

In this book, Goldratt presents concepts like Theory of Constraints with a business thriller (seriously). You get to live the same aha moments as the protagonist, Alex Rogo, as he encounters the pipe-smoking philosopher Jonah.

The setting may be a factory, but you’ll find many parallels to your DevOps work in this book.

The importance of Extreme Programming can’t be overstated.

Kent Beck created one of the few Agile methods that captured not just a process for managing work, but a set of practices that would keep your software manageable in the long run. Shortly after this book was published, the Agile Manifesto was created.

You might say, “the rest is history”, except the industry lost its way for a decade. Extreme Programming was revived in Dave Farley and Jez Humble’s Continuous Delivery – now a vital part of DevOps. The State of DevOps report has validated at least half of the Extreme Programming practices, and Continuous Delivery brings it to the fore once more.

This recommendation is a bit of a cheat — I’m not recommending this exact book, but one of the books in the series that this book is part of.

Once you have the first two books under your belt, you’ll know how to solve ML problems. But you will keep reinventing the wheel. What you need next is a book on common “ML tricks” — best practices and common techniques when doing ML in production.

The problem is that these tricks are specific to the type of data that you will be processing. If you are going to be processing images or time series, read the corresponding books in the same series instead.