The purpose of a Beta is to get a mostly completed application in
front of a select representative group of users for feedback on
usability and design. Functionality should have been identified
during delta's and alpha's at the least.

As such, the length of the beta depends on how complete and "close
to the mark" your application is. If customers find it just what
they were after, then obviously its going to be a short beta.
However, if they find it cumbersome then you are going to need
iterative releases addressing their concerns.

On average, a beta should be 3-6 months. Any more than that and you
will quickly find your development budget vaporizing before your
eyes.

If you are one of the lucky ones who got it right the first time,
then you can always end the beta early. It all depends on your
confidence and budget really.


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=41769


________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help

Reply via email to