What tests are problematic
We think that customers have problems identifying tests that are "problematic". These are tests that may fail intermittently (are flaky), are slow either when passing or failing, are lumped together inefficiently , etc. This leads to long running pipelines and slow feedback cycles for developers and inefficient use of runners which can be a budget concern for VPs / Directors.
We think this impacts a large amount of our customers, around 50%, so score this a 6.0.
We think we can create a medium impact for both personas mentioned above so score this a 1.0.
We have high confidence this is a problem but low confidence we know which part of the problem to tackle first so score this with medium confidence, 80%.
We think this would take 1 milestone (or month) for a PM, Designer, FE and BE to build an MVC that shows improvement. We score this as (1 month x 4 people) -> 4.0
Overall score - 1.2
( Large Percentage Reach (6.0) x Medium Impact (1.0) x Medium Confidence (80%) ) / Effort (4.0) = 1.2 Rice Score