...
Open the Jira Change Management Queue at https://lehigh.atlassian.net/issues/?filter=10797&atlOrigin=eyJpIjoiYWQ3NWQ1NzM3YTdlNDdhY2FlOGI2NTQ5MmJjM2JjZTEiLCJwIjoiaiJ9 and select the change request.
Update and close out the change request.
Blameless Post Mortem Process
There may be times, even with successful changes, that you will need to call a blameless post mortem to review the changes with others so we can make improvements for the future. Follow the process below for a blameless post mortem..
...
Retrospective Process
As part of the process to close out an incident, a blameless retrospective must be conducted by the Incident Owner. The retrospective process must be followed in a way that no one is to be blamed for the incident itself and activities through completion. It must be in an open, honest, and learning environment so that we may capture findings, observations, and actions to continuously improve our services.
All LTS Retrospectives are stored in Google Shared Drive: https://drive.google.com/drive/folders/1cE9od_f0d9cqDqeEG9scYB_x6oIwcRIxx6oIwcRIxConnect your Google account
The Blameless Post Mortem Retrospective template is located at https://docs.google.com/document/d/1tRgl6V8nNqUtOIadrcGDqkXylmQnZ0GaR8X5_TpTFXk/editeditConnect your Google account
Key information captured includes:
...