The Beta test is a commonly accepted method of stress testing a product in the customer's operating environment. Beta tests can be expensive and high-risk yet the data they provide is often crucial to a company's and product's success.

Beta tests are often performed for several reasons:

• Early customer "quotable quotes" for trade publication – this is the most likely reason for Marketing to perform a Beta test
• An opportunity to put the product "in the wild" – this is the most common reason for Engineering to field a Beta test
• Early product evaluation by the customer – this is the most common reason for Sales to promote a Beta test
• An opportunity to evaluate an early release of the product – this is the most common reason a Customer wants to participate in a Beta test

Beta tests can provide a rich source of information about the product's behavior in an operational environment. They can also be the source of embarrassment for the company and disillusionment by the customer.

Phase II has provided Beta test planning services for many years, combining its planning and product development expertise. Some of the key elements of a Beta test plan are:

• Identifying the test objectives – what is to be measured and when will the test be over?
• Determining the test scope – how much of the product needs to be tested, and which customers need to test which elements?
• Calibrating stakeholder expectations – who is going to participate, how will their participation be monitored and rewarded, what is expected to come of the test?
• Creating supporting documentation and materials
• Determining the depth and breadth of training required to complete the test
• Incorporating a usability test

This last element deserves a final comment. A common misconception is that Beta tests can be used as usability tests. Beta tests are not usability tests. Customer reaction to a product for purposes of marketing quotes are not the same as user reactions to the usability of the product.

While it is true that Beta tests are good opportunities to visit with customers, train customers and provide them the opportunity to ask questions about the product, these activities often work at cross purposes for usability tests. On the flip side, because the customer is already setting aside time for orientation, training and setup of the Beta test, it can be an excellent time to slip in a usability test or two.

Phase II provides test planning for both Beta and Usability tests, either separately or together.