“Fireside Chat”: DevOps-Driven ITIL Transformation – SKILup Days 2024

Hey, uh, welcome to today's session, uh, fireside chat on DevOps driven ITIL transformation. I'm Mark Hornby, CEO and principal consultant at Engineering DevOps Consulting and Rio. He's a founder of Analytica, uh, Monterey, and an ITIL master.

We're grateful for the opportunity to speak at this text on learning scale up event and hope you'll enjoy your talk and learn something along with the other talks today. Victoria, uh, how about you introduce yourself for the topics and the topics of this talk? Absolutely.

Hello, mark. In our chat, mark and I will explore the powerful convergence ofop and IT practices and how organizations can leverage this to improve service delivery, agility, and operational efficiency. We'll cover several topics starting with aligning DevOps with IT core principles followed by, uh, cases study of, uh, successful DevOps driven IT transformation.

We'll also dive into actionable strategies for integration, discuss how automation and CI and CD can streamline IT value streams and close with an interactive discussion on challenges, insights, and tools to simplify implementation. So let's get started and learn how combining IT and DevOps can take your service management to the next level. Let's start by discussing how IT and DevOps align it, as we know, is a set of practices for IT service management that focuses on delivering value through well FIN models and systems.

It emphasizes structured service management, governance, and continual improvement. Among rs. One of IT historical key strengths.

It's focus on stability and reliability, ensuring that services are delivered efficiently and predictably. However, traditional IT practices can sometimes feel rigid when compared to the fast-paced iterative nature of DevOps. There is a clear intention on the latest version of it to evolve to include new approaches like agile and win, but there are still more opportunities together with DevOps strengths.

Hey, that's a great point, Victoria. DevOps, on the other hand, it's all about speed collaboration automation where ITIL emphasizes control. DevOps promotes flexibility.

This brings development and operations together rapidly to deliver value. However, that doesn't mean the two are incompatible. In fact, DevOps compliments ITIL by driving faster delivery cycles while maintaining quality through practices like continuous integration, continuous delivery deployment.

CICD DevOps automates much of the manual repetitive work that can slow down traditional ITIL processes. Exactly, mark, it's guiding principles like focus on value and optimize and automate actually fits very well with DevOps. For example, it emphasizes understanding customer needs, which is also central to DevOps.

The continuous feedback loops that DevOps introduces can provide real time insight into service delivery performance, which is valuable for ideal continual improvement efforts. Yes, and if you look at automation, one of DevOps strength is it directly supports ITIL L'S goal of efficiency. By automating processes like incident management change control, we reduce human error and speed up response times.

So with DevOps, ITIL practice can become more agile without sacrificing the control and governance that ITIL brings, And that's why the two can work in harmony. By aligning DevOps practices with it's core principles, organizations can create a balanced approach that the chiefs both speed and, uh, stability and AI tools can enhance this alignment by further automating and optimizing workflows. Yeah, that's a good point.

So I couldn't agree more. Victoria. The convergence of DevOps and ITIL allows organizations to innovate faster with less risk and still maintain a strong governance and framework.

Uh, we're st we're just scratching the surface on how it, how AI can take this to the next level. Now let's explore a real world case study where an organization successfully integrated DevOps into their IT practice using AI augmented tools. This example highlights how combining the best of both approaches leads to tangible improvements.

The example comes from, uh, financial service services company that faced challenges with slow change cycles and frequent incidents during peak operational periods. By implementing DevOps practices like continuous delivery and leveraging AI for automation, they were able to reduce their change cycle time by 40% while improving overall service stability. Yeah, and, and what's remarkable in that case is how DevOps enabled faster incident resolution through improved observability and monitoring.

By embedding observability directly into the systems using service components as code, the company was able to detect issues in real time, thus speeding up the meantime to resolution by as much as 30%. They also adopted a test-driven TDD approach, which allowed them to catch potential issues earlier in the service lifecycle, thereby reducing development failures, deployment failures, I should say. Exactly.

Mark. Um, what stands out here is how the combination of AI and DevOps enhance their IT practices. AI augmented tools provided real time data insights that fit directly into their problem management workflows, allowing them to proactively address issues before they escalate it.

These proactive monitoring combined with, uh, DevOps cultural rapid feedback allowed the teams to not only resolve incidents faster, but also prevent them from happening in the first place. Yeah, that's why the transformation is so impactful. The company went from reactive to proactive service management.

They could use AI to predict and pre, uh, excuse me, prevent incidents while DevOps gave them the ability to implement fixes and improvements almost immediately. This also highlights the value of adopting a test driven approach. TDD integrated with AI enabled tools helped them validate every service change before it hit production, which reduced overall risk and improved system reliability.

This example shows that combining develops with ai, augmented, IT practices leads to measurable improvements where whether it is it's faster incident resolution reduces a change cycle times or, or better monitoring and observability. The key takeaway is that DevOps can enhance IT practices to deliver faster, more reliable services. And with the integration of ai, we can take those efficiencies even further.

Absolutely. Victoria, and in this case study now shows that the convergence of DevOps and ITIL isn't just theoretical. It's happening now with real world results.

By fostering collaboration, automating routine tasks, leveraging AI organizations can drive both agility and stability in their IT operations. Next, let's talk about actionable strategies for integrating DevOps into IT value streams. One of the key things to remember is that while DevOps is fast and agile, it is structure and heavily process driven.

The challenge is finding the right balance so that the organizations can benefit from both. One best practice we have seen is embedding DevOps into the incident and control change control practices by automating parts of these value streams. Using AI teams can resolve incidents faster while still maintaining governance and control.

Yeah, that's right. Victoria. One practical strategy is to start by mapping DevOps processes like continuous integration and continuous delivery directly into ITIL value streams.

For instance, in change management, you can automate the validation and approval processes using pipelines that tests and verify changes before they're deployed. ai augmented tools can further enhance this by analyzing historical incident data to predict prudential risks, allowing teams to prevent issues before they happen. This enables rapid but safe delivery.

Exactly. What we often see is organizations adopting a phase approach to integration, start small, perhaps with automating change approvals or incident classification, and then scales as the benefits become clear. AI tools play a key role here by streamlining routine tasks like categorizing incidents or analyzing logs for root causes.

This reduces the workload of on service desk, allowing IT teams to focus to more on more complex issues. Over time, these smaller changes, creating a more efficient IT workflow that still adheres to the core, core IT principles. Yeah, I was thinking about that.

A phased approach is ideal for scaling the transformation across an organization. Another critical framework to consider is the use of service level objectives, SLOs and service level indicators from site reliability engineering, these metrics can be embedded into it's problem and incident management policies to ensure that services meet performance targets. By continuously monitoring and measuring SLOs, teams can ensure both speed and reliability are maintained as part of the service delivery pipeline.

This data also feeds into continual improvement practices within itil. That's a great point. Mark.

Using frameworks like SLOs and SLIs provides a clear way to quantify service performance and a light deep with business goals. Another best practice is fostering cross-functional collaboration between DevOps teams and IT practitioners. Having shared goals and responsibilities is critical.

For example, when both teams collaborating incident management, they can respond more quickly with the DEVO teams using that automated tools to mitigate the incident while the ITIL team ensures prepare adherence to practices and governance. Yeah, I agree. Collaboration is key and when it comes to scaling frameworks like safe can help ensure that the integration of DevOps and ITIL isn't limited to one part of the organization.

By using frameworks designed to large scale environments, companies can replicate the success of smaller pilot projects across multiple teams and departments. This ensures that both agility and governance are maintained throughout the organization. Yes, and don't forget about the importance of training and education.

For DevOps to truly enhance practices, IT practitioners need to understand how automation and AI tools can support the work. Providing continuous training ensures that the entire organization is aligned with the transformation effort. This not only accelerates adoption, but also helps in identifying new opportunities for for improving value streams.

Agreed. Yeah. The more the empowered the teams are with the right tools and knowledge, the faster they can drive improvements.

Whether it's automated tasks using AI to predict and prevent issues or leveraging SLOs and SLIs to measure success, the goal is always the same rapid, reliable service delivery that's scalable and secure. Absolutely. Automation is one of the most impactful ways to streamline IT.

Value streams, particularly when it comes to incident and change control in it. These practices are traditionally very structured and require several approval and checks to ensure that normal changes are made careful. But as organizations move towards faster service delivery, manual processes can become a bottleneck.

This is where automation and continuous iteration and continuous delivery pipelines come into play, allowing us to maintain the integrity of IT practices while speeding up the process. That's right. Yeah.

Uh, CICD is a cornerstone of DevOps and it can dramatically improve ITIL value streams and CI developers frequently merge code into shared repositories and automated tests are run to ensure the code is stable. This practice reduces the chance of large risky changes being introduced. CD takes it a step further by ensuring that every code change is automatically tested and validated and ready for deployment.

When applied to ITIL practices. CICD helps automate the testing and approval changes, reducing human intervention and speeding up feedback loops. Exactly.

Mark. In incident management, for example, automation can help teams de to detect and resolve incidents faster. By integrating monitoring and observability tools, AI augmented tools can analyze system logs, identify patterns, and predicts potential issues before they escalate into incidents.

This not only improves incident response times, but also enhances problem management By feeding insights back into the system in change control automation can ensure that changes are automatically validated and roll it out without waiting for manual approvals at each each stage leading to a higher volume of standard changes. Good point. I mean, automation is also key to faster feedback loops, which are essential for both incident and change control.

In DevOps, CICD pipelines allow us to continuously monitor and test our systems, providing immediate feedback when something goes wrong. This concept directly benefits itil. For example, instead of waiting for a weekly change review, uh, automated pipelines can test and validate changes in real time, providing fast actionable feedback to both developers and operations teams.

And AI augmented tools can further enhance this by suggesting the best course of action based on the past incident data. That's a great point. Mark.

AI is really revolution how the we approach these processes. AI augmented tools can categorize and prioritize incidents based on severity, predict potential service orders, and even automate the initial response like the starting services or rerouting traffic. For example.

This level of automation enables IT teams to handle incidents and changes faster without compromising the governance that IT man mandates. The result is reduce incident resolution times faster, change implementations, and improved overall service reliability. Yes, and you know, the beauty of CICD in this context is that it doesn't just automate the technical side of change control, it also facilitates continuous improvement.

Every change is validated through automated testing and every failure is analyzed through automated feedback loops, ensuring that issues are addressed immediately. This not only speeds up the deployment process, but also ensures that the quality of service remains high. AI tools can further support this by continuously monitoring existing performance and making adjustments in real time to prevent incidents before they occur.

Yes, and let's not, not forget also about the cultural shift that comes with automation. For example, ideal in IT changes considered as normal, often involves multiple handoffs, but with DevOps and automation teams can collaborate more effectively. These aligns with ideals focus on continual improvement as teams can learn from each automated cycle and use those lessons to improve the next one.

By leveraging both automation and ai, we can streamline IT value streams without sacrificing control or governance. Exactly. The combination of CICD pipelines and AI augmented tools, tools creates a faster, more reliable system where ITIL principles are not only maintained but enhanced.

This allows teams to focus less on manual processes and more on innovation service delivery and achieving the best of both worlds speed and stability. Correct. Let's talk about some of the challenges that organizations face when trying to implement a DevOps driven IT strategy and the tools and resources that can simplify the transformation.

One of the biggest challenge that I have seen is the resistance to change, particularly from teams who are used to, to the more traditional IT framework, especially with those previous versions of IT before the current version, which has changed it significantly. It can be hard to move from a process heavy governance focused approach to a more agile fast moving model like Devo. Indeed.

You know, resistance to change is a common challenge in any transformation, especially when it involves integrating something like DevOps into itil, which has been the backbone of many organizations for years. The one key insight here is to start with small manageable changes. You don't need to transform everything overnight.

Start with automating one part of your practices like incident management or change approvals and then scale from there. The gradual approach helps teams see the value without feeling overwhelmed. Yeah, that's a great approach.

Mark. Another challenge I often see is the complexity of aligning DebOps tools and workflows with the IT framework. DebOps typically emphasizes speed and accessibility while it was traditionally associated with control and governance.

Current version aims to include agile, lean, and DevOp Dev develops concepts, but it is not enough. Bridging that gap can be difficult without the right tools. Fortunately, there are AI augmented tools that can help.

For instance, AI can automate risk assessments and approvals, ensuring that speed doesn't come at the cost of quality or control. The key is finding tools that can integrate well with both DevOps and IT systems. Yeah, it's pretty clear, you know, there's a growing range of tools that can help with this integration.

For instance, CI ICD platforms like Jenkins or GitLab, CI can be set up automatically to handle change approvals, test environments, deployments. At the same time adhering to ITIL control practices while integrated with monitoring tools like Prometheus Elk Stack. These platforms can automatically trigger responses to INS, incidents or changes.

Then you add in tools like Dynatrace and Splunk's AI driven insights, and you get a system that not only detects and reacts to issues faster, but also learns from past incidents to prevent future ones. And that bring us, bring us to the next point. Simplification.

A common challenge is that organizations of complicated process by using too many disjointed tools or failing to integrate them properly, one of the best strategies is to standardize on a few key platforms that integrate seamlessly into both DevOps and value streams. Tools like ServiceNow for example, are we were suited for this. It can manage many of the IT practices like incident and problem management, change control, while also integrating with DevOps pipelines to automate those practices.

Yeah, for sure. Simplifying tool sets makes everything more efficient. The fewer tools you need to manage, the easier it is to align DevOps and itil.

For example, Atlassian Jira can serve both development and operations teams allowing for better collaboration and visibility across the entire lifecycle. When you couple this with automated platforms like Ansible or chef, you can assure that your infrastructure changes are compliant with ITIL guidelines while still being fast and scalable. Yes.

The, the final challenge I want to highlight is the human factor. Making sure that everyone in the organization, from DevOps engineers to IT practitioners, is aligned on the goals of the transformation. This requires training, of course, clear communication and a strong focus on culture.

When people understand how DevOps and IT complement each other and how the tools can make the their jobs issue, issue resistance diminishes and adoption increases. Yeah, again, I fully agree with you. You know, culture is often the biggest hurdle, but it's also the most critical success factor.

When teams understand that DevOps and ITIL aren't at odds with each other, they can coexist and even enhance each other. Transformation becomes much smoother. My advice to organizations is to invest in cross training.

ITIL teams should learn the basics of DevOps practices like CICD and automation. While DevOps teams should familiarize themselves with ITIL s principles and practices, the shared understanding leads to better collaboration and more successful outcomes. I agree.

In summary, challenges are real, but, uh, with the right approach, starting small, selecting the right tools, simplifying processes, and focusing on value and culture, you can overcome these obstacles. The key is to leverage the strengths of both DevOps and IT to create a more agile and efficient organization. Yeah, I agree.

I mean, basically the convergence of DevOps and ITIL isn't just a possibility. It's already happening in many organizations. With the right tools and strategies in place, you can make the transformation both smooth and successful.

Absolutely. So here's a recap of a few takeaways from today's discussion. We've outlined, uh, some actionable frameworks and best practices for integrating DevOps into ITIL value streams emphasized how AI augmented tools can drive agility and continuous improvement across service management practices.

Uh, we also, through a real world case study, uh, showed firsthand the transformational impact on DevOps and itil together with tangible results like reduced incident result response times and faster change cycles, which are key benefits for any organization aiming to stay competitive in today's fast pace IT landscape. And finally, we discussed a range of tools and strategies including AI, augmented solutions and CICD pipelines that can streamline ITIL practices, particularly in areas like incident management and change control, enabling faster feedback loops and better overall performance. You know, we hope, uh, these insights that Victoria and I shared with you will help you on your journey, uh, to seamlessly integrate DevOps and itil.

And we look forward to hearing about your own transformation success stories in the future. Yeah, thank you. Uh, as we grab today's fireside chat on DevOps driven IT Transformation, we want to thank you for taking the time to listen to our fireside chat, in which we have explored how DevOps and it can work hand in hand to create faster, more reliable service delivery and improve operational efficiency.

Feel free to contact either of us. com. We hope that you enjoy the rest of this scale event.

Hey, thanks for wrapping up, Victoria. I would, uh, point out there were a couple of, uh, questions that, um, have come up over the, um, over these types of topics. I, I wonder what do you think about the first one?

Is there a book or document that explains how DevOps and ITIL integration can be accomplished? Yeah. Yes, of course.

Uh, your recent book that talks about continuous testing, quality, security and feedback, mark the title itself represents some of the reasoning of why IT and DevOps should work together. Uh, another interesting publications about ITIL and DevOps can be found in the people search portal, for example. There are a few articles which talks about these two great approaches, uh, and its integration.

Yeah, go ahead. Yeah, I guess, uh, you know, the ITIL documents themselves provide a lot, but you know, the combination of DevOps and ITIL is particularly interesting here. Uh, you know what, another question that comes up, maybe I can answer this one 'cause it, I've had to do some work on this myself recently.

What is the motivation for developers to learn itil? And, you know, I think we've covered that to some extent in the presentation, but the idea is, you know, ITIL provides a lot of insights and detailed guidance on things like change management and governance. Uh, you know, DevOps documentation for the most part is not all that prescriptive.

So, uh, it provides, you know, definite procedures, models, things that developers can learn to not only, you know, be compatible with ITIL l but also to benefit their own work as well. Absolutely. So that pretty much wraps up and, uh, again, appreciate everybody's attention.

Hope you have a great, uh, scale update for the rest of the day. Thank you very much. Thanks, Victoria.

See You there. Thank you, mark. Thanks everyone.

Bye. Byebye.