04 – 08 November 2018 / Barcelona, Spain
Hype Cycle for DevOps
Joachim Herschmann
© 2018 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. and its affiliates. This publication may not be reproduced or distributed in any form
without Gartner's prior written permission. It consists of the opinions of Gartner's research organization, which should not be construed as statements of fact. While the information contained in this
publication has been obtained from sources believed to be reliable, Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information. Although Gartner research
may address legal and financial issues, Gartner does not provide legal or investment advice and its research should not be construed or used as such. Your access and use of this publication are
governed by Gartner’s Usage Policy. Gartner prides itself on its reputation for independence and objectivity. Its research is produced independently by its research organization without input or
influence from any third party. For further information, see "Guiding Principles on Independence and Objectivity."
Hype Cycle for DevOps
The DevOps Hype Cycle includes key technologies and
activities used to support a DevOps initiative.
DevOps practitioners and IT leaders should identify
DevOps technology and process focus areas, and then
map them against Gartner’s Hype Cycle to get an
understanding of both capabilities and maturity.
1 © 2018 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. and its affiliates.
Explaining the Hype Cycle Stages
Expectations
The trend technology The trend is established
failed to achieve as a driver for change
The trend is hyped to unrealistic hyped in institutional memory
be a main driving expectations and action
force for change
A new trend starts to be
highlighted in the press An understanding of the
real and relative impact
of the trend is building
Peak of
Innovation Inflated Trough of Plateau of
Trigger Expectations Disillusionment Slope of Enlightenment Productivity
Time
2 © 2018 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. and its affiliates.
DevOps in Gartner’s Hype Cycle
2015
2016
2017
Expectations
2013
2018
2009
First “DevOps” days
Innovation Peak of Trough of Slope of Plateau of
Trigger Inflated Disillusionment Enlightenment Productivity
Expectations
Time
Note: This chart is a composite, derived from Gartner published Hype Cycles. The particular combination and comparison of items made
here have not been reviewed by Gartner.
3 © 2018 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. and its affiliates.
Hype Cycle for DevOps
From “Hype Cycle for DevOps, 2018” 24 July 2018 (G00338456)
4 © 2018 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. and its affiliates.
Production metrics (SLAs/SLOs) and feedback
Requirements definition (use case, prototyping) Scheduled/
Identify Business metrics (e.g., shopping cart performance,
resolution times, customer satisfaction)
Timed release
Release coordination
DevOps Activities
Update release metrics
New feature/function priorities and fixes
Deploy application
Deployment status
Design Release plan (timing, business case) Change controls
(software, configuration) Security policy, adherence and requirements Fallback/Recovery
Code, code merge, code
quality and performance
Build, build performance
Functional test
Create release candidate
IT infrastructure
agile provisioning and
configuration
(including — storage,
Acceptance test database, network)
Regression test Application
Static analysis provisioning
(quality and compliance) and configuration
Security analysis
(vulnerability)
Performance test Autorelease (e.g., application release is Production load metrics gathering
Defect status automatically pushed) Release measured against test metrics and
Configuration test Triggered release (e.g., upon a ready state expected value
Release test being achieved) End-user response and experience
Release staging/holding IT infrastructure, network, application
Release approval/preapproval performance and availability
Release package configuration (if required)
5 © 2018 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. and its affiliates.
Hype Cycle for DevOps
Transformational
five to 10 years
High
Less than two years
From “Hype Cycle for DevOps, 2018” 24 July 2018 (G00338456)
6 © 2018 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. and its affiliates.
Priority Matrix for DevOps
benefit years to mainstream adoption
less than 2 years 2 to 5 years 5 to 10 years more than 10 years
transformational Communities of Practice
Continuous Delivery
DevOps Toolchain
DevOps Toolchain Orchestration
Enterprise-Class Agile Development
high Agile Application Testing Services Agile Ops Application Release Orchestration
Citizen Developers Application Performance Monitoring Suites Behavior-Driven Development
Test Data Management Bimodal IT Operations Chaos Engineering
Continuous Quality Continuous Configuration Automation
Mediated APIs Continuous Experience
Microservices DevSecOps
Post-Scrum Methodologies IMC-Enabled Hyperscale Application
Architecture
Software-Defined Infrastructure
Mobile DevOps Tools
moderate Miniservices Cloud Management Platforms Site Reliability Engineering (SRE)
Container Management
Crowdtesting
Software-Defined Networking
low
As of July 2018
From “Hype Cycle for DevOps, 2018” 24 July 2018 (G00338456)
7 © 2018 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. and its affiliates.
Recommended Gartner Research
Hype Cycle for DevOps, 2018
George Spafford and Joachim Herschmann (G00338456)
Top 5 Causes of DevOps Failure and How to Avoid Them
George Spafford and Christopher Little (G00345524)
How to Successfully Scale Enterprise DevOps Initiatives
George Spafford (G00310133)
Top SRE Practices Needed by Teams Scaling DevOps
George Spafford, Christopher Little and Mark Jaggers (G00358184)
Build Continuous Quality Into Your DevOps Toolchains
Jim Scheibmeir, Thomas Murphy and Others (G00349594)
For information, please contact your Gartner representative.
8 © 2018 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. and its affiliates.
