The Change Management process establishes an orderly and effective procedure for tracking the submission, coordination, review, evaluation, categorization, and approval for release of all changes to the project’s baselines.
A low risk (in this case, “low risk” is being used as a general term, as opposed to the formal definition calculated by the Risk Questionnaire you can download here), frequently occurring, routing change that has a pre-approved Standard Operating Procedure (SOP).
Non-Production — a change that is being performed against development, test or pre-production IT infrastructure. All non-production changes will go in as a Standard change.
A change that follows the normal process flow that may require approval by the Change Manager or the Change Advisory Board (CAB). Normal Changes are further categorized into high, medium or low risk.
A change that is submitted as a Normal Change but must be expedited with the following justification 1) for Financial or Legal reasons and 2) Organization’s Reputation or a Critical Vulnerability.
A change to resolve an outage or a pending outage, or to address a regulatory or security issue. Emergency changes must be approved by the Director verbally or by email or by text. The change is recorded after the Incident has been resolved.
A change that is driven by a vendor or third-party that is being recorded to aid with communication, e.g. Change Calendar, Informational Change
It is important to observe the minimum lead time for submitting the change and the approval process. The change should be submitted as soon as the business approves the change which typically should be well in advance of the minimum lead time.
Recent Blog Posts
GroupLink ITSM Change Management’s beta release is scheduled for Q3 of 2021. Fill out the form below and we’ll you know when it becomes available.