[DevOps Adoption] Add Secure features to the DevOps Adoption table

Overview

GitLab now has a DevOps Adoption table that shows which GitLab features are being used across different groups in an organization. The MVC looks like this:

Screen_Shot_2021-02-16_at_2.56.02_PM

If a group used a feature in the last calendar month, the circle will be filled in.

Problem to solve

While this is a good MVC, users want a more detailed breakdown of which features have been adopted.

The JTBDs being addressed with the adoption table include:

  1. As a business leader, I need to demonstrate that GitLab is being adopted by teams so I can justify renewing our contract.
  2. As a business leader, I need to evaluate how mature our adoption of GitLab is so I can determine whether we are ready to upgrade to the next tier.
  3. As an engineering leader, I want to identify which teams have been most successful in their adoption of GitLab so we can learn from their successes.
  4. As an engineering leader, I want to experiment with new DevOps processes/tools in my workflows, so that I can improve productivity and the quality of applications being delivered to end users.

For an example of specific use cases from customers, see Problem to solve in the epic.

We would like to add a list of top priority features from each stage to highlight an organization's progress on their devops adoption journey. The table already includes Scanning, but that could be any type of scan. Customers have indicated that they want a breakdown that shows adoption of SAST, DAST, etc.

Screen_Shot_2021-03-09_at_3.09.40_PM

Proposal

Identify another 3-5 key features from the Secure stage that Engineering directors and above will be interested in to evaluate progress on their devops adoption journey and their ROI in GitLab.

Suggested features

  • SAST
  • DAST
  • Fuzz testing
  • Dependency scanning
  • Vulnerability management

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited by 🤖 GitLab Bot 🤖