From Merriam-Webster Online Dictionary

Beta
Pronunciation: 'bA-t&, chiefly British 'bE-
Function: noun
Etymology: Middle English betha, from Latin beta, from Greek bEta, of Semitic origin; akin to Hebrew bEth beth
1: the 2d letter of the Greek alphabet

Software
Pronunciation: 'soft-"war, -"wer
Function: noun
1: something used or associated with and usually contrasted with hardware: as a : the entire set of programs, procedures, and related documentation associated with a system and especially a computer system; specifically : computer programs

test
1: to put to test or proof
1 a: to undergo a test b : to be assigned a standing or evaluation on the basis of tests
2: to apply a test as a means of analysis or diagnosis

test·ing
Function: adjective
1: requiring maximum effort or ability

==========================

So, Beta Software Testing could then be described as:
1: the second evaluation of computer programs undergoing evaluation to gain analysis and diagnostic results.

Software companies (Microsoft included) often let their customers get a first look at their software through beta testing programs before the software is ready to release to retail outlets. In a way, you can think of beta software testing as a kind of dogfooding because of the nature of the bits not being fully vetted with features and of bugs readily found yet the software is being used by customers.

So if beta software testing is a first look for the customer at a software program, what makes Beta Software Testing (Beta Testing) the second evaluation instead of the first? Beta software testing is second due to the extensive testing and dogfooding that was done by the software company on the software to stabilize it prior to the release of the beta software to the beta testing program. Beta software however shouldn't be used in production environments unless specifically stated by the software company that it can because beta software may not have all of the features implemented fully or implemented to where they properly work in each situation that may be available in the released version of the software.

There are many different types of beta testing programs consisting of numerous levels of customers and various depths of beta software usage. Some beta testing programs consist of partnerships between the software companies and their customer (or partner) where there are strict guidelines of software usage and legal non disclosure agreements made between the software company and their partner using the "beta software." While other beta programs are less restrictive and include the general public or preferred customers. While each beta testing program has its benefits, different aspects of evaluation needed by the software company and the nature of the software being beta tested often dictate the type of beta testing program used by the software company.

One beta testing program that we use here in Microsoft Exchange is called the Technology Adoption Program (TAP). Our TAP has the strict guidelines and legal agreements made, support given and non disclosure is set. We have teams of people who work directly with our partners to help them install and configure the software, gather feedback from the partners and to help them with issues. We also have a general beta testing program where more broad range of customers get access to the beta software but do not get the full benefits that our TAP partners receive.

Beta software testing sessions are tracked by number with the first normally being called Beta1 or B1 and the second named Beta2, third named Beta3, etc. The number of beta testing sessions depends upon the software company and within it the group holding the beta software testing session. Some software companies or groups within a large software company, only hold a couple of beta software testing sessions while others hold many more. The duration of each beta software testing session is also dependent upon the software company or group within the software company. Sometimes, marketing factors and/or feedback received from the beta software testers dictate if another session is needed to help stabilize the bits more or if there's a need to change the feature set to better penetrate the market.

All in all, beta software testing it is a good way to help stabilize the software and to get early feedback from customers on your software. The sooner you hear from your customers, the better you can make your software so I suggest that you get a beta software testing program together for your software application. If you are not creating a software application, I suggest that you join a beta testing program for one of the software applications you use. Your involvement in a beta software testing program could help not only the software company but your business too!

For more information on various Microsoft Technology Adoption Programs, go to http://www.microsoft.com and search on Technology Adoption Program.

For more information on Microsoft Beta Testing, go to http://www.microsoft.com and search on Microsoft Beta Testing.