5 reasons your DevOps initiative could fail, and how to avoid them

Through 2023, 90% of DevOps initiatives will fail to fully meet expectations due to the limitations of leadership approaches, not technical reasons. The value in adopting DevOps practices is vast, but if initiatives are to be successful, organizations must approach them in the right way.

 

Any early failure of DevOps efforts will make additional organizational changes that DevOps requires even more difficult and unlikely. I&O leaders must recognize the most common causes of DevOps failures and offers guidance on how to avoid these pitfalls.

 

So, what are the main reasons for DevOps failure, and can they be avoided? Here are a few points that infrastructure and operations leaders can keep in mind while introducing DevOps.


ChallengeDevOps not grounded in customer value

 

It is critical to understand the business outcome of introducing DevOps. Staff and customers, both, need to have a finger on the value it will bring.

 

Recommendation: I&O leaders can rely on marketing to identify, anticipate and deliver the value of DevOps. By refining their understanding of customer value, I&O leaders can evolve capabilities and further enable organizational change.


Challenge: Organizational change not managed

 

Many organizations focus efforts on DevOps tools and disregard the magnitude of getting their staffs on board with the upcoming change.

 

Recommendation: Organizations must identify and nurture candidates with the right DevOps attitude. Those who demonstrate teamwork, accountability and lifelong learning show the most potential.


Challenge: Lack of collaboration

 

More often than not, DevOps efforts are limited to I&O. If all stakeholders are not involved, or DevOps in implemented through uncoordinated groups, it will not bring value.

 

Recommendation: Build an environment that fosters collaboration and breaks down barriers. Teams must be encouraged to work together, rather than in uncoordinated silos.


Challenge: Trying to do too much too quickly

 

DevOps cannot be launched in one step without increasing chances of failure. There are far too many variables for this method to be successful in a large IT organization.

 

Recommendation: A methodical, step-by-step approach to implement DevOps allows an organization to course correct and focus on continual improvements.


Challenge: Unrealistic expectations of DevOps

 

Many organizations struggle with closing the gap between expectations of customer value and what it can actually deliver.

 

Recommendation: By agreeing on objectives and metrics at the start can help manage expectations better. Remember, expectation management is continuous and not a one-time affair.


To learn more about how you can get the most from your DevOps initiative, join us at Gartner IT Infrastructure, Operations & Cloud Strategies Conference 2019, 6 – 7 May, Mumbai, India.

Sign up to be notified when the agenda is live.

Thank You, Please add the domain @gartner.com to your safe sender list to ensure receipt of future email.
Thanks for the subscription.
Error occurred in submitting the form. Please try again!
Error occurred in submitting the form. Please try again!
Thank You, Please check your inbox to confirm your subscription and add the domain @gartner.com to your safe sender list to ensure receipt of future email.

Experience the Gartner Difference.