Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 44 Next »

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

Target release

Document status

10% DRAFT

Document owner

Ian Tao (Unlicensed)

Designer

Asaad Mahmood

Tech lead

Jesse Hallam

Technical writers

N/A

QA

Prapti Shrestha (Deactivated)

User stories

Version

Monitor

Coordinate

Measure

v0.1.0

As 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

  • As the Incident plugin, a message is posted to the channel when the incident starts and ends so there is a timestamp record of who made the change.

v0.2.0

As 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 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.

  • 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.0

As a user, I can manage the commander and create a checklist template to improve future incident responses.

  • As a non-member of the incident channel, I’m prompted to contact the commander if I want to join.

  • 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.0

As 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.

  • As a user of a team, I can see a list of all past and current incidents within the team so 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 export channel transcript from the 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 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, start time, end time, duration, commander, number of people in the channel

v0.5.0

Address feedback so far

  • Give option for public vs private incident (and therefore channel)

  • Make it clear what is shown in RHS list

    • eg. Show All vs only Involved incidents?

  • Mentions (people, roles, channel, group) in checklist items

  • Incident duration in RHS

  • Start incident in an existing channel

  • Multiple people start incidents without realizing it’s for the same event

  • Organize checklist items into sections

    • Both during an incident and in backstage summary

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.0

Incident onboarding

  • As a person that’s just been added to an incident channel, I receive a templated ephemeral message so that I have the resources to help me start contributing.

  • As a user, I can configure the playbook to send a specific message whenever someone is added to the incident channel so that I can include instructions and links to resources.

  • As a user, I can review when each person was added to the incident channel so that I can understand the human resource that was invested.

v0.6.0

Metadata

v0.7.0

Aggregate reporting

v0.8.0

Dynamic slash command

  • (TBC) Interact with checklist via slash command

    • View checklist

    • Add/remove checklist item

    • Check/uncheck checklist item

User interaction and design

Key Learnings

  • Most customers do not expect nor even want automation to start, but rather prompts that gets their teams to consistently execute a procedure.

Open Questions

Question

Answer

Date Answered

Out of Scope

  • No labels