Skip to main content

Integrating ITSM and DevOps

As the pace of technological innovation increases and digital disruption becomes the norm, the need to adapt and accelerate IT service management (ITSM) processes is more critical than ever. It’s no longer a debate about whether ITSM and DevOps should interface; ITSM professionals must now understand how the practices they use to co-create value can either support or undermine the flow of work and pervasive automation in a DevOps environment.

It’s easy to understand why ITSM professionals are skeptical about DevOps. ITSM performance metrics and service level agreements (SLAs) often revolve around the IT organization’s ability to mitigate risks, minimize impact, and “guarantee” availability. While these measures have value, sacrificing speed, agility, and innovation can negatively impact the business.

ITSM Image Even with the evolution to ITIL 4, the what and why of ITSM haven’t changed. A customer-focused culture in which everyone understands how they contribute to the co-creation of value will always serve an organization well. It’s the how that must adapt in support of DevOps. ITSM professionals need a breadth of knowledge about DevOps practices like The Three Ways, Continuous Integration and Delivery, and DevSecOps. Understanding these DevOps concepts will help ITSM professionals see that many controls historically addressed manually can now be achieved more effectively through automation.

ITSM Image What about the “No tools before the rules” mantra? That hasn’t changed either. What has changed is the acceptance of Agile and Lean values within IT. DevOps builds on Agile and Lean principles, taking an iterative, incremental approach with minimal waste. By streamlining processes and embracing concepts like “policy as code” and process automation, ITSM professionals can align with DevOps, achieving greater control through automation rather than manual processes.

The adoption of DevOps practices, especially in an enterprise setting, doesn’t eliminate the need for ITSM. ITSM provides a common language and proven practices that help ensure IT services:

  • Support business strategies
  • Result in a positive customer experience
  • Deliver value
  • Ensure quality, stability, and reliability

Applying Agile, Lean, and DevOps principles to ITSM modernizes the approach and improves the ability of both ITSM and DevOps to deliver business benefits.

To learn more about adapting ITSM practices to support DevOps, consider the following ITSM Academy certification courses and workshops:

ITIL® is a registered trademark of the PeopleCert group.

Join Newsletter

Comments

Popular posts from this blog

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.”  Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...

What is the difference between Process Owner, Process Manager and Process Practitioner?

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See  ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...