Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Construct an outline of the product itself, including information regarding it’s current state (alpha, beta, beta2, etc), high-level modules, etc.
  • Beta Target Market Definition –Detail the types of individuals this product will be used 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 - testing for user experience with initial set of tools
    • Interface acceptance - API works in desired browser
    • Product functionality in real-world environments
    • Test support infrastructure - this will be after release
    • Collect customer suggestions and testimonials - testimonials is essential for expanding user acceptance and for use in newsletters 
    • Include the areas (modules) of the product that will be tested
  • Incentives–Plan out the incentives that will be rewarded for participation, as well as the participation levels which they will be based on.
    • Will we offer incentives?
  • Project Team Responsibilities
    • Define the responsibilities of everyone involved in the project
    • Define how feedback will be managed as it changes hands and progresses

...