Describe the Issue
Creation of current Change Management process snapshot on how these are handled by the Ops team
Additional Context
As part of the Enterprise-Ready journey we've been asked for a snapshot of these two Ops processes now as they are, to compare to what we we'd likely be moving to in the future, which will be modeled and implemented into a full service management posture as iterative improvements, including software
Change Management diagram - business requirements
We 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 following if they need to make any change to the production environment for the AWS landing zone.
Audience: The diagram is intended to be shared with our clients that using the AWS landing zone 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. The change management should only focus on the "landing zone"-level change, client application changes are out of scope.
Acceptance Criteria
Discussion on general Incident/Change management and macro level aspects
Breakdown of processes through process interviews
Process flow mapping of current processes
Creation of the current Incident/Change process snapshot diagram
Discuss with Thibault for creation of final draft as part of additional tickets
Describe the Issue Creation of current Change Management process snapshot on how these are handled by the Ops team
Additional Context As part of the Enterprise-Ready journey we've been asked for a snapshot of these two Ops processes now as they are, to compare to what we we'd likely be moving to in the future, which will be modeled and implemented into a full service management posture as iterative improvements, including software
Change Management diagram - business requirements We 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 following if they need to make any change to the production environment for the AWS landing zone. Audience: The diagram is intended to be shared with our clients that using the AWS landing zone 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. The change management should only focus on the "landing zone"-level change, client application changes are out of scope.
Acceptance Criteria