I am looking for criteria for entering alpha, beta and FCS
in terms of processes passed as well as quality achieved.
Re: I am looking for criteria for entering alpha, beta and FCS
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Levana Fouks:
in terms of processes passed as well as quality achieved.<HR></BLOCKQUOTE>
A tall order considering we really do not know much (actually, anything) about your setup or what has been done. Also, many places have different terms for what they mean by things like "alpha" and "beta." In most places "alpha" means a pre-release with missing functionality to greater and lesser degrees to a minimal subset of their client base. A "beta" usually means a pre-release of most of the core and ancillary functionality present to a wider subset of their client base.
In that case, your entrance criteria for both phases would, at the very least, have the required minimum functionality that was determined for those releases. Entrance criteria would also suggest that a certain level of defects have been removed. For example, you might have an entrance criteria that for your areas of critical functionality, all Severity 1 (or Priority 1) defects have been fixed. Another entrance criteria would be that you have tested the application on all the platforms that it is going to be released to in the alpha and beta stages. In both stages you should make sure that any documentation being sent to the users has been verified for accuracy and completeness. This is definitely one aspect of the entrance criteria.
As far as FCS, keep in mind that your beta releases really should be your FCS release candidates anyway. The last stage of FCS regarding entrance criteria is final sign-off from the relevant teams (QA, project management, etc.) giving the okay to ship the product.
Something you might want to check out that highlights all of this much better than I did: