Skip to main content

Problem, Incident and Change Management Integration

Problem Management seeks to minimize the adverse impact of incidents and problems on the business that are caused by underlying errors within the IT infrastructure and to proactively prevent the recurrence of incidents related to those errors.  In order to achieve this, Problem Management seeks to get to the root cause of incidents, document and communicate known errors and to initiate actions to improve or correct the situation”.  
Given that statement is directly from the ITIL Best Management Practices text, it’s a wonder more organizations don’t have well integrated Problem, Incident and Change processes in their organizations.

I never want to say that there is a single silver bullet solution for a given problem and I’m not suggesting that here.  However having a solid CMS (Configuration Management System) is a good step in the right direction.   Of course before we even think of tools we must have rules.  Thinking holistically we can create an integrated set of best practices across process boundaries. This will allow us to:
  • Optimize processes and ensure their use through standardized models that can effectively guide analyst through best practice for Incident, Problem and Change management.
  • Reduce resolution times by cutting across process boundaries, to ensure that the right information and knowledge is properly communicated and escalated to the correct stakeholders.

Problem Management ensures that all resolutions or workarounds that require a change to a configuration item are submitted through Change Management and implemented through a Request for Change. Change Management will monitor the progress of these changes and keep Problem Management informed. 

Problem Management can also play a significant role in the Change Advisory Board (CAB).  Working in conjunction with Incident management, Problem Management can also be involved in resolving incidents caused by failed changes. For some incidents, it will be applicable to involve Problem Management to investigate and resolve the underlying cause to prevent or reduce the impact of recurrence. Incident Management provides a point where these are reported. Problem Management, in return, can provide known errors for faster incident resolution through workarounds that can be used to restore service.

We can also use the Incident Management process as check on change.  Having the Service desk aware of the change schedule will allow it to be able to detect incidents caused by changes and create the appropriate relationships in the CMS. 



Comments

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group .   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service than toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service

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 th