BETA TESTING

1
BETA TESTING
2

• Goal
• To engage key individuals from participating
  staffs in Beta testing a series of online
  professional development modules developed by th
  e-Learning Design Lab.

3
Beta Test Process

• OSEP support
• Nine states
• One team per state
• SEA
• IHE
• Teacher(2)
• Principal
• Staff development
• Training session
• Each member tests a module
• Phone support
• Online reporting via survey form on web site
• Focus feedback session

4
Staff Development Topics

• Standard Based IEPs
• Author Barbara Bateman, University of Oregon,
  Eugene.
• Best Accommodations
• Author Peggy King-Sears, John Hopkins University
• Models for Collaboration
• Author Jeanne Bauwens, Boise State University
• Effective Transition
• Author Mary Morningstar, University of Kansas
• Relating Assessment to Instruction
• Author Judy Elliot, Long Beach Unified School
  District, California

5
Steppingstones Module Topics

• National Curriculum Standards in Math,
• Reading and Science
• Purpose, Understanding and Application
• Curriculum Standards History, Policy and
  Implications for Classroom Teachers
• Applications of Curriculum Standards

6
Staff Development Module Development Process

• Needs assessment based
• National Board input
• Consultant input
• Specifications for content
• Content developed by content expert
• Teacher participant
• eDL content management
• eDL production

7
TRAINING

• Standards Based IEP

8
Beta Testing Procedures

• The SEA representative will be the key contact
  person in each state.
• Cheryl Harrod will be the key contact person at
  the e-Learning Design Lab on procedures and
  issues. She will coordinate additions to the
  website with Bob Issacson.
• Karl Murray will be the key support person in
  contact with team members during the beta
  testing.
• Each team member will select a module for beta
  testing. The preference is that they select a
  module of interest to them personally and that
  they do not all select the same module.
• A computer generated unique user code will be
  provided each team member. The responses will be
  anonymous. The generator will allow for
  determining if holders of numbers have not
  responded but will not be able to identify them.
  If a number is lost contact Cheryl Harrod.

9
Contd of Beta Testing Procedures

• The user code will be the password to enter the
  modules on the website.
• To access the module of your choice for beta
  testing you will go to the website at
  www.elearndesign.org/betatest/ and select module.
  Click on the module of your choice and a window
  will pop up with a line for entering your User
  Code. Enter your User Code and follow the
  directions on the page.
• Each time you return to work on the module you
  will go through the procedure in Step 7.
• When you have completed the module and are ready
  to complete the Survey Form return to the Website
  at www.elearndesign.org/betatest/ and click
  Survey Form. A window will appear asking you to
  enter your User Code. Follow the instructions for
  completing the Survey Form.
• Once you click submit after completing the
  Survey Form the results are automatically
  recorded and tallied at server site.

10
Contd of Beta Testing Procedures

• Once you click submit after completing the Staff
  Development Beta Test Survey form, the results
  are automatically recorded and tallied at the
  server site.
• Karl Murray will call each team personally to
  determine if they have questions or comments they
  would like to share as they progress through
  their module.
• Following completion of the Beta test, a series
  of four sessions in the form of conference calls
  will be held. A sample of participants will be
  selected for their session.

11

• NOTE
• You are free to beta test more than one modules
  or to review additional modules without
  completing a Survey Form. You also are allowed to
  review any of the original 22 Academy modules. To
  review any the of the original 22 Academy modules
  you follow the following directions

12
PRACTICE