Skip to main content

The Best of Service Strategy, Part 1

I've been hearing a lot lately about "going back to the basics" of ITIL and IT Service Management.  So for the first half of 2013, I'm going to package and republish the best of my blogs for each lifecycle stage.  As always, I welcome your comments and questions!   ~~ ITSM Professor

Utility and Warranty Equals Value
Originally published October, 2012

When a service provider is developing a service for a customer or group of customers the underlying goal is to ensure that the service has value for the customers by meeting a set of defined requirements.   The value is often defined by what the customer is willing to pay for this service rather than what it actually cost the service provider to produce the service or any other essential feature of the service itself.

Services themselves do not actually have intrinsic value.  That value is created by the outcome enabled by employing the service and therefore the value of the service is not determined by the provider of the service but by the customer who receives the service.  This is because they decide how to use it and the type of benefit they will achieve.   Services are only seen to contribute value to an organization if the value created is greater than the cost of procuring the service from the service provider.

From a customer’s perspective value is created by utilizing services to achieve business goals and objectives. This value is defined in terms of utility (fitness for purpose) and warranty (fitness for use).  Utility is the functionality that a service delivers to meet a specific need.  In other words this is what the service does to support desired outcomes.  The customers and the businesses perception of the service (value) is partially based on the ability of the service to consistently create these desired outcomes.

Warranty on the other hand refers to a services ability to be available when needed, provide the required capacity to meet the ever changing demand and insure that the service will be reliable in terms of continuity and security.  Warranty can be described as “how the service is delivered” (fitness for use).  Value gets created by combining these two elements of the value equation.  Customers can only benefit when both of these elements are present.

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…