Load Testing Validation
Problem Statement
Gitlab users do not know how a change to their code has impacted its performance when running under load before deploy.
Reach
We believe this has small reach for the full user base but a large reach for our larger customers who are likely to make use of this feature (3.0).
Impact
We believe that once solved this will have a Medium impact for our customers.
Confidence
We have a High confidence this is a problem that needs solved today based on Gitlab's own Quality department developing their own solution.
Effort
We believe an MVC for this problem could be solved in one milestone by the testing team (2.0)
RICE Score - 150
Current status:
- 4 interviews were conducted in November / December 2019 with internal stakeholders in Quality and Development.
- Because we determined that the grouptesting would not move this to maturitycomplete by the end of 2020 the category was put on hold.
- Affinity mapping from interviews completed in March 2020 which spurred conversation to create a different screener / discussion guide (see next steps).
Next Steps:
- This is being closed for now to do more research later.
- I created a new Screener and discussion guide for when we pick this up based learnings from the internal stakeholder interviews (see the personas in this discussion guide).
Edited by James Heimbuck