Map themes to epics and issues

Problem

Based on initial feedback from the primary stakeholders in the Net ARR meeting, in order for the customer requested issues/epics prioritization model (www-gitlab-com!94444 (merged)) to provide a more automated, quantifiable solution than the "Top ARR Drivers" spreadsheet currently provides (internal: https://docs.google.com/spreadsheets/d/1JdtaZYO90pR4_NQgSZRu9qdGuMrFj_H6qkBs5tFMeRc/edit#gid=0), we need a way to map customer value (retained + growth) to themes in order aggregate them within the prioritization dashboards.

Proposal

  • Operationalize a scoped label schema for product themes and subthemes.
  • Subthemes (ex: https://about.gitlab.com/direction/#gitlab-hosted-first) will be manually added by relevant individuals and triage operations will automatically apply the theme labels based on a mapping maintained in a yml file.
  • Themes can be driven top-down. Product managers are also encouraged to create their own themes to bubble up investment opportunities organically.
graph TD
     B["theme:: ... (Subtheme)"] --> A["investment:: ... (Theme)"]
     I[Issue/Epic] --> B
     A --> G[Growth Value]
     A --> R[Retention Value]
     S[SFDC Links] --> I 
     Z[Zendesk Links] --> I

Tasks

Change management:

Integration into prioritization model + dashboards:

  • Get new vendor SOW approved
  • Create implementation issue for vendor
  • Coordinate with data team (Israel as a starting point)
  • Add aggregation by theme/subtheme
  • Add charts to relevant dashboards
Edited by Gabe Weaver