Closed
Bug 1309010
Opened 8 years ago
Closed 8 years ago
Organize and Analyze TMO Survey Responses
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: frank, Assigned: frank)
References
Details
Attachments
(1 file)
2.31 MB,
text/html
|
Details |
Spreadsheet here: https://docs.google.com/spreadsheets/d/1IX2XmlaM6-0a8xvuNI41kAPyeLKFdaQBuZf6EGRpRV8 We need to organize responses, pinpoint issues, and respond to those that requested. We can use this to decide on next steps for the platform.
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → fbertsch
Updated•8 years ago
|
Points: --- → 2
Priority: -- → P1
Assignee | ||
Comment 1•8 years ago
|
||
The attached is a simple analysis of the survey, which gives an idea of what the responses looked like, and how people are using our platforms. In the spreadsheet, I have a list of bugs and a list of feature requests. So far I've sent out three emails to the volunteers, who just requested more information. There are ten more emails to send out, which should probe about their pain points, and provide any information they asked for. Finally, we need to more generally understand what these results are telling us. The most obvious is lack of documentation. The deeper one is easier monitoring, and more advanced TMO dashboard; ideally one that is grouped per-user, and does more deep analytics or statistics work. What this might mean is an open question, and one we should talk with advanced engineers about.
Assignee | ||
Comment 2•8 years ago
|
||
This is *finally* complete. Issues and feature requests have been created in the appropriate places from all of the comments. All people have been emailed.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•