<p>I'm ITIL certified (though it has been a while.)  I agree with Tensibai: ITIL and DevOps aren't <em>incompatbile</em>, but that doesn't necessarily make them great friends.</p>

<p>The argument can be made that the processes in ITIL must happen in some way, especially for larger organizations.  Successful integration of DevOps practices, where ITIL is already practiced, requires careful planning, communication, and execution.  Then again, that's true of any DevOps Transformation.</p>

<p>For a "greenfield" transformation where neither ITIL or DevOps are in place, I'd craft a combination of both using "mapped" terminology as you have described.  As long as everyone in the organization is on the same page, using the same language, ITIL and DevOps can add value when combined.</p>

CC BY-SA 3.0
2017-03-02T13:05:09.377Z
2017-03-02T13:05:09.377Z
Dave Swersky
<p>I liked the answers provided by the <a href="http://www.itskeptic.org" rel="nofollow noreferrer">IT Skeptic</a> on an <a href="http://devopscafe.org/show/2013/3/25/devops-cafe-episode-40.html" rel="nofollow noreferrer">episode</a> of <a href="http://devopscafe.org" rel="nofollow noreferrer">DevOpsCafe.org</a> If I remember it correctly, his line of thinking is that if you actually really understand ITIL, there is very little conflict. That most of ITIL guidelines are very general and that the conflicts are largely between some implementations of ITIL, not behind the actual specification.</p>

CC BY-SA 3.0
2017-03-02T16:02:52.600Z
While the link may answer the question, if it break your answer makes no sense. It would be good to summarize the idea with your own word in your answer, keeping the link to extend it.
Tensibai
CC BY-SA 3.0
2017-03-02T16:16:17.173Z
I'll re-listen the episode and summarize it here shortly.
Jiri Klouda
CC BY-SA 3.0
2017-03-02T16:00:21.553Z
2017-03-02T16:45:21.267Z
2017-03-02T16:45:21.267Z
Jiri Klouda
<p>In my opinion, the DevOps culture come along with a methodology change toward <a href="https://en.wikipedia.org/wiki/Agile_software_development" rel="noreferrer">Agile</a> process management.<br>
ITIL is heavily aimed at a clear formalism of the process and the results and thus more adapted to a <a href="https://en.wikipedia.org/wiki/Waterfall_model" rel="noreferrer">Waterfall</a> model.</p>

<p>This doesn't mean ITIL is incompatible with Devops, but usually this will be two separate process with different timelines. 
I mean that the inclusion of a new product within ITIL referential will usually be delayed until the product/application has been released in production for a while, where early pitfalls and some documentation needed to integrate ITIL has been done and adapted after the product is "live".</p>

<p>One of the thing in ITIL is the Service Design, which is assumed to be defined before any development task, an agile process will/may review the design in each iteration, breaking the formalism needed in an ITIL process.</p>

<p>The main goal of ITIL is, as you said, to provide a framework to ensure nothing is omitted between the design/conception and maintenance phase (Build/Run).  In a devops culture, the whole team is responsible of all phases on long term, hence why the formalism is reducted.</p>

<p>That doesn't mean we have to forget ITIL, the core principles are absolutely good and, in my opinion, should be used as a checklist to build the initial backlog of a product.
It's just that following the ITIL principle with all its formalism goes against the time to market reduction goal of a quick iterative software development and sometimes is not even applicable as there's less transmission of information needed between teams, as the tasks are done by the same team.</p>

CC BY-SA 3.0
2017-03-02T12:20:19.400Z
Or, to give a more complete answer to the OP:
It depends on how closely you want to follow both structures. Can they be implemented at the same time? Yes, absolutely, but they both have some mutually exclusive points. If you want to implement both, which I try to do in my org, then it's all about finding the right balance.
kazaamjt
CC BY-SA 3.0
2017-03-02T12:14:11.207Z
2017-05-10T13:45:59.800Z
2017-05-10T13:45:59.800Z
Tensibai
<p>In my career, I have been both a software developer and <a href="https://en.wikipedia.org/wiki/ITIL" rel="noreferrer">ITIL</a> practitioner in an operations role. Thus DevOps was a natural progression for me.<br>
However, I have always struggled with the highly specialised language that ITIL introduces and making that "Developer Friendly" enough to not be a complete turn off to developers.</p>

<p>ITIL is an internationally recognised IT Service Management framework that has been developed over 30 years as a set of practices that have a proven benefit to the operational stability and maturity of an organization.</p>

<p>Is DevOps truly compatible with ITIL, or in essence do we need to take the spirit of ITIL and "translate" it to language that is better understood by development teams:</p>

<ul>
<li>Incident &amp; Problem Management → Production Defects, Bugs or Issues</li>
<li>Change &amp; Release Management → Continuous Delivery</li>
<li>Event Management → Logging, Telemetry, Instrumentation and Alerting</li>
</ul>

CC BY-SA 3.0
2017-03-07T13:51:26.950Z
@RichardSlater As you have not accepted an answer already, is there something missing in the answers above or just that you don't wish to accept one at all ?
Tensibai
CC BY-SA 3.0
2017-03-02T11:00:14.390Z
Possible to expand what ITIL is? Pretty sure some folks (like me) don't know about it :)
Dawny33
CC BY-SA 3.0
2017-03-02T12:06:01.073Z
Good call, I have updated the question and accepted an edit with a link to the Wikipedia Page - thanks everyone for your improvements.
Richard Slater
<terminology><itil><operations>
Is DevOps compatible with ITIL?
Richard Slater
# Is DevOps compatible with ITIL?

(Asked by: username_0 on 2017-03-02)

In my career, I have been both a software developer and [ITIL](https://en.wikipedia.org/wiki/ITIL) practitioner in an operations role. Thus DevOps was a natural progression for me.  
However, I have always struggled with the highly specialised language that ITIL introduces and making that "Developer Friendly" enough to not be a complete turn off to developers.

ITIL is an internationally recognised IT Service Management framework that has been developed over 30 years as a set of practices that have a proven benefit to the operational stability and maturity of an organization.

Is DevOps truly compatible with ITIL, or in essence do we need to take the spirit of ITIL and "translate" it to language that is better understood by development teams:

* Incident & Problem Management → Production Defects, Bugs or Issues
* Change & Release Management → Continuous Delivery
* Event Management → Logging, Telemetry, Instrumentation and Alerting

**Tags:** terminology, itil, operations

> **Comments:**
> **username_2**: Possible to expand what ITIL is? Pretty sure some folks (like me) don't know about it :)  
> **username_0**: Good call, I have updated the question and accepted an edit with a link to the Wikipedia Page - thanks everyone for your improvements.  
> **username_1**: @RichardSlater As you have not accepted an answer already, is there something missing in the answers above or just that you don't wish to accept one at all ?  

---

## 3 answers

### Answer by username_1 on 2017-03-02. Score: 26 | Accepted answer

In my opinion, the DevOps culture come along with a methodology change toward [Agile](https://en.wikipedia.org/wiki/Agile_software_development) process management.  
ITIL is heavily aimed at a clear formalism of the process and the results and thus more adapted to a [Waterfall](https://en.wikipedia.org/wiki/Waterfall_model) model.

This doesn't mean ITIL is incompatible with Devops, but usually this will be two separate process with different timelines.
I mean that the inclusion of a new product within ITIL referential will usually be delayed until the product/application has been released in production for a while, where early pitfalls and some documentation needed to integrate ITIL has been done and adapted after the product is "live".

One of the thing in ITIL is the Service Design, which is assumed to be defined before any development task, an agile process will/may review the design in each iteration, breaking the formalism needed in an ITIL process.

The main goal of ITIL is, as you said, to provide a framework to ensure nothing is omitted between the design/conception and maintenance phase (Build/Run). In a devops culture, the whole team is responsible of all phases on long term, hence why the formalism is reducted.

That doesn't mean we have to forget ITIL, the core principles are absolutely good and, in my opinion, should be used as a checklist to build the initial backlog of a product.
It's just that following the ITIL principle with all its formalism goes against the time to market reduction goal of a quick iterative software development and sometimes is not even applicable as there's less transmission of information needed between teams, as the tasks are done by the same team.

> **Comments:**
> **username_5**: Or, to give a more complete answer to the OP: It depends on how closely you want to follow both structures. Can they be implemented at the same time? Yes, absolutely, but they both have some mutually exclusive points. If you want to implement both, which I try to do in my org, then it's all about finding the right balance.  

---

### Answer by username_3 on 2017-03-02. Score: 9

I'm ITIL certified (though it has been a while.) I agree with username_1: ITIL and DevOps aren't *incompatbile*, but that doesn't necessarily make them great friends.

The argument can be made that the processes in ITIL must happen in some way, especially for larger organizations. Successful integration of DevOps practices, where ITIL is already practiced, requires careful planning, communication, and execution. Then again, that's true of any DevOps Transformation.

For a "greenfield" transformation where neither ITIL or DevOps are in place, I'd craft a combination of both using "mapped" terminology as you have described. As long as everyone in the organization is on the same page, using the same language, ITIL and DevOps can add value when combined.


---

### Answer by username_4 on 2017-03-02. Score: 0

I liked the answers provided by the [IT Skeptic](http://www.itskeptic.org) on an [episode](http://devopscafe.org/show/2013/3/25/devops-cafe-episode-40.html) of [DevOpsCafe.org](http://devopscafe.org) If I remember it correctly, his line of thinking is that if you actually really understand ITIL, there is very little conflict. That most of ITIL guidelines are very general and that the conflicts are largely between some implementations of ITIL, not behind the actual specification.

> **Comments:**
> **username_1**: While the link may answer the question, if it break your answer makes no sense. It would be good to summarize the idea with your own word in your answer, keeping the link to extend it.  
> **username_4**: I'll re-listen the episode and summarize it here shortly.  

---

