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 fill in the release page with 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. | COMPLETE | COMPLETE | COMPLETE | COMPLETE | COMPLETE | COMPLETE | |
Enable user to share a checklist during an incident so that it’s clear what to do. | COMPLETE | COMPLETE | COMPLETE | COMPLETE | COMPLETE | COMPLETE | |
Enable users create checklist templates ahead of time so that it saves time when starting an incident. | COMPLETE | COMPLETE | COMPLETE | COMPLETE | COMPLETE | COMPLETE | |
Enable users to access past incidents in a central place so that postmortem is easier. | COMPLETE | COMPLETE | COMPLETE | IN PROGRESS | IN PROGRESS | PLANNED | |
IN PROGRESS | PLANNED | IN PROGRESS | BLOCKED | BLOCKED | BLOCKED |
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: