Commit a4337cb2 authored by David DeSanto's avatar David DeSanto
Browse files

Finalize Sec update and first half of Dev update, also fix typo on Dev section PI metrics

parent 3093d58e
......@@ -20,7 +20,7 @@
- Dev Section Jan 2021 Self-Managed TMAU continues to grow MoM
- Plan Stage Jan 2021 TMAU increased and exceeded its previous highest TMAU value
- Create Stage Jan 2021 TMAU increased and is trending upwards
- Manage Stage Jan 2021 TMAU decreaded MoM
- Manage Stage Jan 2021 TMAU decreased MoM
implementation:
status: Complete
reasons:
......
......@@ -12,16 +12,27 @@ Last Reviewed: 2021-01-12
 
<%= devops_diagram(["Manage","Plan","Create"]) %>
 
## Dev Section Accomplishment, News, and Updates
## Dev Section Overview
The Dev Section is made up of the [Manage](/handbook/product/categories/#manage-stage), [Plan](/handbook/product/categories/#plan-stage), and [Create](/handbook/product/categories/#create-stage) stages of the DevOps lifecycle. The scope for the Dev section is wide and encompasses a number of analyst categories including Value Stream Management, Project Portfolio Management, Enterprise Agile Planning Tools, Source Code Management, IDEs, Design Management, and even ITSM. It is difficult to truly estimate TAM for the Dev Section, as our scope includes so many components from various industries, but research from IDC indicates the estimated [TAM](https://docs.google.com/spreadsheets/d/1LO57cmXHDjE4QRf6NscRilpYA1mlXHeLFwM_tWlzcwI/edit?ts=5ddb7489#gid=1474156035 in 2020 is roughly ~$2B, growing to ~$4.3B in 2024 (18.31% CAGR). Analysis: [Manage](https://docs.google.com/spreadsheets/d/1357Zwbf0yTjcFBuCdX2HnNLBaF9uWnW7Auv4F94aoSo/edit#gid=0) [Plan](https://docs.google.com/spreadsheets/d/1dDNSR_mE4peeOc_3Xhqm_VLoTyk4gSbcbiGfuMrOg6g/edit#gid=0) [Create](https://docs.google.com/spreadsheets/d/1KSwTVPIvMO8IXkMqA40Ms1rL-glmo-w7MjZvUrjMFGA/edit#gid=0). NOTE: The large disparity in the TAM/SAM approaches is due to percentage attribution of DevOps revenue. For example, in the IDC report, it specified a certain percentage of Atlassian revenue for DevOps, but in the bottoms up analysis most of Atlassian revenue would have been counted since we looked at all project/portfolio management revenue.
Nearly [half of organizations](https://drive.google.com/file/d/17ZSI2hGg3RK168KHktFOiyyzRA93uMbd/view?usp=sharing) still have not adopted DevOps methodologies, despite [data](https://drive.google.com/file/d/17MNecg84AepxWlSDB5HjNBrCJggaS9tP/view?usp=sharing) that indicates far higher revenue growth for organizations that do so. Migrating a code base to a modern, Git-backed source control platform like GitLab can often be the first step in a DevOps transformation. As such, we must provide industry-leading solutions in source code and code review, as this is not only the entry into DevOps for our customers, but typically the entry into the GitLab platform. Once a user has begun utilizing repositories and code review features like Merge Requests, they often shift “left” and “right” to explore and utilize other capabilities in GitLab, such as CI and project management features.
Per our [Stage Monthly Active User data](https://about.gitlab.com/handbook/product/dev-section-performance-indicators/) we know that Create and Plan have the highest usage amongst GitLab stages. As such, these stages must focus on security fixes, bug fixes, performance improvements, UX improvements, and depth more than other areas of GitLab.
### Dev Section Accomplishment, News, and Updates
#### Section News & Team Member Updates
* Eric Brinkman will be transitionng out of the company at the end of January
* [David DeSanto's responsibilities have expanded to include leading the Dev and Sec Sections](https://gitlab.slack.com/archives/CL55Q4U0K/p1612561609472800)
* [We are actively hiring Group Manager, Product Management roles for the Create, Manage, and Plan stages](https://gitlab.com/gitlab-com/Product/-/issues/2127)
 
#### Important PI Highlights
1. Usage by self-managed users [increased 23%](https://about.gitlab.com/handbook/product/dev-section-performance-indicators/#manage-manageoptimize---smau-gmau---mau-viewing-analytics-features) in December. We have been focused on improving instance-level analytics over the past 3 milestones and the data shows that these features are being adopted.
1. We exceeded our 30k group SAML logins per month target!
1. The "health status" feature usage is almost non-existent and we should consider down-tiering or continuing to iterate on it by automating it and integrating it into Boards and Roadmaps.
1. Quantitative issue field level data validates that less frequently used fields – such as setting confidentiality and locking an issue – should be moved into the secondary menu within the issue header to decrease clutter in the sidebar.
1. Gitaly cluster instances [continue to increase](https://about.gitlab.com/handbook/product/dev-section-performance-indicators/#creategitaly---other---unique-instances-with-gitaly-cluster-enabled) and the reference architecture has been updated with recommendations for Gitaly Cluster for 13.8.
1. [Dev Section exceeded TMAU target of 2.73M by 1.4% by end of FY21](https://about.gitlab.com/handbook/product/dev-section-performance-indicators/#dev---section-tmau---estimated--recorded-sum-of-dev-section-smau)
1. [Manage:Access experienced 10% growth MoM during the holiday season](https://about.gitlab.com/handbook/product/dev-section-performance-indicators/#manageaccess---paid-gmau---mau-using-paid-saml)
1. [Plan:Project Management exceeded its quarterly metrics target in January!](https://about.gitlab.com/handbook/product/dev-section-performance-indicators/#plan-planproject-management---smau-paid-gmau---mau-interacting-with-issues)
1. [Plan:Product Planning exceeded its quarterly metrics target in January!](https://about.gitlab.com/handbook/product/dev-section-performance-indicators/#planproduct-planning---paid-gmau---mau-creating-epics-each-month)
1. [Interacting with Iterations MAU increased by 52% MoM!](https://about.gitlab.com/handbook/product/dev-section-performance-indicators/#plan-planproject-management---smau-paid-gmau---mau-interacting-with-issues)
1. [Create:Ecosystem Total Active Project Integrations passed 5M!](https://about.gitlab.com/handbook/product/dev-section-performance-indicators/#createecosystem---other---total-active-project-integrations)
 
#### Recent Accomplishments
1. [Merge Request Reviewers](https://gitlab.com/groups/gitlab-org/-/epics/1823)
......@@ -47,14 +58,6 @@ Last Reviewed: 2021-01-12
1. [POC for Settings cascading](https://gitlab.com/gitlab-org/gitlab/-/issues/291082)
 
 
## Dev Section Overview
The Dev Section is made up of the [Manage](/handbook/product/categories/#manage-stage), [Plan](/handbook/product/categories/#plan-stage), and [Create](/handbook/product/categories/#create-stage) stages of the DevOps lifecycle. The scope for the Dev section is wide and encompasses a number of analyst categories including Value Stream Management, Project Portfolio Management, Enterprise Agile Planning Tools, Source Code Management, IDEs, Design Management, and even ITSM. It is difficult to truly estimate TAM for the Dev Section, as our scope includes so many components from various industries, but research from IDC indicates the estimated [TAM](https://docs.google.com/spreadsheets/d/1LO57cmXHDjE4QRf6NscRilpYA1mlXHeLFwM_tWlzcwI/edit?ts=5ddb7489#gid=1474156035 in 2020 is roughly ~$2B, growing to ~$4.3B in 2024 (18.31% CAGR). Analysis: [Manage](https://docs.google.com/spreadsheets/d/1357Zwbf0yTjcFBuCdX2HnNLBaF9uWnW7Auv4F94aoSo/edit#gid=0) [Plan](https://docs.google.com/spreadsheets/d/1dDNSR_mE4peeOc_3Xhqm_VLoTyk4gSbcbiGfuMrOg6g/edit#gid=0) [Create](https://docs.google.com/spreadsheets/d/1KSwTVPIvMO8IXkMqA40Ms1rL-glmo-w7MjZvUrjMFGA/edit#gid=0). NOTE: The large disparity in the TAM/SAM approaches is due to percentage attribution of DevOps revenue. For example, in the IDC report, it specified a certain percentage of Atlassian revenue for DevOps, but in the bottoms up analysis most of Atlassian revenue would have been counted since we looked at all project/portfolio management revenue.
Nearly [half of organizations](https://drive.google.com/file/d/17ZSI2hGg3RK168KHktFOiyyzRA93uMbd/view?usp=sharing) still have not adopted DevOps methodologies, despite [data](https://drive.google.com/file/d/17MNecg84AepxWlSDB5HjNBrCJggaS9tP/view?usp=sharing) that indicates far higher revenue growth for organizations that do so. Migrating a code base to a modern, Git-backed source control platform like GitLab can often be the first step in a DevOps transformation. As such, we must provide industry-leading solutions in source code and code review, as this is not only the entry into DevOps for our customers, but typically the entry into the GitLab platform. Once a user has begun utilizing repositories and code review features like Merge Requests, they often shift “left” and “right” to explore and utilize other capabilities in GitLab, such as CI and project management features.
Per our [Stage Monthly Active User data](https://about.gitlab.com/handbook/product/dev-section-performance-indicators/) we know that Create and Plan have the highest usage amongst GitLab stages. As such, these stages must focus on security fixes, bug fixes, performance improvements, UX improvements, and depth more than other areas of GitLab.
## Dev Section FY22 Themes
 
The primary themes for the Product department in FY22 are:
......
......@@ -124,8 +124,8 @@ page and a complete list of upcoming features can be found on the [Upcoming Rele
 
#### Section & team member updates
 
* [David DeSanto's responsibility was expanded to include leading the Dev Section as well](https://gitlab.slack.com/archives/CL55Q4U0K/p1612561609472800)
* We have opened a Director, Product Management - Sec role, reporting to David, and are actively recruiting
* [David DeSanto's responsibilities have expanded to include leading the Dev and Sec Sections](https://gitlab.slack.com/archives/CL55Q4U0K/p1612561609472800)
* [We are actively hiring a Director, Product Management role for the Secure and Protect stages](https://gitlab.com/gitlab-com/Product/-/issues/2127)
 
#### Important PI milestones
 
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment