Why did S2 Bug MTTC spike in January
Description
The S2 Bug MTTC almost doubled from December to January moving from 53.4 to 102.99
Hypothesis
An increased proportion of old bugs were closed due to not being recreateable or fixed much earlier. This is due to increasing focus on severity2 bug from Engineering Managers.
Investigation
Charts are found at https://app.periscopedata.com/app/gitlab/825406/S2-MTTC-Close-Exploratory-Analysis
Findings
- Frequency for closed bug with no milestone or %Backlog increased from 6 to 23 which is change by percentage of 13.6% (
6/44
) to 32.8% (23/70
) of all severity2 bug closed that month: https://app.periscopedata.com/app/gitlab/825406/S2-MTTC-Close-Exploratory-Analysis?widget=11039458&udv=0- I will refer to this group as invalid milestone bugs below
- MTTC P80 for Invalid Milestone is at a 24 month high: https://app.periscopedata.com/app/gitlab/825406/S2-MTTC-Close-Exploratory-Analysis?widget=11038744&udv=0
- Average MTTC for all bugs with invalid milestone is at 24 month high in January for completed months. February looks to surpass this: https://app.periscopedata.com/app/gitlab/825406/S2-MTTC-Close-Exploratory-Analysis?widget=11038690&udv=0
Corrective Actions
-
Create a MTTC dashboard with additional charts with additional context for Invalid Milestone population. Keep KPI defined as is. - https://docs.google.com/document/d/1ekx4wX5B77_3kR0P14F7YZR56oxfIOAe0ts-NxxR7eM/edit#bookmark=id.8agbajhg85po
Edited by Kyle Wiebers