Skip to main content

Visible Ops & Agile Service Management

Image
By
I highly recommend The Visible Ops Handbook by Gene Kim, Kevin Behr and George Spafford.

There are a lot of intersections between Visible Ops (VisOps) and being Agile.  In fact, following Visible Ops practices allows you to achieve an Agile perspective in a shorter time scale. 

There is an area in particular where I think alignment between VisOps and Agile is very strong. One of the four tenets of the Agile Manifesto is that we value “Responding to change”.  This is further underpinned by the principle “Welcome changing requirements, even late in development”.   Agile processes harness change for the customer’s competitive advantage.   This also ties us to the goal and objective of Agile Service Management in “Improving IT’s entire ability to meet customer requirements faster”.

Responding to change does not equate to bypassing process or controls.  Every business decision triggers an IT event.  Industry statistics tell us that 80% of outages are a direct results from poorly planned, unauthorized, undocumented or poorly executed changes that had limited risk assessment and no back out plans.  Consistent responsiveness requires processes that are designed to be agile and adaptive.

High performing IT organizations have incorporated elements from both this methodology and framework. As an example, Agile processes are designed with “just enough” structure and controls.  Visible Ops states CAB meetings should be restricted to evaluating and approving RFCs.  The goal is to keep change management meetings focused on management of change.  The CAB function is to identify which changes are risky, not come up with the solution for risk reduction. CAB meetings should be completed within 15 minutes.  Very Agile/Scrum like, no?

In high performing IT organizations, change management is not seen as burdensome, bureaucratic and a consumer of resources, time and money.  That’s because it is not.  It is well designed with “just enough” in place and ties success measures to business outcomes. Benefits such as increased availability, increased changed success rate, reduction of risk and reduction of MTTR comes often and early. This is due in part to creating a culture of change management through integrated processes, defined accountable and responsible roles and communication between all stakeholders.
Labels:

Comments

Post a Comment

Popular posts from this blog

Four Service Characteristics

By
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...
Post a Comment
Read more

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

By
This article was originally published in 2015. With the Introduction of ITIL 4, some of the concepts have changed in ways that are described below. ITIL 4 has also introduced new roles, as explained in our blog ITIL 4 and the Evolving Role of Roles . Before we dive into the difference between these roles, let’s first look at a key update in ITIL 4 – the shift from processes to practices. ITIL 4 has evolved to focus on holistic practices vs. isolated processes. By definition, a practice is a set of organizational resources designed for performing work or accomplishing an objective. For example, the purpose of the incident management practice is to minimize the negative impact of incidents by restoring normal service operation as quickly as possible. All organizations recognize the need to allocate resources to the management of incidents and mature their capabilities in that area. In ITIL 4, each practice includes resources based on the four ...
1 comment
Read more

What Is A Service Offering?

By
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.      ...
Post a Comment
Read more