Beta testing is a way to find out how the product behaves in the user environment with a limited number of selected users. It has many advantages:
• You can find out how the product behaves in a wider variety of configurations than it is possible to test in a test set-up.
• You can limit the damage done to your reputation if there are serious problems with the product.
• It allows your front line support to practice dealing with the calls related to the product with a limited volume of calls
• It exposes the product to a user base that you know is tolerant and “friendly” towards your product and has enough expertise to tell real problems from user error.
To gain maximum benefit from a beta test, it must be carefully prepared, conducted, and analyzed. If you plan to conduct a beta test, you can use the list below as a checklist, or ask Uniplus for assistance. The list is not exhaustive or sufficiently detailed to be a process definition. So you may be better advised to seek expert assistance.
• Design communication plan
• Design evaluation criteria
• Select pilot customers
• Invite them to participate
• Set up special help service
• Record
• Track
• Record all contacts from pilot customers
• Provide feedback
• Evaluate
• Provide feedback
