Change Management - Process Guide (ITSM, ISO 20000) – Word DOCX

The Change Management Process Guide (ChM) provides a comprehensive framework for managing changes within IT services, ensuring that beneficial changes are implemented with minimal disruption. This guide outlines the lifecycle of changes, detailing workflows, roles, and policies necessary for effective change management. By adopting this process, organizations can enhance service delivery, reduce risks associated with changes, and align IT services with business needs. The document serves as a living resource, requiring regular review and updates to maintain its relevance and effectiveness.

•  IT Service Managers overseeing change initiatives
•  Change Management Process Owners responsible for governance
•  Change Advisory Board (CAB) members involved in decision-making
•  IT teams implementing changes across various environments
•  Business stakeholders requiring alignment with IT services

Best-fit moments to use this deck:
•  During the planning phase of IT service changes
•  When assessing the impact of proposed changes on business processes
•  In preparation for critical business periods requiring change freezes
•  For training sessions on change management best practices

•  Define the Change Management process and its significance in IT service delivery
•  Establish a clear workflow for submitting and processing Requests for Change (RFCs)
•  Identify roles and responsibilities within the Change Management framework
•  Categorize changes based on urgency, risk, and impact
•  Implement standardized procedures for emergency and major changes
•  Evaluate the effectiveness of changes through post-implementation reviews

•  Introduction (page 6)
•  Key Definitions & Abbreviations (page 7)
•  Purpose and Objectives (page 11)
•  Scope (page 12)
•  Change Freeze (page 14)
•  Benefits (page 15)
•  Process Requirements (page 16)
•  Policies (page 22)
•  Triggers, Inputs, Outputs (page 25)
•  Categories of Change (page 26)
•  Process Flow (page 28)
•  Process Activities (page 29)
•  Roles and Responsibilities (page 40)
•  RACI Matrix (page 46)
•  CSF and KPI (page 48)
•  Process Reviews and Audits (page 50)
•  Process Reporting (page 51)
•  Role Assignment (page 54)

•  Change Management Process - This process ensures that all changes are managed effectively, minimizing disruptions and aligning IT services with business needs.
•  Request for Change (RFC) - A formal proposal for a change that must be submitted and assessed before implementation.
•  Change Advisory Board (CAB) - A group that advises on the assessment, prioritization, and scheduling of changes.
•  Emergency Change Procedures - Specific guidelines for handling urgent changes that must be implemented immediately.
•  Post-Implementation Review (PIR) - A review conducted after a change to assess its success and identify lessons learned.
•  Roles and Responsibilities - Defined roles within the Change Management process, including the Change Manager and Change Authority.

•  Change Request Form template for submitting RFCs
•  Change Record template for documenting changes
•  Standard Change Model for repeatable, low-risk changes
•  Emergency Change Procedure documentation
•  Post-Implementation Review report template
•  RACI Matrix for clarifying roles and responsibilities

•  Overview of the Change Management Process Flow
•  Key Definitions and Abbreviations for clarity
•  Categories of Change with detailed descriptions
•  RACI Matrix illustrating roles in the process
•  Benefits of implementing a structured Change Management process

Change Management Overview Session (60 minutes)
•  Introduce the Change Management framework and its importance
•  Discuss roles and responsibilities within the process
•  Review key definitions and terminology

RFC Submission and Assessment Workshop (90 minutes)
•  Walk through the RFC submission process and requirements
•  Practice categorizing changes based on urgency and impact
•  Review case studies of successful and unsuccessful changes

Post-Implementation Review Session (60 minutes)
•  Discuss the importance of PIRs in continuous improvement
•  Analyze examples of PIR reports and lessons learned
•  Develop action plans for future changes based on review outcomes

•  Adjust the Change Management process to fit specific organizational needs and structures
•  Tailor the RFC submission form to include relevant fields for your environment
•  Define specific criteria for categorizing changes based on your business context
•  Update the RACI Matrix to reflect actual roles within your organization

•  Change Freeze periods and their implications
•  Risk assessment methodologies for changes
•  Communication strategies for stakeholders during change processes
•  Continuous Service Improvement initiatives related to change management
•  Integration of Change Management with other IT service management processes

What are the main stages of an IT change management process?

Typical stages include submitting a Request for Change (RFC), assessing and prioritizing the RFC (often with Change Advisory Board input), scheduling and approving the change, implementing the change in the live environment, and conducting a Post-Implementation Review (PIR) to evaluate outcomes and lessons learned, culminating in documented change records and PIRs.

How should organizations categorize changes for handling and approval?

Organizations classify changes by risk, impact, and urgency into categories such as Standard (pre-authorized, low risk), Normal (full assessment and approval), Emergency (immediate action), and Major (project-managed with significant implications), with criteria defined in policies and the change categorization guidance.

What is a Request for Change (RFC) and what information does it require?

An RFC is a formal proposal describing a proposed change, its benefits, risks, impacted services, and implementation plan. It should provide sufficient detail for assessment, scheduling, and approval and map to the organization’s RFC submission requirements and the Change Request Form template.

When should emergency change procedures be used and what follows implementation?

Emergency change procedures apply when a critical issue requires immediate implementation to restore or protect services; such changes follow a documented emergency workflow, are recorded in change records, and are subject to a Post-Implementation Review to assess effectiveness and lessons learned as per the Emergency Change Procedure documentation.

What should I look for when selecting an IT change management template or process guide?

Choose a template that includes clear process flows, roles and responsibilities, a RACI matrix, CSFs and KPIs, RFC and Change Record templates, emergency change procedures, and guidance on reviews and audits. Alignment with ITIL and ISO 20000 and inclusion of tools like a RACI Matrix and RFC template are key attributes.

How much customization is typically required to adopt a standard change management process?

Expect to adapt the RFC submission fields, categories and criteria for change classification, the RACI Matrix to reflect actual roles, and any communication or freeze policies to your organizational context. The guide’s Customization Guidance recommends tailoring the Change Request Form and RACI Matrix to local structures.

I must plan a release during an upcoming change freeze; what should I consider?

Review the organization’s Change Freeze policies to determine allowed windows and exemptions, assess whether the release qualifies as an emergency change, secure required CAB approvals or documented authorizations, update relevant Change Records, and communicate stakeholder impacts according to the Change Freeze guidance.

How often should the change management process be reviewed and audited?

The process should undergo regular reviews to remain effective and aligned with goals; the guide recommends formal process reviews and audits at least quarterly, supported by monitoring CSFs and KPIs and documented process review outcomes during audits.

These are questions addressed within this presentation.

What is the purpose of the Change Management process?
The Change Management process aims to control the lifecycle of all changes, enabling beneficial changes to be made with minimal disruption to IT services.

What types of changes are covered under this process?
The process covers Standard, Normal, Emergency, and Major changes, each with specific procedures and requirements.

How are changes prioritized?
Changes are prioritized based on their impact to the business and the urgency for implementation, ensuring that critical changes are addressed promptly.

What is a Request for Change (RFC)?
An RFC is a formal proposal for requesting a change, detailing the proposed change, its benefits, and any associated risks.

What happens during a Post-Implementation Review (PIR)?
A PIR assesses the success of a change, evaluates whether it met its objectives, and identifies any lessons learned for future changes.

How often should the Change Management process be reviewed?
The process should be reviewed at least quarterly to ensure it remains effective and aligned with organizational goals.

What is the role of the Change Advisory Board (CAB)?
The CAB advises on the assessment, prioritization, and scheduling of changes, ensuring that all changes are evaluated appropriately.

What are the benefits of implementing Change Management?
Benefits include improved service delivery, reduced risks associated with changes, better alignment of IT services with business needs, and enhanced communication among stakeholders.

•  Change Management - The process responsible for controlling the lifecycle of all changes.
•  Request for Change (RFC) - A formal proposal for requesting a change.
•  Change Advisory Board (CAB) - A group that advises on change assessment and prioritization.
•  Emergency Change - A change that must be implemented immediately to resolve a critical issue.
•  Post-Implementation Review (PIR) - A review conducted after a change to assess its effectiveness.
•  Configuration Item (CI) - Any component that needs to be managed to deliver an IT service.
•  Service Level Agreement (SLA) - An agreement between an IT service provider and a customer.
•  Key Performance Indicator (KPI) - A metric used to evaluate the success of a process.
•  Critical Success Factor (CSF) - A key area that must be managed effectively to achieve success.
•  Standard Change - A low-risk change that follows a pre-defined workflow.
•  Normal Change - A change that follows the complete change management process.
•  Major Change - A change that has significant implications and is managed as a project.
•  Change Freeze - A period during which changes are not allowed to minimize risk.
•  Impact - The effect of a change on business processes.
•  Risk - The potential for loss or disruption resulting from a change.
•  User - A person who uses the IT service on a day-to-day basis.
•  Incident - An unplanned interruption to an IT service.
•  Problem - The cause of one or more incidents.
•  Deployment - The process of moving new or changed IT services into the live environment.