Determine model inputs for issues that do not have SFDC links
Problem To Solve
We can easily define the inputs for two of the four value profiles -- increase revenue, protect revenue -- because they map cleanly to quantifiable dollars via SFDC links. We need to figure out to determine model inputs for the other types of issues on our prioritization table so that we can calculate Cost of Delay based on monetary value and an urgency profile.
Context
This is a difficult issue, but it is worth keeping in mind some of the guidelines for estimating value:
- Estimate the beneficial effects of the change
- Make the value equal to the cost of alternatives
- Make assumptions visible
- The goal is accuracy, not precision.
- The Lean “5-Whys” technique can help in identifying the value of a feature. Keep asking “why” until you are able to identify one or more of these benefit types [value profiles].
Tasks
For each of these types of Issues, determine how value and urgency can be quantified:
| Description | Label | Model Inputs |
|---|---|---|
| Security Fixes | security |
Value: TBD Urgency: TBD
|
| Data-loss prevention | data loss |
Value: TBD Urgency: TBD
|
| Availability | availability |
Value: TBD Urgency: TBD
|
| Fixing regressions | regression |
Value: TBD Urgency: TBD
|
| Availability and Performance Refinement |
infradev, performance-refinement
|
Value: TBD Urgency: TBD
|
| Instrumentation improvements, particularly for XMAU | instrumentation |
Value: TBD Urgency: TBD
|
| Usability Improvements and User Experience to drive xMAU |
enhancement, UX debt
|
Value: TBD Urgency: TBD
|
| Identified For Dogfooding |
Dogfooding: Build in GitLab, Dogfooding: Rebuild in GitLab
|
Value: TBD Urgency: TBD
|
| Velocity of new features, technical debt, community contributions, and all other improvements |
direction, feature, technical debt
|
Value: TBD Urgency: TBD
|
| Behaviors that yield higher predictability | predictability |
Value: TBD Urgency: TBD
|
Examples To Use
- severity1 security issue - Improper Access Control on Deploy Token
- ~customer ~severity1 ~availability bug - CI Artifact upload 500 error
- regression bug - GitLab CI after_script is not executed
Edited by Gabe Weaver