Survey for monitoring feature prioritization

Links

• #882 (closed) Research request
• #883 (closed) Recruitment request
• Project folder with Research plan, Survey and Features list
• Survey
  • Version 1 (Please input Test into the Job title field if you don't want us to analyze your answer)
• Analysis spreadsheets
  • Internal – GitLab SREs
  • External – Firstlook
• Dovetail project

Checklist

Design survey

• Draft the survey
• Create a list of features
• Transfer the survey questions to Qualtrics @akiripolsky

Pilot survey

• Fill the survey and fix any problematic pieces in the MR
• Fix the survey in Qualtrics @akiripolsky @nadia_sotnikova

Collect responses – Round 1 – Internal

• Distribute the survey to GitLab SRE team @dhershkovitch
• Improve the questionnaire based on the feedback from SREs @akiripolsky
• Input the data collected to the analysis spreadsheet @akiripolsky

Collect responses – Round 2 – External

• Open a Recruiting request issue. Assign it to the relevant Research Coordinator @dhershkovitch
• When the survey is ready, ask Emily in the recruitment issue to send the survey to external participants from FirstLook @akiripolsky
• Notify Research Coordinator of survey closure. @akiripolsky

Document findings

• Analyze the data @akiripolsky
• Document the results @dhershkovitch
• Document insights in Dovetail
• Create actionable insight issue
• Update Metrics direction page
• Update the Problem validation research issue. Link to findings in Dovetail. Unmark as confidential if applicable. Close issue.

Survey about requirements for monitoring/Feature description guidelines.md

+# Feature description guideline
+
+## Guidelines
+- Clear and sufficiently detailed description that sets the feature into 
+necessary system context.
+- Simple language without GitLab lingo or sales pitching
+- Describe proper features, not MVCs. 
+
+### Feature description structure
+- Feature: What can the user see in the UI
+- Behavior: What does it do
+- Value: Why do we want to introduce it