|
Product:
Beta Cycle Manual
Written in clear text, this
step-by-step manual describes details for the following topics: Organization, Methodology, Activities,
Participants, Beta Team Coordination, Project Tracking, Control
and Communication.
Also provides Comprehensive
Chart of Eight Phases and milestones includes: Project Planning, Investigation, Development
of Relationships, Product, Beta Testers, Feedback Collection,
Testimonials, Closure
View Sample
below:
ßeta Manager:
Establish
goals, roles and responsibilities |
|
Milestones |
|
An Account on the Corrective
Actions Database.
Team Leaders in the Daily Escalation
Meeting know their roles and their collective goals are established.
External sites are approved
and are installation ready. |
|
Engineering |
Written definition of Severity
for example:
- Software broken, no workaround.
- Feature is broken, no workaround.
- Feature is broken, painful
workaround.
- Feature is broken, easy workaround.
- Minor feature problems.
- Cosmetic, Alignment or defect
in gui.
- Cosmetic, Trivial or preferences.
Written Classification for
example:
Software problems categorized
into 6 levels of severity (see definitions of severity) in the
scope of the beta release.
- Issues outside the scope of
the beta release.
- Features working as designed.
- Configuration / environment
- requiring additional instruction, training and / or documentation.
|
|
|
Completes first draft of documentation
and readies beta. |
|
Technical &
Customer Support |
Understands the role they take
during the beta including attendance at the Daily Escalation
Meeting.
Works through the Test Plan
or Matrix. |
|
ßeta Manager |
Sets up a Communication Portal. |
|
