It’s Still All About “The Process”

Organizations adopting DevOps cultures and practices are able to deliver high-quality software faster. This means the business can deliver value to customers faster. You sometimes hear that DevOps and ITSM aren’t compatible. In a recent ITSM for DevOps workshop an attendee asked whether process is still relevant for digital transformation initiatives in today’s environment. The answer is emphatically Yes. Now more than ever before the attention to process is critical. Whether your company is striving to achieve traction for a cultural shift, for a digital transformation, to create a DevOps pipeline or any other improvement initiative, Process will always be a critical success factor. Remember we are talking about just enough process. We cannot have over engineered bureaucratic processes. For our purpose here, we will focus high level on some of the process design considerations and mistakes to avoid. To learn more about what is just enough and how to design or redesign your existing process there is a Certified Process Design Engineering class that goes into more depth and detail.

The true success to any improvement initiative will most likely fall back to your process. Remember that a process is a predefined set of activities. Some believe that process does not matter if your focus is on automation. That is not true. The Process is what you are attempting to automate. It also does not matter whether you focus on LEAN, ITSM, DevOps or another best practice/standard. The process maturity lifecycle reflected in various frameworks and standards is essentially the same.

The Process must be:

Defined
Documented (just enough)
Managed (via performance metrics)
Continually Improved

Failing to recognize the effort required to complete these seemingly simple steps is a common mistake that organizations make. Failing to establish clear and measurable improvement targets is another common mistake. Failing is simply a road to overall failure. Setting improvement targets and selecting a process design approach begins with understanding the factors triggering a process design or improvement initiative. Understand why a process design initiative is needed. This will help you focus and to prioritize efforts and processes that lead to success!

Comments

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...

Search