5 Common Misconceptions About DevOps

DevOps

DevOps is a transformative operational concept designed to help development and production teams coordinate operations more effectively. In theory, DevOps software is designed to be focused on cultural changes that stimulate collaboration and efficiency, but the focus often ends up being placed on everyday tasks, distracting organizations from the core principles - and value - that DevOps is built around. This has led to many technology professionals developing misconceptions about DevOps because they have been part of deployments - or know people who have been involved in DevOps plans - that strayed from the core principles of the movement.

This struggle is understandable. Cultural changes are abstract measures that, when delivered effectively, lead to process innovation and significant value creation. That's the aim with DevOps. However, not everybody will buy into cultural adjustments and be comfortable with the idea of adjusting how they work. This leads organizations to respond with strict procedural guidelines that sometimes detract from the results of movements like DevOps. Five common misconceptions that emerge from this kind of environment include:

1. DevOps Doesn't Work With ITIL Models
The IT Infrastructure Library creates seemingly rigid best practices to help organizations create stable, controllable IT operations. DevOps is built around creating a continual delivery environment by breaking down longstanding operational silos. It would seem that these two principles are contradictory, but ITIL gets a lot of bad press that it doesn't deserve. The reality is that ITIL features lifecycle management principles that align naturally with what organizations are trying to achieve through DevOps.

2. ITIL is too Rigid for DevOps
The core process models of ITIL and DevOps can work together, but some people think that even if you can make the marriage work, it will fall apart because ITIL is so rigid and DevOps focuses on giving users flexibility to work in whichever way works best for them. There may be some conflict here, but ITIL has been changing in recent years. ITIL is increasingly being fine tuned into a set of key guidelines, not rigid rules that organizations need to abide by for comprehensive ITIL integration. You can pick and choose how to implement the technology. This gives ITIL the flexibility needed to work within a DevOps environment.

3. DevOps Emphasizes Continuous Change
There's no way aound it - you will need to deal with more change and release tasks when integrating DevOps principles into your operations - the focus is placed heavily on accelerating deployment through development and operations integration after all. This perception comes out of DevOps' initial popularity among web app developers. "DevOps for Dummies" explained that most businesses will not face change that is so frequent, and do not need to worry about continuous change deployment just because they are supporting DevOps.

{{cta('2837f107-ea5e-4770-b95c-c9c4e46c0241')}}

4. DevOps Forces Developers to Bail out Operations Teams
This misconception is often the result of DevOps deployments that don't go so well. If your DevOps tools end up boiling down to production teams complaining that an app is causing compatibility issues and needs to be changed, you aren't really doing DevOps correctly. The goal is to get both teams to work constructively to build apps with the production configuration in mind and bring development-related knowledge into the final push to release.

5. DevOps Eliminates Traditional IT Roles
If, in your DevOps environment, your developers suddenly need to be good system admins, change managers and database analysts, something went wrong. DevOps as a movement that eliminates traditional IT roles will put too much strain on workers. The goal is to break down collaboration barriers, not ask your devs to do everything. Specialized skills play a key role in support effective operations, and traditional roles are valuable in DevOps.

ITIL and IT service management principles in general do not need to be a barrier to DevOps use. Understanding these misconceptions and avoiding falling prey to them can help you align ITSM tactics and DevOps to create maximum value.

Previous Article
4 Preliminary Steps to Take Before Implementing DevOps
4 Preliminary Steps to Take Before Implementing DevOps

The DevOps movement is an up and coming set of strategies and ideologies that leverage the concept of con...

No More Articles