Verify:Testing - Code Quality JTBD Research
What’s this issue all about?
The Verify:Testing group has been grooming the Jobs To Be Done (JTBD) for the Code Quality Category. The next step is to connect with our users to understand what JTBD they would prioritize. Our plan is to gather data around what JTBD would be required to migrate to Gitlab's Code Quality category to the Viable Maturity.
Who is the target user of the feature?
Engineers and team leads. A technical buyer persona might also benefit if we better understand what could be blocking that process.
What questions are you trying to answer?
Core questions
"Which of these JTBD/stories are necessary for you to be confident you know which parts of a project's code are low quality and should be addressed."
Additional questions
- Are the Jobs listed all of the jobs that apply to Code Quality?
- Which of the JTBD would you say directly impacts the users day to day work?
- Which of the JTBD would have the lowest impact on the users day-to-day?
- How do users perceive the maturity of their most important JTBD at GitLab? (interesting comparison could be between current GitLab and Non-GitLab users)
- Of the JTBD the user rated as highly impactful, what improvements or features would they expect/desire a solution to offer?
What hypotheses and/or assumptions do you have?
- Some of the JTBD will consistently be ranked as important while others are unimpactful. There will also be more consistency in responses when user types are compared independently.
- There might be some JTBD that are important or relevant to our users that we have missed.
What decisions will you make based on the research findings?
- What JTBD will be focused on next in priority for research, design, and product development.
- What JTBD will be getting user based UX Scorecards.
When do you need this research to be completed? (Milestone or date)
Findings
After having the survey in the field for almost 5 months we received 28 responses.
The majority of the survey takers match up with our Developer Persona, so we will tailor the CMS Scorecard for them. A secondary round of interviews for the Manager persona may take at some point in the future.
Based on our survey we found the jobs these users care about are:
- Primary job - Setup Static analysis so I can get to writing code
- Secondary Job - Review a list of identified issues in an MR
For our Category maturity scorecard we will test on the Secondary job, utilizing the features within the category. A secondary study focused on setup may occur at a later time.