5.3 KiB
5.3 KiB
Experiment summary
We believe that... {describe your hypothesis in one sentence}
To verify that, we will... {describe your test in one sentence}
And we’ll measure the impact on... {metrics}
Hypothesis
Business problem
Supporting data
Expected outcome
Experiment design & implementation
ICE score
| Impact | Confidence | Ease | Score |
|---|---|---|---|
| value 1 | value 2 | value 3 | Average(1:3) |
Known assumptions
Results, lessons learned, next steps
Checklist
- Fill in the experiment summary and write more about the details of the experiment in the rest of the issue description. Some of these may be filled in through time (the "Result, learnings, next steps" section for example) but at least the experiment summary should be filled in right from the start.
- Add the label of the
group::that will work on this experiment (if known). - Mention the Product Manager, Engineering Manager, and at least one Product Designer from the group that owns the part of the product that the experiment will affect.
- Fill in the values in the ICE score table ping other team members for the values you aren’t confident about (i.e. engineering should almost always fill out the ease section). Add the ~"ICE Score Needed" label to indicate that the score is incomplete.
- Replace the ~"ICE Score Needed" with an ICE low/medium/high score label once all values in the ICE table have been added.
- Mention the [at]gitlab-core-team team and ask for their feedback.
/label ~"workflow::validation backlog" ~"experiment idea"