The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations

kaizen blitzes, which are periods when engineers self-organize into teams to work on fixing any problem they want.

The Second Way enables the fast and constant flow of feedback from right to left at all stages of our value stream. It requires that we amplify feedback to prevent problems from happening again, or enable faster detection and recovery.

We also hold internal technology conferences to elevate our skills and ensure that everyone is always teaching and learning.

DevOps is the outcome of applying the most trusted principles from the domain of physical manufacturing and leadership to the IT value stream.

The Third Way enables the creation of a generative, high-trust culture that supports a dynamic, disciplined, and scientific approach to experimentation and risk-taking, facilitating the creation of organizational learning, both from our successes and failures.

“Even more important than daily work is the improvement of daily work.”

In DevOps, we typically define our technology value stream as the process required to convert a business hypothesis into a technology-enabled service that delivers value to the customer.

The First Way enables fast left-to-right flow of work from Development to Operations to the customer. In order to maximize flow, we need to make work visible, reduce our batch sizes and intervals of work, build in quality by preventing defects from being passed to downstream work centers, and constantly optimize for the global goals.

Instead of a culture of fear, we have a high-trust, collaborative culture, where people are rewarded for taking risks.