Split Test Calendar ... Best Practice?
So our Executives are urging us to create some sort of a split test calendar that would show past tests, performance, and future tests scheduled for future dates. I was wondering if anyone here has something like that in their company.
Each row contains:
1- the name of the test
2- brands, sites, and platforms affected (we have 4 brands, 6-8 sites (geographical) per brand, and two platforms - mobile and desktop)
3- DEV task (if any) that the test is tied to
4- web analytics integration (which SiteCatalyst eVar or prop)
5- Start Date
6- End Date
7- Trend Indicator (red down arrow, green up arrow, yellowish horizontal arrow)
The columns are the calendar days - the cells are filled in with a color coded representing ended, active, and scheduled run dates (like a horizontal bar chart).
Tests that are prioritized but do not have a planned start date appear at the bottom of the list.
This is a great question and really shows your organization is focused on the strategy and value of testing, not just the executional mechanics.
If we're specifically focusing on a testing calendar, the best practice is really to find or define a documentation style or practice that works best for you. If you want to borrow from what another organization has done, great! If you want to build new documentation from the ground up, fabulous!
Mozilla, one of our customers, created a testing wiki to showcase their ideas and results. They link to plan and results templates. Another large household and professional services provider has created an internal blog where they publish a running dialog on their tests and results.
We'd love to hear and see what your team has or will come up with!
Solutions Architect | Optimizely, Inc.