Open Solution Validation Issues (Dev Section)

Context

https://about.gitlab.com/handbook/product-development-flow/#validation-phase-3-solution-validation

Note: Solution validation is only needed after designs or solutions have been proposed. If you lack confidence in a specific direction or if there is a high risk in moving forward without user validation, then continue with these steps. If you are uncertain, whether to move forward, reach out to your Product Design Manager. If you have any questions regarding what type of research you should be engaging in for a particular problem, talk to your manager first for their support. If you are looking for feedback during any part of the research process, ask your manager first for guidance.

Product Designer creates a new issue using the Solution validation template in the GitLab project. The issue will automatically apply the workflowsolution validation label. Link the associated Opportunity Canvas and design-related issues. Assign the new issue to yourself, the PM, and the Product Design Manager. PM and Product Designer discuss user recruitment needs and clarify the research study's goals and hypotheses. Once a draft is complete, the Product Design Manager reviews and provides feedback. Product Designer begins crafting a screening survey in Qualtrics

Open Research Issues

Manage
  • FY21-Q1 Manage UX OKR: Tables - end-user usability testing: #670 (closed)
  • FY21-Q1 Manage UX OKR: Tables - GitLab design/developer usability testing : #695 (closed)
  • Compliance Dashboard Prototype #792 (closed)
Plan
  • Tasks and Issue Task Lists as a first class asset: #760 (closed) / #615 (closed)
  • Requirements Documentation MVC - Usability Testing: #627 (closed) (this issue may be updated or closed depending on Nick's approach)
Create
Ecosystem
  • New Integrations and Service Templates usage at Instance and Group levels: #789 (closed)
  • Jira Transition ID update (no research issue yet)

Resources

Edited by Daniel Mora