The Three Ways describe the values and philosophies that frame the processes, procedures, practices of DevOps, as well as the prescriptive steps.

The “Three Ways" which are the principles that all of the DevOps

The First Way emphasizes the performance of the entire system, as opposed to the performance of a specific silo of work or department — this as can be as large a division (e.g., Development or IT Operations) or as small as an individual contributor (e.g., a developer, system administrator).

The First Way: Flow/Systems Thinking

The Second Way is about creating the right to left feedback loops. The goal of almost any process improvement initiative is to shorten and amplify feedback loops so necessary corrections can be continually made.The outcomes of the Second Way include understanding and responding to all customers, internal and external, shortening and amplifying all feedback loops, and embedding knowledge where we need it.

The Second Way: Amplify Feedback Loops

The Third Way is about creating a culture that fosters two things: continual experimentation, taking risks and learning from failure; and understanding that repetition and practice is the prerequisite to mastery. We need both of these equally. Experimentation and taking risks are what ensures that we keep pushing to improve.

The Third Way: Culture of Continual Experimentation and Learning

In this blog post, I talk about the “Three Ways,” which are the principles that all of the DevOps patterns can be derived from, which we’re using in both the&nbsp;&nbsp;<a href="http://www.itrevolution.com/book/the-devops-handbook/" dir="ltr">“DevOps Handbook”</a> and <a href="https://itrevolution.com/books/novel/" dir="ltr">“The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win.”</a> We assert that the Three Ways describe the values and philosophies that frame the processes, procedures, practices of DevOps, as well as the prescriptive steps.It has been especially fun working on this&nbsp;with fellow co-author Mike Orzen, the most recent winner of the cherished Shingo Prize for his contribution to operational excellence for his book “Lean IT.”The Three Ways are as follows. In a future blog post, I’ll describe the DevOps patterns that can be derived from each.<h2>The First Way: Flow/Systems Thinking</h2><img title="first way" src="https://itrevolution.com/wp-content/uploads/2012/08/first-way2-400x191.png" alt="" width="400" height="191">The First Way emphasizes the performance of the entire system, as opposed to the performance of a specific silo of work or department — this as can be as large a division (e.g., Development or IT Operations) or as small as an individual contributor (e.g., a developer, system administrator).The focus is on all business value streams that are enabled by IT. In other words, it begins when requirements are identified (e.g., by the business or IT), are built in Development, and then transitioned into IT Operations, where the value is then delivered to the customer as a form of a service.The outcomes of putting the First Way into practice include never passing a known defect to downstream work centers, never allowing local optimization to create global degradation, always seeking to increase flow, and always seeking to achieve profound understanding of the system (as per Deming).Read a deeper dive on <a href="https://itrevolution.com/elements-of-the-first-way-and-the-devops-implications/" dir="ltr">The First Way here</a>.<h2>The Second Way: Amplify Feedback Loops</h2><img title="second way" src="https://itrevolution.com/wp-content/uploads/2012/08/second-way1-400x211.png" alt="" width="400" height="211">The Second Way is about creating the right to left feedback loops. The goal of almost any process improvement initiative is to shorten and amplify feedback loops so necessary corrections can be continually made.The outcomes of the Second Way include understanding and responding to all customers, internal and external, shortening and amplifying all feedback loops, and embedding knowledge where we need it.<h2>The Third Way: Culture of Continual Experimentation and Learning</h2><img title="third way" src="https://itrevolution.com/wp-content/uploads/2012/08/third-way-400x224.png" alt="" width="400" height="224">The Third Way is about creating a culture that fosters two things: continual experimentation, taking risks and learning from failure; and understanding that repetition and practice is the prerequisite to mastery.We need both of these equally. Experimentation and taking risks are what ensures that we keep pushing to improve, even if it means going deeper into the danger zone than we’ve ever gone. And we need mastery of the skills that can help us retreat out of the danger zone when we’ve gone too far.The outcomes of the Third Way include allocating time for the improvement of daily work, creating rituals that reward the team for taking risks, and introducing faults into the system to increase resilience.In my follow-up book, <a href="https://itrevolution.com/the-unicorn-project/" dir="ltr">The Unicorn Project</a>, I revisit Parts Unlimited and describe my learnings through the <a href="https://itrevolution.com/five-ideals-of-devops/" dir="ltr">Five Ideals</a>.

Principles that all of the DevOps patterns can be derived from

The Three Ways describe the values and philosophies that frame the processes, procedures, and practices of DevOps.

personaldevelopment

Personal Development

corporateculture

Corporate Culture

problemsolving

Problem Solving

leadershipandmanagement

Leadership & Management

In this blog post, I talk about the “Three Ways,” which are the principles that all of the DevOps patterns can be derived from, which we’re using in both the  <a href="http://www.itrevolution.com/book/the-devops-handbook/">“DevOps Handbook” </a>and <a href="https://itrevolution.com/books/novel/">“The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win.” </a>We assert that the Three Ways describe the values and philosophies that frame the processes, procedures, practices of DevOps, as well as the prescriptive steps.

It has been especially fun working on this with fellow co-author Mike Orzen, the most recent winner of the cherished Shingo Prize for his contribution to operational excellence for his book “Lean IT.”

The Three Ways are as follows. In a future blog post, I’ll describe the DevOps patterns that can be derived from each.

The First Way emphasizes the performance of the entire system, as opposed to the performance of a specific silo of work or department — this as can be as large a division (e.g., Development or IT Operations) or as small as an individual contributor (e.g., a developer, system administrator).

The focus is on all business value streams that are enabled by IT. In other words, it begins when requirements are identified (e.g., by the business or IT), are built in Development, and then transitioned into IT Operations, where the value is then delivered to the customer as a form of a service.

The outcomes of putting the First Way into practice include never passing a known defect to downstream work centers, never allowing local optimization to create global degradation, always seeking to increase flow, and always seeking to achieve profound understanding of the system (as per Deming).

Read a deeper dive on <a href="https://itrevolution.com/elements-of-the-first-way-and-the-devops-implications/">The First Way here </a>.

The Second Way is about creating the right to left feedback loops. The goal of almost any process improvement initiative is to shorten and amplify feedback loops so necessary corrections can be continually made.

The outcomes of the Second Way include understanding and responding to all customers, internal and external, shortening and amplifying all feedback loops, and embedding knowledge where we need it.

The Third Way is about creating a culture that fosters two things: continual experimentation, taking risks and learning from failure; and understanding that repetition and practice is the prerequisite to mastery.

We need both of these equally. Experimentation and taking risks are what ensures that we keep pushing to improve, even if it means going deeper into the danger zone than we’ve ever gone. And we need mastery of the skills that can help us retreat out of the danger zone when we’ve gone too far.

The outcomes of the Third Way include allocating time for the improvement of daily work, creating rituals that reward the team for taking risks, and introducing faults into the system to increase resilience.

In my follow-up book, <a href="https://itrevolution.com/the-unicorn-project/">The Unicorn Project </a>, I revisit Parts Unlimited and describe my learnings through the <a href="https://itrevolution.com/five-ideals-of-devops/">Five Ideals </a>.

The Three Ways: The Principles Underpinning DevOps - IT Revolution

The “Three Ways" which are the principles that all of the DevOps

The First Way: Flow/Systems Thinking

The Second Way: Amplify Feedback Loops

The Third Way: Culture of Continual Experimentation and Learning

CURATED BY

CURATOR'S NOTE

Related collections

More like this