Fall, 1999

Companies which apply a formal beta process to software development have a competitive advantage. A formal beta process or beta cycle involves far more than sending the product to several customers for testing. A formal beta process is thorough and involves reviewing all features of the package beginning with documentation and ending with a detailed examination of the result with the actual methodology tailored to the specific product and needs. By verifying through the beta process that the product does deliver what has been promised, management is in a position to get maximum benefit in its dealings with its customers, its employees and shareholders, the technical press, investment community and other stakeholders.

Quality Assurance is not beta

Quality assurance is only one part of the testing process. It is not a substitute for a formal beta process. Take the case of the word processing software company which released an upgrade of its popular product to run on what was then a new platform. QA documented functionality tests of each feature and subsystems were supposed to ensure overall integrity and accuracy. While these worked in the laboratory at the Alpha stage, quality assurance didn’t keep up with the revisions that were taking place in the platform itself. The company lost market share when pressures from the marketing division pushed the product out the door quickly undermining the product’s image as a solid work processing program. The release, untested externally, thwarted efforts to expand users let alone keep its current customers.

The beta cycle process can help software development companies align themselves with the realities of the market and, most significantly, test interoperability. The product development life cycle consists of five stages:

• Investigation
• Laboratory
• Alpha
• Beta
• Release.

The use of the beta process can prevent embarrassment and the financial repercussions that will fall on any technology company whose results fail to meet the expectations of investment analysts.

A case in point, a major intranet developer which released a product offering instantaneous access. Its success in an earlier version was based on its ease of use creating access rules. The authentication was logon and password established by the administrator. The later release had secure authentication as a result of customer requests. Our company determined during the beta process several problem areas. Working with the various departments of this company, we quickly arrived at solutions and product that was placed in the jewel case was flawless.

Contact us
BetaWatch Inc. provides a formal beta process cycle. In our capacity as beta test project manager we work with all levels of your organization to ensure your software is thoroughly tested and meets all of your objectives. Other services offered include in-house training of your beta team. For a proposal on your specific need contact tgrafstein@betawatch.com