Gartner Blog Network

Getting Your Arms Around DevOps – DevOps Patterns and Practices

by Cameron Haight  |  October 13, 2014  |  7 Comments

I receive lots of inquiries from our clients around the subject of “what is DevOps?” Their interest goes beyond needing a simple definition to wanting to know what constitutes it. After much searching, I couldn’t find exactly what I was looking for so I developed the graphic below awhile ago that I now use in some of my presentations. I’ve shared this with several of my Gartner colleagues as well as a few notable DevOps thought leaders. For example, Andrew Clay Shafer ( thinks a Euler diagram ( might be a better representation, however, I’m not sure that this shows dependencies as well (although it certainly would make for a cleaner depiction). In any case, feel free to let me know what you think – I’m certainly open to suggestions. Thanks …

Update: I’m re-posting with a larger graphic that will hopefully help.


Additional Resources

View Free, Relevant Gartner Research

Gartner's research helps you cut through the complexity and deliver the knowledge you need to make the right decisions quickly, and with confidence.

Read Free Gartner Research


Cameron Haight
Research VP
10 years at Gartner
30 years IT industry

Cameron Haight is a research vice president in Gartner Research. His primary research focus is on the management of server virtualization and emerging cloud computing environments. Included in this effort is… Read Full Bio

Thoughts on Getting Your Arms Around DevOps – DevOps Patterns and Practices

  1. DevOps looks complicated. Maybe they should simplify architecture patterns by abstracting away the application through private PaaS and containers like Docker.

  2. Cameron Haight says:

    Like perhaps also with Apprenda, Chris? 😉 DevOps is not just about (technology) architecture as I’m sure you know – but also people, process and culture. It can be as simple or as “complex” as needed in order to solve the problem domain for the organization. Hopefully we can limit the amount of “accidental” complexity that often manifests itself as part of the solution.

  3. Dhruv Gupta says:

    This is a welcome initiative. There is no blueprint for devops and CD best practices. It would definitely be useful to simplify the chart, or highlight the key ingredient in each of the people, tech, process, culture aspect. Would love a pointer to one of your decks that affords more context to this graphic.

  4. Cameron Haight says:

    Hi Dhruv. Thanks for the comments. Right now it pretty much stands alone although I go into more detail on specific areas such as continuous delivery, etc., in my presentation.

  5. Hi Cameron,

    Thank you very much for sharing your graphical overview of DevOps. Much appriciated!
    As I am in the middle of creating a DevOps organisation, I could really use such a picture to show my organisation (in a different way) what we are talking about. Do you perhaps have such a picture in a higer resolution (for me not everything on this picture is readable).

    Many thanks in advance!

    Kind regards,


  6. Dhruv Gupta says:

    Yes, a high resolution image would be much appreciated!

  7. Cameron Haight says:

    Hopefully the new graphic is more readable although it makes the page look a bit unsightly.

Comments are closed

Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.