Experiment Checklist

Experiments are not tested by the QA Team.
Therefore the Developer and The Product team have the full responsibility of the QA around the experiments.
In Addition to this responsibility the Developer who create the experiment must make sure there are no "side effects" and no regressions by the new experiment.

All the experiment related code should be toggled.
Which means that we can be able to completely shut down the experiment remotly if needed.

The code of the experiment must be marked with proper comment to be easy to notice, find and delete later on.

When coding new experiment - Always keep in mind that this code is temporary and need to be easy to remove.

Document you experiment in the Trello board and notify the team about the new experiment. 

If the experiment is a complex one and may affect all of the users consider to get QA involved.

All of the experiment's configuration should be set to OFF by default.