The Agile Process Owner

Let’s face it, IT service management (ITSM) processes get a bad rap. Sometimes deservedly so. Bureaucratic and overly risk-adverse processes can be a real constraint in the IT value stream; particularly in organizations that are adopting agile, lean and DevOps practices. To keep pace, today’s IT organizations must be built on ITSM policies and processes that facilitate speed and change. So who ensures that ITSM processes are designed with ‘just enough’ control to meet an organization’s needs? Here’s where the role of Certified Agile Process Owner comes into play.

A Certified Agile Process Owner (CAPO)^SM adapts agile and Scrum values and practices to ITSM processes and process design and improvement activities. Much like a Scrum Product Owner, a Certified Agile Process Owner manages stakeholder requirements and strives to translate those requirements into process activities and features that deliver value.

What’s different is that CAPOs and Process Improvement Teams use Sprints to deliver those activities and features in usable increments, in much the same way that Product Owners and developers deliver software increments. A CAPO plays a critical role before, during and after Sprint events by:

Managing and prioritizing a Process Backlog
Capturing and mapping user stories
Facilitating backlog grooming activities
Collaborating with stakeholders, Process Improvement Team members and the Agile Service Manager
Deciding when and how process increments are released

Traditional process design and improvement projects are sometimes prolonged efforts with little opportunity for experimentation, learning, and stakeholder feedback. To more quickly deliver value, a CAPO learns to focus on critical process activities and to deploy those activities in small, frequent releases. Fast feedback and a focus on measuring outcomes that matter to the business enable continuous process improvement and processes that are fit for purpose.

While it’s often perceived that processes stand in the way of progress, the reality is that the highest performing organizations don’t get there without efficient and effective ITSM processes. Nor do these organizations become high-performing with overly-rigorous processes. They get there by having agile processes and by using agile methods and techniques to continuously improve those processes.

Realizing the value of a process is dependent on the steps taken to ensure the process is agile, sustainable and constantly evolving. Selecting Process Owners with the right level of authority, the right mindset and the right skillset is critical to ensuring the value is fully realized. A CAPO brings an agile mindset and the ability to adapt agile practices to process design and improvement activities.

What our alumni are saying about Certified Agile Process Owner (CAPO)^SM:

Excellent course. Our entire ITSM Center of Excellence needs this sort of class.

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

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

Search