Productivity Portfolio

If the questions and comments I'm getting are a gauge, I think there is a misconception about what is alpha software. An alpha software release is not for the average user despite the ease at which you can find these apps on the Internet. This isn't like getting in on an IPO or the premiere of the newest box office thriller. Its more like spelunking and knowing whether you like the dark or it scares the hell out of you.

As the name suggests, the alpha release is the first in the software development cycle. It comes before beta and well before the final released product. In some cases, the program lacks functionality and documentation. Moreover, the program probably has had limited testing. The program may work fine in house, but that is no assurance it will work at your house. At the alpha development stage, the main purpose of the release is testing.

There are legitimate reasons why people would want to participate in such a test. Maybe you want to get a job at this company and figure it helps to know the product and provide feedback. You might also be a software or hardware developer that has a related product. In these instances, it may make sense to try an early release. For other people, I would suggest they review these questions and take precautions before installing alpha software on their computer.

10 Questions to ask before participating in an alpha program

1. Will you commit to providing the software company with good and useful information such as bug reports?

This item goes to my earlier statement about alpha releases and value. There is definite value in this type of testing. But for the developers to get real value and for the program to improve, testers need to make a time commitment. This is more than a commitment to install, but to actively use the product and communicate issues and problems.

2. Do you plan to install this software on a production environment?

If you answered yes, please tell me you don't work in genetic engineering or a at a nuclear power facility. Alpha and beta software should not be installed on a production system. The risks of losing data far outweigh the benefits you'll get.

If you want to participate, use the right equipment. Put the software on a machine that doesn't have critical data or interacts with other systems.

3. Will this software fix an existing software problem?

If this software doesn't fix or remedy a problem, ask yourself what benefits you expect.

4. Do you have current backups of your system?

Even if you install the software on a separate test machine, it helps to have a backup so you can easily restore the system to its previous working state.

5. Do you read End User License Agreements (EULA) and Readme files?

These documents offer more clues about the stability of the software. I suspect that if more people read these files before installation, there would be far fewer problems. Many readme or known issues pages outline problems you can expect. This advice also applies to production software.

6. Do you share the PC you plan to install the software on with someone else?

Lets just say I would be miffed if you installed alpha software on a machine I also used. Be mindful of others when using shared resources.

7. Do you have a high risk tolerance?

If you don't buy lottery tickets because of the odds, then you probably shouldn't install alpha software. Ive never encountered a software package, commercial or otherwise, that didn't have bugs. The odds are you will run into bugs.

8. If you're replacing a production version of the software does the alpha program need to work with add-ins such as extensions, toolbars and so on?

This is a case where programs can have their own ecosystem. As example, if you're installing an alpha version of a web browser, you'll want to know if it can co-exist with your current version. The same holds true with 3^rd party utilities as they seldom work with an alpha version.

9. Does the program have an installer and uninstaller?

This is a personal rule I follow when testing software. Ive run into too many programs that were either cumbersome to install or a royal pain to fully remove.

If possible try to use a software program that monitors the installation so you know what program files and registry entries were made to your system. This step can also help if one of these files gets flagged by your anti-virus or anti-spyware program.

10. Do you need support?

Yes, I know we all need a support system. The point is that the level of support may not be what you expect or need. Its not that the developers don't want to help you, but more of a resource allocation problem. At a minimum, there should be an online forum where testers can post their comments.

If you decide to participate, here are some tips Id suggest.

1. Always download the program from a reputable site. I would stick with the company or authors site.

2. Stay current with the releases. If the developer issues a new release, you should install it.

3. Never make a buying decision based on an alpha release. Too much can change between this first test release and the final version.

4. Finally, don't expect support from us ;-)