Create Next Prioritization team dashboards in respective team pages
Objectives
Direction from @meks:
- Have teams review their backlog & maintain MR hygiene, so the intent is for EMs to embed two dashboards under their respective development team pages in our external handbook.
- Note: The ones under
engineering/metrics
are a reference data catalogue. Similar to our global prioritization list partial, they are still SSoT but can be embedded in many places.
- Note: The ones under
- By standardizing this, we will have a few examples done, and have the remaining done by EMs, with step by step instructions on how to update their handbook pages.
- Not all team pages currently exist, so we will take this as an opportunity to do handbook structure maintenance. We will take lead on this and point to missing pages since Eng Analytics already has it mapped out
Dashboard
Cross functional backlog dashboard
- Security issues (pastdue)
- Infradev issues (pastdue)
- SUS impacting issues by severity
- Bugs by severity
MR types dashboard
- Historical MR types
- Current month MR types
- List of recent MRs (2 months)
Team pages
Create the 2 dashboards above
- From https://about.gitlab.com/handbook/engineering/metrics/
- To team pages under:
- https://about.gitlab.com/handbook/engineering/development/dev/
- https://about.gitlab.com/handbook/engineering/development/sec/
- https://about.gitlab.com/handbook/engineering/development/ops/
- https://about.gitlab.com/handbook/engineering/development/fulfillment/
- https://about.gitlab.com/handbook/engineering/development/growth/
- https://about.gitlab.com/handbook/engineering/development/enablement/
- https://about.gitlab.com/handbook/engineering/development/modelops/
Instructions for EMs
Add two links - Team page
and MR
(see others' examples as listed below)
How?
- Add a link to your Team page
- Add a link to your MR, which adds two dashboards to your team page using the snippet below or by referencing the model MR. Please make sure to edit your group name in the code. The example below is for the Editor group. Feel free to assign @lmai1 as a reviewer on the MR. (Note that the
filter_value
parameter is used for theteam_group
filter in the dashboard)
<%= partial "handbook/engineering/metrics/partials/_cross_functional_dashboard.erb", locals: { filter_value: "Editor" } %>
For managers that manage more than one group, please follow this MR.
Check the box once complete.
Dev Sub-department - @timzallmann
-
devopscreate - @dsatcher
-
Source Code - @sean_carroll -
Code Review - @sean_carroll / @andr3 -
Integrations - @arturoherrero -
Editor
-
-
devopsmanage - @m_gill
-
Access - @jarka -
Compliance - @dennis -
Import - @wortschi -
Optimize - @blabuschagne -
Workspace - @mksionek
-
-
Gitaly - @andrashorvath -
Project Management - @donaldcook -
Product Planning -
Foundations - @leipert
Enablement Sub-department - @cdu1
-
Distribution -
Geo -
Memory -
Global Search -
Database -
Sharding
Ops Sub-department - @sgoldstein
-
devopsverify - @cheryl.li
-
Pipeline Execution - @marknuzzo
-
Pipeline Authoring - @marknuzzo
-
Runner - @erushton
-
Pipeline Insights - @shampton
-
-
devopsrelease devopsconfigure devopspackage - @dcroft
-
Release - @nicolewilliams -
Configure - @nmezzopera -
Package
-
-
Monitor:Respond - @crystalpoole
Fulfillment Sub-Department - @jeromezng
-
Self-Service Purchase - @rhardarson -
Billing and Subscription Management - @rhardarson -
Provision - @jameslopez -
Utilization - @csouthard -
Fulfillment Platform - @jameslopez
Growth Sub-Department - @pcalder
-
Activation - ? - Team page: [on hold]
- MR: n/a
-
Adoption - @jayswain -
Conversion - @kniechajewicz -
Expansion - @kniechajewicz -
Product Intelligence - @alinamihaila
Secure Sub-department - @twoodham
-
Static Analysis - @twoodham -
Dynamic Analysis - @sethgitlab -
Composition Analysis - @gonzoyumo -
Threat Insights -
Vulnerability Research - @mark.art
-
Container Security - @nmccorrison
Anti-Abuse - @pcalder
-
Anti-Abuse - @jayswain
ModelOps - @mray2020
-
Applied ML - @mray2020