Change Management Document - near term implementation plan

Describe the Issue Describe our Change Management procedure with an initial diagram and high level document

Additional Context This is an initial step focusing on the near-term and we will add iterations to this document with time.

Description: Change management is about the implementation of processes and procedures that help not only manage platform changes but also communicate these planned events, while ensuring that any modifications are well understood, tested, planned for and documented_

Change Management diagram - business requirements: Need to create a diagram documenting change management for the AWS landing zone. A change defines an event when the state of an existing service changes, either by introducing a new version of the existing service (i.e. upgrade), or a brand new service/feature (a new release) or decommissioning an existing service. The diagram should document the process the team follows if they need to make any change to the production environment for the Cloud landing zone.

Audience: The diagram is intended to be shared with our clients that using the AWS landing zone currently, who want to know how our team is managing changes in the landing zone production environment.

Process Scope: The change management flow in the diagram should reflect what improvements to the current change management process we can introduce "tomorrow" without developing any additional code (ie. near-term). The change management should only focus on the "landing zone"-level change, client application changes are out of scope.

Acceptance Criteria

[ ] Diagram of Change Management procedure
[ ] High level description (maximum 1 page)

bcgov / cloud-pathfinder

Change Management Document - near term implementation plan #2951