Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties

Target release

Document status

Status
title1% Draft

Document owner

Ian Tao (Unlicensed)

Designer

Asaad Mahmood

Tech lead

Jesse Hallam

Technical writers

N/A

QA

Prapti Shrestha (Deactivated)

Objective

Deliver an Help Mattermost users monitor, coordinate, and measure their incident response solution that customers would use in production and Mattermost can start selling.

Success metrics

...

Goal

...

Metric

...

Customer uses our MVP in production

...

Number of customers

...

Made first made

Assumptions

process so that it can be more transparent, efficient, and impactful.

User stories (2020-03-20: This is out of date from Productboard migration, will be updated this weekend)

As

Access and manage the pluginMonitor

Coordinate incident response

Organize and review incidents

Customize incident playbooks

Streamline response process

Measure

v0.0.1

start/viewStart/end

  • As an admin, I can install the Incident plugin on my server so that all users can access it.

  • As an admin, I can disable the Incident plugin so that users can’t access it but its data isn’t deleted.

  • As a user, I can start an incident with a slash command so that response can start quickly.

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 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.As the Workflow plugin, incident start is available both as a trigger and action with channel name as a parameter so that it can be automated.

v0.0.2

stagesChecklist template

  • As a user, i I can change the stage of an incident within the RHS so that its current status is clear to everyone elsesee the checklist for each active incidents in the RHS it’s clear what’s been done and what needs to be done.

  • As a user, I can see the current stage of the active incidents in the RHS without opening it configure the incident playbook with a checklist so that I save a clicktime setting up each future incidents.

  • As a usermember of the incident channel, I can see how long it has been since the incident has started in RHS so I can put its urgency in context.As a user, I can configure the incident playbook with specific stages using code so that they can be set for future incidentscheck 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 the stage a checklist item has been changed checked/unchecked so that there is a timestamp record of who made the change.

  • As the Workflow plugin, incident stage change is available both as a trigger and action with stage name as a parameter so that it can be automated.

v0.0.3

Add/remove checklist items & change commander

  • As a user, I can check off items for an incident in the RHS so that it accurate represents the team’s progress.As a usermember 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 usermember 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 usermember of the incident channel, 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 user, I can configure the incident playbook with a checklist using code so that it created for future incidentschange the incident commander from the RHS so that it remains accurate.

  • As the Incident plugin, a message is posted to the incident channel when a checklist item has been added, removed, checked, or checked/unchecked so that there is a timestamp record of who made the change.

  • As the Workflow plugin, incident checklist item change is available both as a trigger and action with action and item description as parameters so that it can be automated.

v0.0.4

message forwardingv0.0.4

Basic reporting

  • As a user, I can see a list of all past and current incidents so that I have a complete record to refer to.

  • As a user, I can see the detail of any past incident so that I can use it for post-mortem.

  • As a user, I can see related messages from elsewhere automatically copied in the incident channel so that I have all the information that I need.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 messages

  • As a user, I can see the following actions ordered chronologically so that I can visualize the timeline of the incident:

    • Start incident, commander change, checklist item checked and unchecked, end incident

  • As a user, I can configure the incident playbook with conditions to copy messages elsewhere in MM so that context is centralized in one place.As the Incident plugin, messages that meet the condition in the playbook are automatically posted in the incident channel so that users save time from doing it manually.see the total number of incidents so that I can decide how much to invest in proactive prevention.

  • As a user, I can see the total duration of all incidents so that I can decide how much to invest in proactive prevention.

  • As a user, I can see in the range and medium duration for all incidents so that I can decide how much to invest in reactive response.

v0.0.5

Detailed playbooks

v0.0.6

Multiple playbooks

v0.0.7

Granular checklist

User interaction and design

...