Overview
We are currently in closed beta and here is our target process for release planning:
PM researches and creates feature ideas in Productboard
PM consults UX and Dev collaborate to group features into upcoming releases
PM + UX + Dev lead collaborate to draft specs and designs
Whole team collaborates to build, test, and document the release
Dev lead cuts the release
PM announces to beta customers
Planned Releases
...
Objective
...
Scope/Spec
...
UX design
...
Technical design
...
Development
...
QA
...
Documentation
...
...
Enable users to start and end incidents without leaving Mattermost so that the conversation can be centralized.
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
...
Enable user to share a checklist during an incident so that it’s clear what to do.
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
...
Enable users create checklist templates ahead of time so that it saves time when starting an incident.
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
...
Enable users to access past incidents in a central place so that postmortem is easier.
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
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
Polish
...
1: Give option for public vs private incident (and therefore channel)
2: Make it clear what is shown in RHS list
eg. Show All vs only Involved incidents?
4: Incident duration in RHS
...
3: Start incident in an existing channel
To be prioritized:
...
Checklist item assignment
...
Mentions (people, roles, channel, group) in checklist items
...
Checklist sections
...
Organize checklist items into sections
Both during an incident and in backstage summary
...
Save incident as playbook
...
Save checklist from an incident as a playbook
...
Status update
...
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.
...
Metadata
...
Aggregate reporting
...
Dynamic slash command
...
(TBC) Interact with checklist via slash command
View checklist
Add/remove checklist item
Check/uncheck checklist item
Past Releases
v0.3.1
Feature: As a user, I can create playbooks ahead of time so that incidents can start with a checklist template.
Demo: Click here to see demo in user guide.
v0.2.3
Feature: As a user, I can share a checklist with my team during an incident so that it’s clear what to do.
Improvements:
Automatically navigate to the channel after starting an incident
Added telemetry
Fix issues for HA environments with configured read replicas. (v0.2.3)
Demo:
...
v0.1.0
Feature: As a user, I can start/end incidents within Mattermost so that there is a dedicated channel for discussion.
Download: v0.1.0
Demo:
...