Welcome!

@DevOpsSummit Authors: Zakia Bouachraoui, Stackify Blog, Jnan Dash, Liz McMillan, Janakiram MSV

Related Topics: @DevOpsSummit, Microservices Expo, Linux Containers, Containers Expo Blog

@DevOpsSummit: Article

ITIL vs. DevOps | @DevOpsSummit #DevOps #ITIL #FedRAMP #Microsevices

Top Takeaways

Earlier this week, we hosted our Continuous Discussion video podcast, this time discussing ITIL and DevOps. The episode featured expert panelists Jan-Joost Bouwman (ING), Kaimar Karu (AXELOS), Jeff Sussna (DevOps writer and speaker) and Simon Morris (ServiceNow). During our discussion, we uncovered the similarities and differences between ITIL and DevOps, and discussed tips for how to align the two methodologies in an organization. Read on for the top highlights, best practices and key takeaways from this week's expert discussion.

Want more #c9d9? Join us every other Tuesday at 10 a.m. PST for free, live episodes of Continuous Discussions video podcast. In the meantime, you can watch every single Continuous Discussion here or on our Youtube playlist. Also, be sure to join us on Tuesday, March 22nd for a special episode of #c9d9 at 5 p.m. PST, live from Mobile Delivery Days conference.

1. Pro tip: You don't have to obey every page of ITIL manuals. Simon Morris says, "Any company which slavishly follows the manual is on the path to nowhere good." In fact, companies should think about adapting any model - whether it is ITIL, DevOps or Agile - to their business needs. In other words, ITIL is the blue pill and DevOps is the red pill - if presented with both, take both.

2. DevOps is more of a mindset of how you want developers and operations to work together in an organization, but it doesn't tell youhow to do your Ops. Solution: "Look at what parts bring value and keep them, and those that don't produce value, lose them." - Jan-Joost Bouwman

3. Why choose ITIL? "It's an antidote to chaos," says Jeff Sussna. ITIL is a good way to get control over what you are doing; however, the danger is when you become too focused on the process. The process tends to get ossified and loses touch with the underlying service premise of ITIL. Keep the focus always on service.

It's not about Dev, Ops, software or servers, it's about the service. Go beyond Dev and Ops when thinking about service. Think about the product/design/support, how we teach people how to use the product and how we get feedback. This gives the ability to evolve a product.

4. The phrase "Incremental ITIL" should not exist - you cannot do that. ITIL should be adopted - in terms of mindset, and adapted - take as much or as little as you need. It's less about the process and more about the organizational capability. - Kaimar Karu

5. DevOps brings back the human factor on two levels: 1) Getting teams to work with each other to solve problems instead of in a queue, and 2) Focuses on automation so that humans can focus on working together. - Jeff Sussna

6. ITIL does not support a culture of learning like Lean or Agile or DevOps - fragile infrastructure companies most likely do not support a culture of learning. People who follow DevOps are more attuned to learning from failure. - Simon Morris

7. Use incident management straight from ITIL, but reserve capacity in sprint planning for operational stuff; for example, use 30% of sprint planning for solving incidents. Items that are ready to go into production should then be checked by an automated CAB.

Dev and Ops should work together and should understand the other persons' skill - but there are still people that are better at coding and people that are better at learning. Let each do what they are best at. - Jan-Joost Bouwman

8. Nine things you should keep in mind for ITIL that also align with DevOps: 1) Focus on value 2) Work holistically 3) Keep it simple 4) Design for experience 5) Progress iteratevly 6) Collaborate 7) Start where you are 8) Observe directly 9) Be transparent. - Kaimar Karu

9. When something goes wrong, ITIL companies tend to think the answer is to add more process. To them, learning means: "How can I get people to do more work to get more work done?" DevOps says "Let's get to the root cause," whether it's lack of infrastructure or available rollback. - Simon Morris

10. If you don't automate, you will never mature - it needs to be step number one. Do not have people doing stuff that can be automated, it creates poor IT and infrastructure. - Anders Wallgren

+Bonus: I don't want a neurosurgeon in the morning doing thoracic surgery in the afternoon. Same goes with DevOps - don't hire someone that can do both on a mediocre level, hire someone that specializes in one or the other. - Anders Wallgren

Watch the replay of the episode for more:

More Stories By Anders Wallgren

Anders Wallgren is Chief Technology Officer of Electric Cloud. Anders brings with him over 25 years of in-depth experience designing and building commercial software. Prior to joining Electric Cloud, Anders held executive positions at Aceva, Archistra, and Impresse. Anders also held management positions at Macromedia (MACR), Common Ground Software and Verity (VRTY), where he played critical technical leadership roles in delivering award winning technologies such as Macromedia’s Director 7 and various Shockwave products.

@DevOpsSummit Stories
Docker is sweeping across startups and enterprises alike, changing the way we build and ship applications. It's the most prominent and widely known software container platform, and it's particularly useful for eliminating common challenges when collaborating on code (like the "it works on my machine" phenomenon that most devs know all too well). With Docker, you can run and manage apps side-by-side - in isolated containers - resulting in better compute density. It's something that many developers don't think about, but you can even use Docker with ASP.NET.
If you are part of the cloud development community, you certainly know about “serverless computing,” almost a misnomer. Because it implies there are no servers which is untrue. However the servers are hidden from the developers. This model eliminates operational complexity and increases developer productivity. We came from monolithic computing to client-server to services to microservices to the serverless model. In other words, our systems have slowly “dissolved” from monolithic to function-by-function. Software is developed and deployed as individual functions – a first-class object and cloud runs it for you. These functions are triggered by events that follow certain rules. Functions are written in a fixed set of languages, with a fixed set of programming models and cloud-specific syntax and semantics. Cloud-specific services can be invoked to perform complex tasks. So for cloud-na...
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex to learn. This is because Kubernetes is more of a toolset than a ready solution. Hence it’s essential to know when and how to apply the appropriate Kubernetes constructs.
In a recent survey, Sumo Logic surveyed 1,500 customers who employ cloud services such as Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP). According to the survey, a quarter of the respondents have already deployed Docker containers and nearly as many (23 percent) are employing the AWS Lambda serverless computing framework. It's clear: serverless is here to stay. The adoption does come with some needed changes, within both application development and operations. That means serverless is also changing the way we leverage public clouds. Truth-be-told, many enterprise IT shops were so happy to get out of the management of physical servers within a data center that many limitations of the existing public IaaS clouds were forgiven. However, now that we've lived a few years with public IaaS clouds, developers and CloudOps pros are giving a huge thumbs down to the...
To enable their developers, ensure SLAs and increase IT efficiency, Enterprise IT is moving towards a unified, centralized approach for managing their hybrid infrastructure. As if the journey to the cloud - private and public - was not difficult enough, the need to support modern technologies such as Containers and Serverless applications further complicates matters. This talk covers key patterns and lessons learned from large organizations for architecting your hybrid cloud in a way that: Supports self-service, "public cloud" experience for your developers that's consistent across any infrastructure. Gives Ops peace of mind with automated management of DR, scaling, provisioning, deployments, etc.