beta_nomination
<![CDATA[
===================================================================
CALL FOR BETA CALL FOR BETA CALL FOR BETA CALL FOR BETA
===================================================================
]]>
XYZ today is announcing the call for beta sites for a major new XYZ solution,
known as XYZ.
PRODUCT DESCRIPTION
TARGET MARKET FOR BETA
IMPORTANT DATES
<![CDATA[
Deadline for submitting beta nominations ddmmmyy
Start of beta nominations ddmmmyy
Start of beta training ddmmmyy
Start beta ddmmmyy
Complete beta ddmmmyy
]]>
PRODUCT FEATURES AND BENEFITS
WHAT TO DO NEXT
Supporting a beta for a product of this magnitude are substantial. Please
walk through the following steps before submitting the name of a prospective
user to:
<![CDATA[
1. Review the attachments
SELECTING BETA SITES
PROGRAM AND PRODUCT OVERVIEW
2. Contact potential users meeting the selection criteria.
3. Describe the product to the candidate.
4. Involve district/region/country personnel.
5. Discuss customer goals and obligations.
6. Fill out and submit to by ddmmmyy the attached
BETA SITE NOMINATION FORM
]]>
Personnel in the following groups are available to help during this process:
Refer to SELECTING BETA SITES for members of these groups who have been
trained in the XYZ product.
SELECTING BETA SITES
This document contains information that will enable you to select appropriate
candidates to beta test the XYZ product:
<![CDATA[
- Beta Objectives
- Beta Selection Criteria
- Getting Help
- Environmental Requirements
- Recommended Beta Test Scenarios
- Beta Calendar
- Beta Training
]]>
Beta Objectives
---------------
The purpose of this beta test is to evaluate the complete product, XYZ,
including role in the marketplace, distribution to customers, installation,
functionality, performance and supportability. This evaluation will be
undertaken at a minimum of 6 and a maximum of 10 beta sites. It is an
objective of the beta testing to obtain substantial feedback from users in
order to ensure the soundness of the product for general availability and
to prioritize important product amendments or enhancements.
Beta Selection Criteria
-----------------------
Site selection will be focused primarily on the following HIGH PRIORITY
selection criteria:
<![CDATA[
1. Upon successful completion of beta, will the user be willing to be a
reference and/or included in a published application brief?
2. Has the user a demonstrated commitment to improved XYZ functionality by
applying the necessary resources (e.g. products, staff, organization)?
3. Has the user committed appropriate personnel and the minimum number of
hours of beta testing, as defined in the BETA PLAN, Section 5.2?
4. Is the user planning to acquire XYZ product in order to do, at a minimum,
one of the following:
5. In addition to a beta analyst, will a trained field analyst be available
for consulting throughout the beta planning and testing period?
]]>
THE BETA NOMINATION FORM MUST REFER TO THESE HIGH PRIORITY SELECTION CRITERIA.
In addition to meeting the above requirements, a prospective beta candidate
will increase the likelihood of being selected by meeting as many of the
following optional requirements as possible:
Getting Help
------------
One of the XYZ trained personnel roles is to assist account teams with both
the selection and beta test process. The following have sufficient product
knowledge and presentation materials that they could assist in giving product
overviews to prospective beta candidates.
Environmental Requirements
--------------------------
Required:
Recommended Beta Test Scenarios
-------------------------------
A beta candidate must submit a beta test plan before beta testing can begin.
The scope of the plan should include plans for three types of testing:
<![CDATA[
Product Installation
Component Testing
End-to-end Functional Testing
]]>
Although a completed beta test plan will not be required prior to acceptance
as a beta site, customer intentions for each type of testing will be used to
select beta sites. Please review the XYZ BETA PLAN, Test Scenario Guidelines,
to ensure prospective beta candidates understand the type of testing we are
striving for.
Beta Calendar (yyyy)--------------------
<![CDATA[
Call for beta sent to Divisions ddmmm
Close of beta nominations ddmmm
Beta site selection ddmmm
Beta training start ddmmm
Beta test plans complete ddmmm
Start of Beta ddmmm
Beta refresh ddmmm
End of Beta ddmmm
]]>
Beta Training
-------------
Initial Beta training has been scheduled to occur on mmmddyy. Beta training
is intended for all customers or users and the beta analyst. As with all beta
classes, travel expenses are the responsibility of the participating field
office. The beta class will be x days in duration. If attendance at the beta
class is too great a number to manage, a second class will be offered at a
time and geographical location to be announced after beta selection is
complete.
Call to Beta ADDENDUM
PRODUCT AND PROGRAM OVERVIEW
This document includes a discussion of the goals of the XYZ program, a high
level description of the functions delivered through theXYZ products, and
product positioning statements. This information is essential for customers
to be able to understand the role that XYZ products will play in their
operations management planning. Sections included are:
<![CDATA[
- Program Goal
- XYZ Products
- Relationship to Existing xxx Products
- Relationship to the XYZ Architecture
]]>
Account teams must thoroughly review and understand this material before
introducing the product to the customer for beta consideration.
Program Goal
------------
Today's XYZ Products
--------------------
BETA SITE NOMINATION FORM
<![CDATA[
1. Customer Name:________________________ System #:__________
Customer Address:_________________________________________
_________________________________________
Customer Industry/Application:____________________________
2. Supporting XYZ Office - City:_____________
3. Sales Rep: _____________________ Emp#_______
Contacts:
S.A. _______________________ Emp#_______
C.E. _______________________ Emp#_______
4. Provide information on the Company/Customer relationship.
A. Is this a key account? ___________(y/n)
B. Account Size? ___________
C. Has the customer participated in other Betas? (y/n)
D. If the customer has participated in other Betas, please list the
products and the customer attitude at conclusion of beta.
________________________________________________________________
________________________________________________________________
________________________________________________________________
E. Does this customer require special attention?
________________________________________________________________
________________________________________________________________
G. Is this product critical to the customer's environment?
________________________________________________________________
________________________________________________________________
5. Provide the following information on the customer's business environment
for which the BETA Test is requested.
A. Reason's for participating in beta
________________________________________________________________
________________________________________________________________
B. Describe the Customer's goals in participating in the beta?
Product functionality _________________________________________
Product installability and quality ____________________________
Personnel productivity ________________________________________
Solving a business requirement ________________________________
C. Assess the risk of:
Discontinuing the beta
____________________________________________________________
Slipping the beta start date
____________________________________________________________
Extending the length of Beta test
____________________________________________________________
D. Describe the system configuration:
network(s) _______________________
Terminals _______________________
Memory _______________________
CPUs _______________________
Disk _______________________
E. What release of the operating system will the BETA site use?
F. Describe if applicable, the XYZ environment:
How long has it been installed? ___________________
Is it in production? _____ How Long? ___________
What release is installed?
(include date stamp) _________________________
What is the customer's ability to support XYZ?
(Use scale of 0 - 10, with 10 being max.) ____
G. Describe if applicable, the XYZ environment:
H. Does the account have a test system? --if so,
How much "production" is done on it?
How much pain will it cause the customer if their test system
crashes?
(we don't expect crashes, but this is a BETA Test)?
____________________________________________________
____________________________________________________
____________________________________________________
I. What is the customer's scheduled production date for XYZ?
_______________
J. Which of the following environments will be managed via XYZ?
____ Systems
____ Networks
____ Other ___________________
6. Account Support:
A. What is the local support commitment allocated for this BETA?
(for example, 1/2 analyst)
__________________________________________________________
B. Who is the analyst(s) that will support the BETA Test?
__________________________________________________________
C. Describe the current level of XYZ training and experience of the BETA
support analyst(s):
__________________________________________________________
__________________________________________________________
7. Customer Technical Skills:
A. What personnel resources is the customer commiting to this Beta?
(for example, 1 full-time analyst)
______________________________________________________
B. Describe the current level of XYZ training and experience of the
of the customer's technical personnel assigned to the project:
__________________________________________________________
__________________________________________________________
C. Describe, if applicable, the additional training plans for the
customer's analyst:
__________________________________________________________
__________________________________________________________
]]>