Welcome!

@DevOpsSummit Authors: Pat Romanski, Liz McMillan, Yeshim Deniz, Elizabeth White, SmartBear Blog

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
@DevOpsSummit at Cloud Expo, taking place November 12-13 in New York City, NY, is co-located with 22nd international CloudEXPO | first international DXWorldEXPO and will feature technical sessions from a rock star conference faculty and the leading industry players in the world.
Without lifecycle traceability and visibility across the tool chain, stakeholders from Planning-to-Ops have limited insight and answers to who, what, when, why and how across the DevOps lifecycle. This impacts the ability to deliver high quality software at the needed velocity to drive positive business outcomes. In his general session at @DevOpsSummit at 19th Cloud Expo, Eric Robertson, General Manager at CollabNet, will discuss how customers are able to achieve a level of transparency that enables everyone from Planning-to-Ops to make informed decisions based on business priority and leverage automation to accelerate identifying issues and fast fix to drive continuous feedback and KPI insight.
More and more brands have jumped on the IoT bandwagon. We have an excess of wearables – activity trackers, smartwatches, smart glasses and sneakers, and more that track seemingly endless datapoints. However, most consumers have no idea what “IoT” means. Creating more wearables that track data shouldn't be the aim of brands; delivering meaningful, tangible relevance to their users should be. We're in a period in which the IoT pendulum is still swinging. Initially, it swung toward "smart for smart's sake," and many brands remain in that corner. But many brands are also gradually opting for more strategic approaches. They're taking a breath and stepping back to examine both existing and potential IoT experiences, asking themselves whether their products lend real value. Once we reach this goal, the implications for personalization are staggering. Consumers will expect devices they use and i...
We all know that end users experience the internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices - not doing so will be a path to eventual business failure. The real and more difficult question, in developing microservices-based applications, is this: What's the best combination of cloud services and tools to use to get the right results in the specific business situation in which you need to deliver what your end users’ want. Considering that new streams of IoT data are already raising the stakes on what end users expect in their mo...
We all know that end users experience the internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices - not doing so will be a path to eventual business failure. The real and more difficult question, in developing microservices-based applications, is this: What's the best combination of cloud services and tools to use to get the right results in the specific business situation in which you need to deliver what your end users’ want. Considering that new streams of IoT data are already raising the stakes on what end users expect in their mo...