This outline example is a general guideline of how the Beta process normally takes place...
The initial sign up period is used to determine the right sites based on criteria defined by the program team. The General Interest Survey included on this page is instrumental in helping the Beta Team gather information and find customer matches for our current Beta program. If there is a match, additional surveys and information will be required before the :productivePRO Beta Team can make a final decision.
Selected sites will receive their first beta build with documentation and are expected to begin testing immediately. Sites will use our web based beta feedback forum to report issues in a timely manor so the Beta Team can prioritize for fixes in follow up beta drops. The Beta team will hold weekly conference calls, giving sites the opportunity to provide verbal feedback directly to the Beta Team, and online surveys will be conducted for each beta drop to track sites perception of the product(s) over time. As issues are addressed, sites will be asked to verify fixes and eventually repeat the test cycle with a new beta build, which varies depending on the program. Once the established exit criteria has been met through conference calls, bug report status, and final surveys, beta will then proceed into the final release stages prior to first customer shipment “FCS”.