Skip to main content

Changing ITSM Seasons


As we approach the fall and winter in the northern hemisphere, the change of seasons makes me think of the whole idea of renewal. This leads me to think about the place of renewal in ITSM—Continual Service Improvement. To make improvement work really well it must be a continuous activity. At a minimum, we should take some time to recognize that ITSM has seasons just like the physical world. Each year as we strive to deliver value to our customers, users and business partners we should think about those seasons. The seasons of the year offer up an opportunity to renew our efforts in ITSM and to bring new life out of the longer-term activities and efforts within our organizations. Just like the need to change a battery in a smoke detector once per year, the “battery” of your ITSM work might need replacement, recharging or renewal.
What does renewal of an ITSM implementation or effort look like? Here is a short list of the activities and steps you might take to help your own “renewal”:
  • Review your strategy: Is it still valid? Have conditions changed since you created the strategy? Are tactics and operations still in line with the original strategy? Will a change in strategy cause a change in tactics or operations?
  • Refresh your service catalog: Are there any services that need retirement? Is the information still valid? Does the information represent the current offerings? Does the catalog still “market” your services effectively?
  • Shuffle your CAB membership: Is it time to bring new “blood” or “fresh eyes” to the Change Advisory Board? Does the meeting format still suffice? Are there collaborative technologies now available that could help the CAB?
  • Refresh your incident and problem models: Are the current catalog of models or knowledge articles still up to date? Have technology updates made the models obsolete? Are there models still needed that have not been written?
  • Review your measurements and metrics: Are the metrics still bringing a fresh view of your strategic, tactical and operation world? Are the metrics “stale”? Has work fallen into a rut because of “stale” metrics?
These are just a short list of thought starter questions you should ask yourself as you change seasons or as you go into year’s end. Time your renewal with the change of the physical world as a reminder each year that as nature refreshes so should your organization!

Comments

Anonymous said…
Awesome reminder to review what you have, do you need it, is it effective, does it meet your company's goals? It also builds the foundation for improved IT Governance, Risk and Compliance.
Thanks,Professor Wise.

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…