Define TAM inputs

This is part of the prioritization framework pilot #1563 (closed)

Proposed Labels

  • Value: value::low, value::medium, value::high
  • Urgency: urgency::low, urgency::medium, urgency::high
  • Value Profile: reason::grow, reason::protect

Tasks

  • Create easy to understand definitions for each value label
  • Create easy to understand definitions for each urgency label
  • Create easy to understand definitions for each value profile (other two will come later)
  • Update the Feedback Template with information and context on how to use the labels (and keep them up to date over time)
  • Determine how and where to set the Duration input (estimated weeks to complete issue / epic)

Working doc for model input definitions are here: https://docs.google.com/document/d/167F5YbEbdurp2_THJip0o-Lw48WOinh0OSfyaqDzETc/edit

Definitions: VALUE

  • value::low
    • Minimal or no business impact. Enhancement is requested but ‘nice to have’ - will not facilitate additional spend or growth. No direct impact on the operation of GitLab - no risk of downsell or churn in not addressing
  • value::medium
    • Some business impact. Important GitLab features are unavailable, but a workaround is available.
  • value::high
    • Significant business impact. If delivered, customer will upgrade/increase spend. Alternatively if not delivered, customer will downsell or churn. Important GitLab features are unavailable with no acceptable workaround. Serious impact on future growth.

URGENCY

  • urgency::low
    • Whenever possible
  • urgency::medium
    • Soon
  • urgency::high
    • ASAP

VALUE PROFILE

  • reason::grow
    • Increase product adoption and utilization (SMAU, uptiers, license count)
  • reason::protect
Edited by Sophie Pouliquen