...
Objective
Help organizations monitor, coordinate, and iterate measure their incident response process pipeline so that it can be more efficient transparent and effective. Focusing specifically on the following areas in order of priority:
...
| Monitor | Coordinate | Measure |
---|
v0.1.0 Start/view/end incidents | As a user, I can view a list of active incidents 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 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.0Checklist template | | As a user, I can configure the incident playbook with a checklist so that I save time setting up each future incidents. As a member of the incident channel, I can check off items for an incident in the RHS so that it accurate represents the team’s progress.
| |
---|
v0.3.0 Add/remove checklist items & change commander | 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.
| | |
---|
v0.4.0 Basic reportingLog and summary | As a user, I can see a list of all past and current incidents so that I have a complete record to refer toso that the information is not lost. As the incident plugin, the channel is automatically archived when the incident ends so that it reduces clutter.
| As a user, I can see export channel transcript from the detail of any past incident detail page so that it can be saved for record As the incident commander, I receive an incident summary and a link to more info after ending an incident so that I can use it know where to go for post-mortem.
| As a user, I can see a summary of the following on incident detail page so that I can get the gist at a glance: Channel name, start time, duration, last-known commander, total number of people in the channel, number of messagesbots in the channel
As a user, I can see the following actions ordered chronologically review when each checklist item was completed so that I can visualize the timeline of the incident: As a user, I can see the total number of incidents so that I can decide how much to invest in proactive preventionidentify the steps that are taking the most time.
|
---|
v0.5.0 Welcome message | | | |
---|
v0.56.0 Detailed playbooksMetadata | | | |
---|
v0.67.0 Multiple playbooksAggregate reporting | | | |
---|
v0.78.0 Granular checklistMultiple playbooks | | | |
---|
User interaction and design
...