Virima’s guide to incorporating agile framework with ITIL 4

Share on linkedin
Share on facebook
Share on twitter
incorporating-agile-framework-with-itil-4

ITIL4® embraces Agile more than any of the previous versions of ITIL, making it easier to implement and less of an organizational impact when implemented.

While ITIL4 still focuses on providing value to customers, the shift of focus from offering only service management practices to the customer and the value that programs bring to the customer makes it very different from prior iterations of the framework.

Agile is a software development methodology that focuses on making small, iterative changes quickly and with more focus on customer needs.

The seven guiding principles of ITIL 4

One of the ways ITIL 4 shifts its viewpoint from ITIL v.3, 2011 is with a focus on the seven guiding principles that were originally introduced in the Practitioner guidance, but which form the foundation of ITIL 4:

  1. Focus on Value
  2. Start Where You Are
  3. Progress Iteratively with Feedback
  4. Collaborate and Promote Visibility
  5. Think and Work Holistically
  6. Keep It Simple and Practical
  7. Optimize and Automate

The first principle, “focus on value,” sets the context for why an organization is adopting ITIL and what it is trying to accomplish.

The ITIL foundation guide adds some additional questions to consider when adopting the guiding principles. This helps IT when it engages with customers to determine the services they would consider valuable and which also helps frame the basis of why an organization is adopting ITIL 4 in the first place:

  • What? What is the current issue that must be solved?

  • Why? Why must this issue be solved?

  • How? How can the guiding principle(s) prevent mistakes during the process to the best solution?

The remaining principles are used to deliver on the promise of the framework, but several of these demonstrate why ITIL 4 and Agile work well together.

Start where you are

This principle works well in many organizations and reduces the impact of change often associated with adoption. In its purest sense, this is saying “don’t trash all of the good work you’ve done.”

The idea is to assess and align what works well in an organization and tweak it to be more effective. It also enables an organization to put any pain points to the three questions listed above and determine how to address them. This forms the basis for the work to be performed.

Agile: Progress iteratively with feedback

This is the Agile part of ITIL 4. It brings the concept of making many, small improvements to what’s working well and implementing new practices in small bites, making it far easier to adopt and adapt with ITIL 4.

By working on changes to existing practices in many small iterations, the team can gather feedback and determine if the process is moving in the right direction before implementing more change. This enables an organization to adjust before moving towards the next iterative change.

Optimize and automate

Once the organization has a base ITIL4-adoption program, the work continues, looking for ways to optimize iteratively and automate as many functions as possible.

The ITSM-ITOM connection

By the time an organization reaches the “optimize-and-automate” phase of any core practice, IT service management (ITSM) and IT operations management (ITOM) platforms become very important.

The configuration management database (CMDB) is a core component of every ITIL adoption program, because of the data it provides to the other processes, making it possible to diagnose issues and determine the risk of making a change, for example. The less obvious area is the use of automation to improve ITIL4 practices, such as problem management.

Most organizations still use problem management primarily to troubleshoot the root cause of major and repetitive incidents. With appropriate monitoring tools and a good CMDB, however, an organization is poised to become more proactive in its approach.

One of the keys to automating these areas is the use of predictive analytics and artificial intelligence capabilities that are now available in many service management platforms. Applying these capabilities to leverage the CMDB and historical data from event monitoring can help an organization identify problems earlier, prioritize them based on the services they support and then address them as needed.

All of this can be implemented iteratively, starting with an organization’s current state and working closer and closer to a more proactive service management style with every iteration.

Virima features can automatically discover and map your critical IT resources and the interconnections that link them to one another, your applications and services, and your users.

Virima is here to help. To get started, contact us today to schedule a demo and explore the possibilities!

ITIL® and ITIL4® are registered trademark of AXELOS Limited. Copyright © AXELOS Limited 2019. All rights reserved.

Share on linkedin
Share on facebook
Share on twitter

Subscribe to Our Newsletter

More to Explore

IT Operations Management (ITOM) refers to the administration of technology and application requirements within an IT organization. Under the ITIL framework, ITOM’s objective is to monitor, control, and execute the routine tasks necessary to support an organization’s IT infrastructure.(Also, see…

CMDB service maps are visual depictions of hierarchical relationships among business services (sometimes also major applications) and their supporting Configuration Items (CIs). Because service maps can provide an instant bird’s eye view of critical dependencies and relationships, their utility lies…

Understanding the Configuration Management Database (CMDB) and its core functions is a critical aspect of service management. The CMDB forms the hub of numerous service management practices and provides a means of correlation needed to deliver business services successfully.   The…

Introduction  IT asset management (ITAM) and inventory management are both useful practices that can benefit any organization using IT. Both of these practices are concerned with the management of IT assets but focus on different things. Inventory management can exist…

IT asset management (ITAM) and configuration management are both useful practices that can benefit any organization using IT. Both of these practices are concerned with the management of IT assets, but focus on different things.Configuration management can exist without IT…

Some people think that an IT service desk is the same thing as an IT help desk. It isn't, as I'm going to explain. Sure, there are some similarities, but there are also many differences. Let's start by exploring what…

To understand the business value of service mapping, it’s important to shift to a service delivery mindset, rather than thinking about delivering infrastructure, equipment, software, and applications. Defining services is relatively simple if thought of as the commoditization of what’s…

Business service mapping – the area of configuration management that perplexes so many IT professionals, yet that which provides the highest value in configuration management database (CMDB) projects. There are several major reasons IT gets stopped when it comes to…

The world of ITSM has changed as technology has shifted from providing tools for administrative support to being fully embedded in the delivery of the business’ core function.  There’s a world of difference between using an accounts payable system to…

The Configuration Management Database (CMDB) provides a single database that contains information about the enterprise’s assets, both logical and physical. In modern service management platforms, it provides core functionality that is referenced by all of the service management practices, including…