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/Features list.md

@@ -3,10 +3,15 @@
 Descriptions of features that we will present to the respondents.
 
 ## Guidelines
- 
 - Clear and sufficiently detailed description that sets the feature into 
 necessary system context.
-- Simple language without GitLab lingo or sales pitching.
+- 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
 
 ### Questions
 In the survey the questions about feature will be asked in a following way: 
@@ -25,83 +30,93 @@ In the survey the questions about feature will be asked in a following way:
      - I can tolerate it
      - I dislike it
 
-## Current experience
-Even though we will try to add as much context to each feature description, it
-is still necessary to provide at least general explanation of what system 
-are we talking about.
-<!-- Note: we need to align with the terminology charts or panels-->
-In GitLab a dashboard in a group of charts, a single dashboard can contain one or more chart
-
-
-
-
-<!-- Depends on the scope of this research study, 
-currently its not well defined.-->
-Dashboard consists of one or more panels that can contain chart or text. 
-Dashboard configuration is described in a text file that can be changed by users.
+## Current features
+- GitLab monitoring is... Consists of dashboards.
+- Dashboard consists of a number of panels. Each panel can contain a chart, 
+a numerical indicator or a static markdown text. It is possible to create new 
+and delete existing dashboards. 
+- Configuration of each dashboard is done by editing its configuration yaml file.
+- Alerts that are set on a metric are visualized on the metric chart. 
 
-## Features
+## New features
 
 ### Dashboard level
 
 ##### ⭐Import dashboard templates to create new dashboards
+Templates for yaml configuration files
+that you can choose when creating new dashboards. 
+Templates contain basic file structure, configuration examples and comments
+to speed up the dashboard creation process and improve consistency across dashboards.
 
 ##### ⭐Add variables to a dashboard
+Interactive 'quick configuration panel'
+where you can select specific variables of the dashboard right in the dashboard UI. 
+It will allow you to have smaller number of dashboards created and therefore 
+make dashboard management simpler. 
+
 <img src='./image_5.png' width=600px />
 
 ##### ⭐Out of the box dashboard for monitoring different technologies and services
-
-##### ⭐Ability to delete out of the box dashboards from Metrics
+A set of out-of-the-box dashboards for the most common technologies and services
+that are configured automatically when you set up monitoring in GitLab. 
+It will improve experience of users that just started using the monitoring 
+features of GitLab. 
 
 ##### ⭐Group dashboards into folders
-Group dashboard into folders
+Dashboard folders in the dropdown 
+that you can group your dashboards in
+to improve organization of your dashboards.  
 
 ##### ⭐Add tags to dashboard for easier search
-Add tag to a dashboard to better help you searching for a dashboard
+Tags with searchable keywords
+that you can assign to dashboards.
+It will allow you to find dashboards faster.
 
 ##### ⭐Add a special panel with custom hyperlinks
-<img src='./image_1.png' width=600px />
-
-Provide the ability to add hyper links from a dashboard to allow: 
+A special panel with a list of custom hyperlinks
+so you can drill down to a tool of your choice (e.g. another dashboard or external tool)
+right from the dashboard UI.
+To speed up navigation between different tools.
 
-* Drill down from a dashboard into another dashboard
-
-* Drill down from a dashboard to an external source
+<img src='./image_1.png' width=600px /> 
 
 ##### ⭐Rearange panels using drag and drop
-<img src='./image.png' width=600px />
+A possibility
+to rearrange panels using drag and drop rather than by editing the yaml file. 
 
-Current experience: the user can rearrange charts in a dashboard using a yml file
-Feature description: Rearrange charts on your dashboard using drag and drop functionality
+<img src='./image.png' width=600px />
 
-##### ⭐Resize panels with cursor cursor 
-Current experience: The panels in the dashboard are at fixed height and length
-Feature description: Resize a panel on a dashboard using a cursor
+##### ⭐Resize panels with cursor 
+A possibility
+to resize panels using cursor rather than by editing the yaml file.
 
 ### Panel level
 
 ##### ⭐Add custom hyperlinks to the options menu of a panel
-<img src='./image_2.png' width=600px />
-
-Provide the ability to add hyper links from a panel in a dashboard to allow 
+Custom hyperlink in the options menu of a panel,
+so you can drill down to a tool of your choice (e.g. another dashboard or external tool)
+right from the relevant panel.
+To speed up navigation between different tools.
 
-* Drill down from a chart to another chart
-
-* Drill down to an external source
+<img src='./image_2.png' width=600px />
 
 ##### ⭐Annotate metric charts
-<img src='./image_3.png' width=600px />
+Annotation, a vertical line in a chart that shows custom message on hover,
+so you can highlight an important point within the chart.
+To improve collaboration and informativeness of the chart.
 
-Annotation is a vertical line on a chart, when hovered it provide additional 
+<img src='./image_3.png' width=600px />
 
 ##### ⭐Configure alert directly from a metric chart
+A contextual alert configuration popup openable from within the metric chart
+where you can configure alerts without the necessity to navigate to a dedicated alert configuration page.
+It will improve the speed of alert configuration and provide better awareness of the underlying metric.
 
 ##### ⭐Add thresholds that do not trigger alerts
+
 <img src='./image_4.png' width=600px />
 
 Current experience: Thresholds and alerts are tightly coupled
 Feature: Allow the users to set and see diffrent thresholds without triggering an alert
 
 ##### ⭐Change the appearance of the line on a chart (color, width, dotted line, etc..)
-
-##### ⭐Ability to correlate between metric chart and logs