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

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 the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: René. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…