Skip to main content

What are IT Services So Hard to Define? (Part 2)

In my last blog, I provided some suggestions for overcoming challenges in obtaining agreement on the scope and definition of IT Services.  As I mentioned, the Service Catalog is one of the first and most important assets in any service management program.


Today we are going to take a high level look at mapping IT Services to business processes.   The first step is to understand what your business or customer does and how it does it.


In truth, every business only has five primary focus areas - regardless of whether it is public, private, governmental, non-profit, small or large.  Consider this:
  1. Every business designs, develops or acquires products and/or services
  2. Every business communicates, markets and sells those products or services
  3. Every business delivers those products or services
  4. Every business supports its products or services
  5. Every business has to have a corporate infrastructure (HR, IT, Finance, etc.)
Can you identify where these activities are performed within your organization?


Starting at the highest level of your enterprise, create a running list of possible outcomes that are needed to fulfill each of these critical focus areas.  For each outcome, identify the associated end-to-end IT service or services.  For organizations with multiple lines of business, you may want to repeat this exercise until you reach an acceptable, agreeable and manageable level of service definition.


The key to this exercise is to not perform it in isolation.  Try to take a 360 degree view of services and outcomes. Engage stakeholders at all levels from IT and the business.  An interesting by-product will be an improved dialogue between IT and its customers and users. 


My final piece of advice is to start simple and stay simple.  A service catalog does not need to be very complex; it needs to be very clear.  

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…