Skip to end of metadata
Go to start of metadata
Objective
Help organizations monitor, coordinate, and measure their incident response process so that it can be more transparent and effective. Focusing specifically on the following areas in order of priority:
Information security
Site reliability
Build pipeline
Urgent support
User stories
Version | Monitor | Coordinate | Measure |
---|
v0.1.0As a user, I can start/end incidents within Mattermost so that there is a dedicated channel for discussion. | As a user, I can view a list of active incidents within my team in the RHS so that I get an overview of what’s currently happening. As a user, I can select an active incident in the RHS to view its detail so that it’s accessible from anywhere. As a user, I can see and click on the channel associated to an incident in the RHS so that I can quickly navigate to it. As a user, I can view the commander of all incidents in the RHS without opening it so that I know who’s the point person.
| As a user, I can start an incident within my team with a slash command, RHS, or post action so that response can start quickly. As the user that starts an incident, I default as the commander so that ownership is clear. As the Incident plugin, a new channel is automatically created when an incident starts so that there is a place to log activities. As a user, I can choose the name of the new channel so that it’s easily recognized
| |
---|
v0.2.0As a user, I can share a checklist with my team during an incident so that it’s clear what to do. | As a user, I can see the checklist for each active incidents in the RHS it’s clear what’s been done and what needs to be done. As a member of the incident channel, I can add items to the end of the incident checklist in the RHS so that the team can adapt to the situation. As a member of the incident channel, I can remove items from the incident checklist in the RHS so that the team can adapt to the situation.
| | As the Incident plugin, a message is posted to the incident channel when a checklist item has been added/removed so that there is a timestamp record of who made the change. As the Incident plugin, a message is posted to the incident channel when a checklist item has been checked/unchecked so that there is a timestamp record of who made the change.
|
---|
v0.3.0As a user, I can manage the commander and create a checklist template to improve future incident responses. | | As a user, I can configure incident playbooks with a checklist to optionally save time setting up future incidents. As a member of the incident channel, I can change the incident commander from the RHS so that it remains accurate.
| As the incident plugin, a message is posted to the incident channel when the commander is changed. As a user, I can review when each checklist item was (last) completed so that I can identify the steps that are taking the most time.
|
---|
v0.4.0As a user, I can refer to any past incident by reviewing them in a central place so that my team can use that information to make postmortem easier. | | | |
---|
v0.5.0 Polish | | | |
---|
v0.6.0 Checklist item assignment | | | |
---|
v0.7.0 Checklist sections | | | |
---|
v0.6.0 As a user, I can post an incident status update so that it can be broadcasted and be referenced as a checkpoint by others. | | | |
---|
v0.5.0Incident onboarding | | | |
---|
v0.6.0Metadata | | | |
---|
v0.7.0Aggregate reporting | | | |
---|
v0.8.0 Dynamic slash command | | | |
---|
User interaction and design
Key Learnings
Open Questions
Question | Answer | Date Answered |
---|
| | |
Out of Scope