In ITIL (Information Technology Infrastructure Library), "change" refers to the practice of managing changes to the IT infrastructure in a systematic and controlled way. ITIL Change Management aims to ensure that standardized methods and procedures are used for efficient and prompt handling of all changes to minimize the impact on IT services.
This involves assessing and authorizing changes, understanding the risks, communicating with relevant stakeholders, and implementing changes with proper documentation. The goal is to balance the need for change with the need to maintain the stability and reliability of IT services.
Types of changes
In ITIL Change Management, changes are categorized into different types based on their nature and impact. Common types include:
1. **Standard Changes:** Routine, low-risk changes that are pre-authorized and follow a documented procedure.
2. **Normal Changes:** Changes that go through the full process of assessment, authorization, and implementation.
3. **Emergency Changes:** Urgent changes required to resolve a critical issue or prevent a major incident. These changes are expedited but still follow a controlled process.
4. **Major Changes:** Significant alterations that may have a substantial impact on services, requiring careful planning, assessment, and communication.
5. **Minor Changes:** Low-impact changes that are typically handled with less formality than major changes.
These classifications help in tailoring the change management process to the specific needs and risks associated with each type of change.
Who can raise the change.
In the context of ITIL Change Management, change requests can be raised by various individuals or groups within an organization. Common entities authorized to raise change requests include:
1. **Users:** Individuals experiencing issues or having enhancement requests for IT services.
2. **Service Desk:** Frontline support staff who may identify the need for changes based on user feedback or incident patterns.
3. **IT Staff:** Technical teams or system administrators proposing changes for system improvements, updates, or maintenance.
4. **Business Units:** Departments or teams with specific requirements for changes to IT services in support of business goals.
5. **Change Advisory Board (CAB):** A group responsible for assessing and approving changes. CAB members may initiate changes or review proposals brought to their attention.
The specific process for raising change requests may vary between organizations, but it generally involves collaboration among stakeholders to ensure effective change management.
Approving Authorities of change.
In ITIL Change Management, the authority to approve changes is typically vested in a group known as the Change Advisory Board (CAB) or an authorized Change Manager. The CAB is a key component of the change management process and is responsible for assessing and approving changes based on their impact and risks.
The CAB may include representatives from various stakeholders, such as IT, business units, and other relevant parties. The Change Manager, on the other hand, is an individual who often leads the change management process and has the authority to approve certain types of changes.
The specific approval process can vary between organizations, and it's essential to define clear roles and responsibilities to ensure effective and controlled change management.