Skip to main content

Agile Service Manager

What is an Agile Service Manager? The following is a definition from the University of California Santa Cruz for an IT Service Manager. “The Service Manager has overall accountability for defining the service, ensuring services meet the business need and are delivered in accordance with agreed business requirements and managing the service lifecycle – often in conjunction with a Service Team. I also looked up some jobs offerings from around the globe that were described as Agile Service Management and took some pieces from them.  Here are a couple of examples:
  • Has responsibility for defining and creating the global service, developing the reliability and performance of the services in line with the business requirements, and managing the overall service lifecycle within an agile environment. This includes stability, performance, capability, risk acceptance and analysis of the services.
  • Developing a deep understanding of what is important to the service, you will be prioritizing and driving improvements, key business initiatives and resolution of service related issues through established strong relationships with your key stakeholders and all the technical teams.
You see the similarities? The differences?  Let’s start at the beginning and ask why all this talk about being Agile. In today’s IoT (Internet of Things) every business has become a technology business and every business decision triggers some type of IT event. Demand for innovation, reliability, automation and the capability to deliver these services and the underpinning technology quickly and on budget has become a critical success factor for all IT organizations today. 

Rapidly changing IT requirements require rapidly changing IT capabilities” (1)

Being Agile is not the incorporation of just one thing such as a framework like scrum into the way we manage the delivery of our services, but is the approach and perspective with which we can apply multiple frameworks, practices and principles always with the goal of increasing value to the business.  “Agile Service Management ensures that ITSM processes reflect Agile values and are designed with “just enough” control and structure in order to effectively and efficiently deliver services that facilitate customer outcomes when and how they are needed.” (2)
An Agile Service Manager must ensure that:
  • Agile values and principles are embedded into the entire ITIL lifecycle
  • We improve ITSM’s entire ability to meet customer requirements faster
  • We are being Lean; not overly complex, both effective and efficient
  • We ensure scalability.  Processes with “just enough” control and structure, ensuring the removal of constraints where capable and allowable.
  • We are communicative, always keeping an open eye and ear to the changing customer needs and requirements
How many of you already incorporate these items in what you do today? See, you're already on the journey to becoming Agile.   Good Luck!

For a list of certification courses: www.itsmacademy.com/agile
For related webinars http://www.itsmacademy.com/webinar-archives/

(1,2) The Agile Service Management Guide (Jayne Groll)

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…