assessed first by the Change Advisory Board (CAB). A Forward Schedule of Changes will The universe of Change is Reduces the likelihood of be published. All requested and understood; reduces the unintended consequences to any approved changes with their status chance that conflicting change or group of changes. will be listed. The Forward Schedule changes will introduce risk of Change will be reviewed at each of unintended CAB meeting. consequences into the Production Environment The definition of an Emergency Ensure that standardized Ensures prompt handling Change is: A Change that must be methods are used for of changes introduced as soon as possible such as process Emergency Allows for Assessment of those to resolve a Major Incident or changes in order to prevent risk, impact to (IT and the implement a Security patch. change-related incidents business) and resource requirements for Emergency Change requests Maintains effective communication with both IT staff and business users even during an Emergency. Emergency Changes require Ensure that as little risk as Ensures that the risk of business Emergency Change Advisory Board possible is introduced into service interruption during a (ECAB) approval. the production change is minimized environment during a change Access to alter the production Prevents people who are Ensures that appropriate environment is controlled, and access not authorized to make a checks and balances are rights are only given to those people Change from having access achieved. who are authorized to make changes. to the production Decreases the risk of environment. unauthorized Changes and potential disruption to the production environment All Changes require successful Ensures that any Changes Reduces the likelihood for failed completion of testing before being are tested to being Changes and the subsequent cost implemented into the production implemented into the to Customers for unplanned environment when there is a test production environment downtime. environment in place. At a minimum, and any Emergency Change validation in the production not tested prior to
assessed first by the Change Advisory Board (CAB). A Forward Schedule of Changes will be published. All requested and approved changes with their status will be listed. The Forward Schedule of Change will be reviewed at each CAB meeting. The universe of Change is understood; reduces the chance that conflicting changes will introduce risk of unintended consequences into the Production Environment Reduces the likelihood of unintended consequences to any change or group of changes. The definition of an Emergency Change is: A Change that must be introduced as soon as possible such as those to resolve a Major Incident or implement a Security patch. Ensure that standardized methods are used for process Emergency changes in order to prevent change-related incidents Ensures prompt handling of changes Allows for Assessment of risk, impact to (IT and the business) and resource requirements for Emergency Change requests Maintains effective communication with both IT staff and business users even during an Emergency. Emergency Changes require Emergency Change Advisory Board (ECAB) approval. Ensure that as little risk as possible is introduced into the production environment during a change Ensures that the risk of business service interruption during a change is minimized Access to alter the production environment is controlled, and access rights are only given to those people who are authorized to make changes. Prevents people who are not authorized to make a Change from having access to the production environment. Ensures that appropriate checks and balances are achieved. Decreases the risk of unauthorized Changes and potential disruption to the production environment All Changes require successful completion of testing before being implemented into the production environment when there is a test environment in place. At a minimum, validation in the production Ensures that any Changes are tested to being implemented into the production environment and any Emergency Change not tested prior to Reduces the likelihood for failed Changes and the subsequent cost to Customers for unplanned downtime.