Skip to main content

The Best of CSI, Part 1

 
We conclude our "Best of" blog series with Continual Service Improvement.
 
CSI and the 7 Step Improvement Process
Originally Published on January 24, 2012


I would like to revisit the 7 step improvement process from the perspective of CSI, since there has been a slight (logical) modification to it.  The concept of measurement, what we measure, gathering the data , processing it into understandable formats and then being able to analyze it, is fundamental in our ability to perform (CSI)  Continual Service  Improvement as an overall vision and in support of the business need and the underpinning of tactical and operational goals.

1. Identify the strategy for improvement: (Plan) Talk to the business, to your customers and to IT management.  Utilize your service catalog and the associated service level requirements to define a starting point.  The question “What is important to the business?” must be answered.  Look to the corporate vision, mission, goals and objectives.  Identify the IT vision, mission, goals and objectives.  Are these properly aligned? Tie in the Critical Success Factors.  Are these being met?  Is value creation happening? (Wisdom)
2. Define what you will measure: (Plan) This directly relates to the organizations strategic, tactical and operational goals.  It is in this step where we actually define what can be measured.  If a gap exists between what can be measured and what we need to measure, then a gap analysis must be completed and then finalize an actual measurement plan.  CSI can identify opportunities for improvement. (Data)
3. Gather the data: (Do) Data can be gathered from multiple sources.   Quality is the key objective of gathering the data for CSI.   The emphasis is not on assuring real time performance (that is an operational perspective) but on identifying where improvements can be made to existing levels of service, or IT performance. (Data)
4. Process the data: (Act) Data is processed in alignment with Critical Success Factors (CSF) and Key Performance Indicators (KPI).  If necessary we can align this data all the way up to the vision.  The goal here is to process the raw data into an understandable format that can be rationalized and made consistent.  We begin to create information.  After this we can begin to analyze the information and begin to make the essential comparisons. (Information)
5. Analyze the data: (Check) In this step the information begins to be transformed into meaningful knowledge of the events that are impacting the organization.  We can begin to define any trends that may be happening within our environment.  We can also determine if these trends are positive or negative.  It is important that we ensure that proper analysis takes place, to support our future recommendations before we present this data to the business. (Knowledge)
6. Present and use the information: (Check) At this point we present and use the information in whatever way is necessary for the target audience.  It is imperative that you understand your audience and the purpose for which the report is being given.  The purpose and the value being created must be properly articulated.  This will prevent the gap that often happens between what IT reports and what is of interest to the business.  This will underpin our recommendations and assist the business in defining the next steps. (Knowledge)
7. Implement improvements: (Act) Here the knowledge gained is used.  We can optimize, improve and corrects services and processes.  The issues have been identified and solutions can now be applied.  Since each stage of the lifecycle has limited resources it is also here where we prioritize which improvements can actually be implemented.  Once done, new baselines can be established and the process can begin again.

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…