Incident Management Plan for CMS Teams

[EWashb]

Background

To ensure proper communication with stakeholders, editors, and internal teams of the Sitewide Crew during a variety of incidents that may cause issues with the CMS, it is necessary that we create an incident management plan that is not dependent on one method of communication.

User Story or Problem Statement

How might we create an incident management plan that accounts for various scenarios and provides a path of communication not reliant on one person in the ecosystem.

Affected users and stakeholders

• CMS editors
• All sitewide crew members
• PO

Hypothesis

We believe that a documented incident management plan will achieve seamless communication in the event of an emergency.

Acceptance Criteria

• [ ] incident management plan with various scenarios is documented and approved by PO
• [ ] Runbook(s) created

Labels

(You can delete this section once it's complete)

• [x] Issue type (red) (defaults to "Epic")
• [ ] CMS subsystem (green)
• [ ] CMS practice area (blue)
• [x] CMS workstream (orange)
• [ ] CMS-supported product (black)

CMS Team

Please check the team(s) that will do this work.

• [ ] Program
• [ ] Platform CMS Team
• [ ] Sitewide Crew
• [x] ⭐️ Sitewide CMS
• [ ] ⭐️ Public Websites
• [ ] ⭐️ Facilities
• [x] ⭐️ User support

[stefaniefgray]

Assigned to @TroyA6 and moving to In Progress since he's been working on this and can tie the associated tickets together and link related documentation