Skip to main content

Strategies for Managing IT Services

When I teach ITIL foundation classes and we start talking about aligning IT strategy with business strategy, I usually see some puzzled looks on the faces of my students.  So I thought I would give some basics on what we are trying to establish here.

The purpose of strategy management for IT services is to create a process for defining and maintaining an organization's perspective, position, plans and patterns related to its services and the management of those services.   The purpose of a service strategy is to communicate how a service provider will enable an organization to achieve the desired business outcomes and establish the criteria and mechanisms to decide which services will be delivered, to whom they will be delivered to and to establish the most effective and efficient way to manage these services.
The objectives of strategy management for IT services are:
  • Analyze the internal and external environments in which we (the service provider) exist and to identify any opportunities that we can exploit for the benefit of the organization.
  • Identify constraints that may impede our ability to exploit those opportunities and the delivery of services to create those business outcomes. Then define how we can remove or mitigate the effect of those constraints.
  • Agree on perspective and continually review to ensure relevance to current situation. This should result in a clear vision and mission statement for the service provider.
  • Establish the position of the service provider comparative to its customers and other service providers in the market space. This should define which services will be delivered and to whom they will be delivered to. This should also define how we will maintain a competitive advantage in the market space.
  • Produce and maintain planning documents and ensure all appropriate parties have current copies of this documentation. This should include the IT strategy, service management strategy and strategy plans for each service being delivered.
  • Ensure that each organizational unit has a tactical and operational interpretation of these strategic plans and understand what is required by each to deliver on this strategy.
  • Manage changes to the strategies making sure that they stay aligned to the internal and external environments. Certify that the related documentation includes these updates.


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…