Implementation task coming out of spike T354952
Description
Create a satisfaction survey to product teams adopting Metrics Platform to create instruments
Use Case
To establish Metrics Platform baseline of measuring cumulative engineering time on instrument development given the following success criteria:
decrease the amount of engineering days required to create instruments by X%
User Story
As a product manager, I want to know the cumulative engineering time for instrumentation development to compare technical approaches, as well as the implementer's experience with using the Metrics Platform
Outcome
We have an idea of the approximate cumulative engineering time to build an instrument, and qualitative data about the implementer's experience with using Metrics Platform.
Acceptance Criteria
- Survey is publicly accessible (for MVP, spreadsheet is sufficient)
- Survey is sent to implementing engineer upon instrument completion.
- We have a mechanism for synthesizing/analyzing survey responses
Required
- Documentation
Technical Notes
In T354952#9511891, surveys were discussed as a low-tech solution for capturing developer satisfaction and cumulative engineering time on instrumentation building using Metrics Platform.
We could potentially automate the sending of surveys based on merge data of stream configs from Gerrit API. Or if we prefer to manage manually for the time being, we can ask partner product teams to fill out surveys after instrumentation completion.
Example surveys:
- https://docs.google.com/forms/d/13Lz23F0O83SUfr9-8HB-Dw-YGRC2Ci5HjR5C9fC00ng/edit
- https://docs.google.com/forms/d/11aj5s35d6z7lzHqouhWm44-pSck2ui5wpns-jp2zySs/edit
Example survey reports:
- https://docs.google.com/document/d/1-0SVGlJnTmxCgTQ7JXb9cHe3l3UFQeCvx77m07962EY/edit#heading=h.vyt1m0p2t0j6
- https://docs.google.com/document/d/1qadOmeJbeStpKqvJL_1FwkJ5JGjr28Re3clVIO3mxSo/edit#heading=h.vyt1m0p2t0j6
Survey methodologies: