Book Club: The DevOps Handbook (Conclusion)

This entry is part [part not set] of 25 in the series DevOps Handbook

The following is a chapter summary for “The DevOps Handbook” by Gene Kim, Jez Humble, John Willis, and Patrick DeBois for an online book club.

The book club is a weekly lunchtime meeting of technology professionals. As a group, the book club selects, reads, and discuss books related to our profession. Participants are uplifted via group discussion of foundational principles & novel innovations. Attendees do not need to read the book to participate.

Background on The DevOps Handbook

More than ever, the effective management of technology is critical for business competitiveness. For decades, technology leaders have struggled to balance agility, reliability, and security. The consequences of failure have never been greater―whether it’s the debacle, cardholder data breaches, or missing the boat with Big Data in the cloud.

And yet, high performers using DevOps principles, such as Google, Amazon, Facebook, Etsy, and Netflix, are routinely and reliably deploying code into production hundreds, or even thousands, of times per day.

Following in the footsteps of The Phoenix Project, The DevOps Handbook shows leaders how to replicate these incredible outcomes, by showing how to integrate Product Management, Development, QA, IT Operations, and Information Security to elevate your company and win in the marketplace.

The DevOps Handbook

Conclusion: A Call to Action

DevOps offers a solution at a time when every technology leader is challenged with enabling security, reliability, agility, handling security breaches, improving time to market, and massive technology transformations.

An inherent conflict can exist between Development and Operations that creates worsening problems, which results in slower time to market for new products and features, poor quality, increased outages and technical debt, reduced engineering productivity, as well as increased employee dissatisfaction and burnout. DevOps principles and patterns enable teams to break this core, chronic conflict.

DevOps requires potentially new cultural and management norms, and changes in technical practices and architecture. This results in maximizing developer productivity, organizational learning, high employee satisfaction, and the ability to win in the marketplace.

DevOps is not just a technology imperative, but also an organizational imperative. DevOps is applicable and relevant to any and all organizations that must increase flow of planned work through the technology organization, while maintaining quality, reliability, and security for customers.

“The call to action is this: no matter what role you play in your organization, start finding people around you who want to change how work is performed.”

The DevOps Handbook

This concludes the book club summary for “The DevOps Handbook.” Other book club summaries are available for “The Phoenix Project” and “BDD: Discovery“. Stay subscribed for more book club summaries and other great content on automation & DevOps.

Series Navigation

Leave a Reply

%d bloggers like this: