⚙️ WoE Action: Review Operation Engineering Slack Channels #5494
Description
User Need
As a COAT (parka, puffer, rain, duffel, trench, lab, fur etc etc)
I want to review the existing Operations Engineering Slack channels
so that we can remove anything that isn't COAT related
Value
Removing unused, or no longer helpful, legacy Operations Engineering channels will reduce noise and clutter in Slack and improve our working efficiency. Looking into the purpose of the existing Ops Eng channels will enable us to move useful stuff (e.g. alerts) to the relevant COAT channels, making information easier to find and allow us to better monitor existing services.
Functional Requirements (What):
- Review the purpose of existing Ops Eng channels and the services/information they provide
- Move pertinent services/information into new COAT channels
- Close down as many legacy channels as possible
Non-Functional Requirements (How):
- Review the legacy channels and their purpose as a team
- Create a plan for the decommission of old channels including the moving of services/information they provide
Acceptance Criteria:
- Legacy channels have been reviewed
- Services and information from existing channels have been moved to new COAT channels
- Any necessary coding changes/Slack changes etc have been made and tested
- Ensure any external users of the existing channels are aware of how to find the new home(s) of services/information they use
Assumptions (Optional):
- That we can, or indeed should, decommission legacy Ops Eng channels
Risks and Mitigation (Optional):
- As Slack history cannot be moved to new channels there is a risk of losing useful information
- There could be a risk of services no longer working as expected, or outages during transition