Skip to main content

Agile Service Management – Roles and Responsibilities

Agile Development is an umbrella term for several iterative and incremental development methodologies.  In order to achieve Agile Development, organizations will adopt frameworks and methodologies such as SCRUM and LEAN.

Being Agile and using SCRUM, LEAN and other methodologies in development is good!  What happens when development starts adopting this culture and becomes more agile and begins to move faster and leaner than ever before, only to come up against laborious and bureaucratic change management and Service Operation processes?  One example that I heard lately is that it is like pushing more and more paper into a printer and expecting it to print faster!   It doesn’t work!

The Agile Principles and the Agile Manifesto are applicable beyond software development. Therefore, service providers not only need Agile Development we also need to adopt Agile principles throughout the entire Design, Transition, and Operation lifecycles.  Agile Service Management (Agile SM) ensures that ITSM processes reflect Agile values and are designed with “just enough” control and structure to effectively and efficiently facilitate customer and business outcomes when and how they are needed.

There are several Roles identified in the SCRUM Framework for Agile Software Development and when adopting Agile Service Management for ITSM processes the roles are quite similar.

Agile Service Management Roles:

Agile Process Owner:
Instills Agile thinking into the process
Communicates the process’ vision and goals
Creates, maintains and prioritizes a Process Backlog
Ensures that Agile values are embedded into the process
Inspects the process’ progress after each Sprint
Audits and reviews the process
Prioritizes improvements in the CSI Register
Is accountable for overall process quality

Agile Process Team – A Cross‐functional Agile Process Team should include:
Process Owner
Process Manager(s)
Process Practitioners
Change Manager(s)
Tool Administrators
Technical Writers or Documenters
Customer and/or User Representative
Other Process Managers or skills as required

Agile Service Manager - Operational counterpart to Developments ScrumMaster
Manages the Agile and Scrum aspects of the ITSM program
Ensures Agile and Scrum principles are understood and applied to ITSM
Removes impediments whenever possible
Works closely with the Process Owner and Team to get the work done
Facilitates Scrum events as needed
Helps the Agile Process Team bridge relationship with Development Teams!

To learn more, or register for ITSM Academy's Certified Agile Service Manager (CASM) or Certified Agile Process Owner (CAPO) - Click Here

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