Skip to main content

Creating and Supporting Services – Plan, Protect and Optimize!

Would you buy a product or service that did not include some type of warranty?  If the manufacturer or reseller does not explicitly set the expectations, then you will form them for yourself.  It is the same with the customers of your IT services.  Either IT clearly sets the expectations, or end-users will develop them on their own. Best practice tells us that during the negotiation and acceptance of Service Level Agreements, IT commits that services not only meet business and customer outcomes but also that they will meet requirements for availability, capacity, continuity and security. 

Ok… that is good.  Best practice tells us to include these so called “non-functional” requirements early in the lifecycle of a service.  In reality these warranty requirements are often considered somewhat in the Strategy/Design stage but more often than we would like to admit the majority of the work and effort for security and availability are performed reactively in the Service Operation lifecycle stage.

The lifecycle of a service consists of activities performed in Service Strategy, Service Design, Service Transition and Service Operation. In each of these lifecycle stages there are many processes and activities.  For example, Incident and Problem Management processes are primarily performed in the Service Operation lifecycle stage. Here is a simple test.   Ask your team or managers or IT practitioners this question:

In which of these lifecycle stages would you place the “Capacity Management” and “Availability Management” processes or activities? 

The answer that I get more frequently than not is that the majority of activity for Capacity, Availability, Continuity and Security are performed in “Service Operation”.  No…. we don’t want this.   These requirements and design activities should be early on in the Strategy/Design stage.  These requirements should be included along with the functional requirements and with the same amount of rigor and emphasis as the functional requirements for a service.  Warranty requires that we, as service providers, agree to specified levels of availability, capacity, IT service continuity, and Information Security.   If 80% or more of the activity for warranty is performed in Service Operation it is likely that the service provider is very reactive and not able to meet the needs of changing business demands in a timely or cost effective manner.  These organizations will sometimes break down from reactive mode to chaos where business value and customer confidence take a hit. 

Moving from common practice to best practice presents many challenges.  Best practice tells us that
care must be taken, however, not to set up standards or documentation requirements that create excessive bureaucracy without consistently returning better services to the business and/or customer. The goal should be to put just enough definition, measurement and control of design activities in place to successfully manage the work and improve results, but no more.

For more information, education or certification in these areas click here: “Plan, Protect and Optimize


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

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for th

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