Code Quality Category Maturity Research
What’s this issue all about?
We want to measure the maturity of the Code Quality category for a scheduled move in FY22 Q2.
What hypotheses and/or assumptions do you have?
We assume this category has met the main JTBD and that we WANT internal users to start leveraging the feature set and this will prove out they now could.
What questions are you trying to answer?
Can users complete their main JTBD:
- When I review a Merge Request, I want to see code quality violations introduced to the changed files, so I can maintain the quality of the project.
- When I review a Merge Request, I want to see how it will change the code quality of the project, so I can be confident it will still be high quality.
Core questions
- How would you review how code quality changed in this MR if you were reviewing it?
- How would you measure the change in code quality of the overall project if you merged this MR now?
Additional questions
TBD
What persona, persona segment, or customer type experiences the problem most acutely?
Developers.
What business decisions will be made based on this information?
The maturity of Code Quality will increase OR stay put and we will know more validation research is needed.
Links / References
Edited by James Heimbuck