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:
For related webinars

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


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 th

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

The ITIL Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi