The Beta Plan:

• Ensures the project parameters, goals, milestones, activities, and participant demographics are well defined
• Outlines all internal resources (project members and teams) involved, as well as their responsibilities
• Is the basis of the report which will summarize the results and effectiveness of the beta project (more later)

Plan Definition:

• Construct an outline of the product itself, including information regarding it’s current state (alpha, beta, beta2, etc), high-level modules, etc.
  • Beta Release
• Beta Target Market Definition –Detail the types of individuals this product will be sold to. This could include consumers, business IT departments, soccer moms, previous customers, and everything in between. Most products span multiple markets. Break down the types of users you plan to recruit into pools. Include the tester requirements (time, hardware, etc) in this definitionused by.
  • PEcAn
  • CZO communities
  • DataONE
    
    • value for the ecological community - specifically allowing for data to be downloaded in a variety of different forms directly from DataONE
  • Research Data Services,
    
    • beginning with our own University of Illinois RDS
• Test Parameters –Outline the basic parameters unique to the project including number of beta testers and projected timeline.
  • Include the tester requirements (time, hardware, etc) in this definition
    • Windows or Mac what about Linux?
    • looking at a ... 2 hour window?
    • What is space requirement
    • What is RAM/Processor requirement
• Test Goals (SUPER KEY)–List the unique goals of the project.
  
  • Items such as general quality improvement
  , interface acceptance, product
  • - testing for user experience with initial set of tools
  • Interface acceptance - API works in desired browser
  • Product functionality in real-world environments
  , test
  • Test support infrastructure
  , collect
  • - this will be after release
  • Collect customer suggestions and
  testimonials.
  • testimonials - testimonials is essential for expanding user acceptance and for use in newsletters 
  • Include the areas (modules) of the product that will be tested
  .
  • • Planning Testing
• Incentives–Plan out the incentives that’ll that will be rewarded for participation, as well as the participation levels which they will be based on. (more later)
  • Will we offer incentives?
• Project Team Responsibilities –Define
  
  • Define the responsibilities of everyone involved in the project
  .
  • Define how feedback will be managed as it changes hands and progresses
  .

Initial Activities –

Plan out the initial activities which will be performed throughout this beta (activities will likely change in response to the project progression) 

Recruiting Testers

• BD Team
• ISDA Team
• Any SSA Team Members?
• Students
• Current Collaborator / Students

Tester Management

Clearly Express Expectations Early on and Throughout

• Consistently Encourage Do we have anything that will need Confidentiality (NDA, etc)?
• Balance Gratitude with Expectations - Thank you for testing but make sure to meet deadlines for reporting
• Keep Sites Exec Committee Involved with On-going Activities
• Keep Sites Exec Committee Current Regarding Project Progress
• Offer a Simple Consistent Method for Testers to Provide Feedback in the Forms you Wantwe want
  • Testing Matrix - need to offer paper copy as well as online - how can online version be copied multiple times
  • Shared Google Doc for bugs?
  • One person enter bugs in JIRA
  • We could use Google Spreadsheet or what about Google Survey? https://support.google.com/docs/answer/87809?hl=en
• Allow Testers to Communicate Amongst Themselves (increases participation, secure outlet for excitement)
• Respond Quickly to all Issues and Requests
• Contact Inactive Testers Directly (by phone if possible)

...