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

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 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 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 than toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service

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

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th