Update BT Change Management with Post-Implementation Review + Minor Change

Why is this change being made?

This change is being made to enhance the Business Technology Change Management process to align with the new approved process here. In order to remain SOX compliant, we have been tasked with adding a post-implementation review to the Change Management process. Because this is a requirement, we have modified the approval matrix to add this step, as well as identify a new change type: CMTMinor Change. This new change type allows for business continuity during blocked periods and increases efficiency for small system changes.

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---