Skip to content

Incident Management UseCase Priority

John Jeremiah requested to merge jj-incident-mgt-usecase into master

Why is this change being made?

Based on our roadmap and direction for debugging and health and input from @kbychu we are on track to introduce a major improvement in "Incident Management" by the end of FY20 Q3.

  • incident management
    • Who? Incident Management for Devs
    • As an expansion of other capabilities
    • Ops Genie - 2nd most linked tool in Octa
    • Could be used to manage incidents for anything in IT...but will be awesome for GitLab projects.
    • Timeline (Looking at a fairly mature and useful state by end of next quarter (November)- Introducing a new object - Incident. (not just an issue)

This needs to be a use case that we start to build out so that we have messaging and content ready for a launch and potential campaigns at the end of the year.

Conceptually, this Use-case/Solution fills in the DevOps lifecycle addressing the management of applications in production.


journey
    title DevOps Lifecycle
    section Agile
      Manage: 5:
      Plan: 5:
    section VCC
      Create: 5:
    section DevSecOps
      Secure: 5:
      Defend: 5:
    section CI
      Verify: 5:
      Package: 5:
    section CD  
      Package: 3:
      Release: 3:
      Configure: 3: 
    section Incident Mgt
      Monitor: 0:

Why?

  1. There is a huge market for incident management solutions.
  2. Delivering this as part of Gitlab's offering will increase GitLab adoption and the value customers get from GitLab
  3. Incident Mgt will be ANOTHER differentiating capability and ANOTHER market where we will be competing. (We can launch the Solution/Use Case WITH the product.
  4. and... it will complete the DevOps lifecycle from a solution/usecase perspective.

Author Checklist

  • Correct MR template applied (e.g blog post)
  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.

For help with failing pipelines reach out in #mr-buddies in Slack

Edited by John Jeremiah

Merge request reports