What does the beta in “beta software” really mean?

The is an interesting article on zdnet today entitled A long winding road out of beta. In the article Paul Festna comments on the fact that a lot of companies are now performing the Beta stage of software development in public and for a long period of time.

I think that Paul is missing the point here about what the Beta in “Beta Software” really means. I do agree that in the classic software development process the beta stage could be described some what like this:

The beta version, named for the second letter of the Greek alphabet, typically refers to the second stage of software testing. Traditionally distributed to a limited group of testers, it follows the alpha version, which is tested in the lab


This description doesn’t map very well on to software like flikr or gmail. Both of these products are going through a long beta cycle. In fact I suspect that during this process many new features have been introduced and at the introduction of each one your traditional beta cycle really recommences. In traditional software development this would have been obvious to the beta tester because the version number of the software they were using would have been incremented. However, the web based software that we are discussing here doesn’t really have a user visible version number and as such these changes are not obvious.

To me as a software developer the different stages of software development mean different things as following:

  1. Alpha – The software is functional to some degree, it has some if not all the features desired for the current release. It is possible that it has serious bugs (or features!).
  2. Beta – The software is feature complete for the current version. We need to find out from our users whether or not it does what they expect and that the way in which it works fits there usage pattern.
  3. Release Candidate – This is the result of fixing any issues found in the Beta version, without adding any new features, new features would require another Beta release.
  4. Release Product – The product is finished, the next version (if it is to be developed further) will have a set of new features/ incremental improvements

One Response to “What does the beta in “beta software” really mean?”

  1. Daniel Moth says:

    Also check out this comment (http://blogs.msdn.com/somasegar/archive/2005/02/13/371938.aspx) which brings into the picture CTPs and “go-live”.



d
go to dashboard
l
go to login
h
show/hide help
e
edit post/page
r
comment on post/page
m
go to moderate comments
esc
cancel
%d bloggers like this:
Skip to toolbar