Product Version Migration

When TestOut updates their products, we know it can impact your program and classes. To reduce the impact, we want to work with you, review your program, review the product changes, and decide the best time to implement the product update. We keep the process simple, yet organized. In general, we use the following framework of phases:

Decision Phase

We review your program goals, such as Course Completion, Learning/Mastery Assessment, Certification Pass Rate, and more.
We review product changes, including:
 
  • New or Updated exam content for the updated 3rd party exam (CompTIA, Microsoft, Cisco, etc.)

  • Course reorganization to fit best learning/design practices

  • Enhanced/improved programming in the simulated labs, etc.


We develop a time frame that fits the needs of the program, including your:
 
  • Course redevelopment/refresh cycles

  • Term/semester start dates

  • Available Resources (teams and employees)


 
The time frame should have clear beginning and milestone dates, with ongoing “Maintenance” dates.

Prepare Phase

 
NO. 1
Organize
We organize the product migration team (aka team) to include members from the school AND TestOut Team members, such as:
 
  • School’s Program Dean (Executive Sponsor)

  • School’s Program Manager or Project Manager

  • School’s Lead Instructor(s) and/or Subject Matter Expert

  • School’s LMS Technician (if LMS Integration is present)

  • TestOut’s Account Manager

  • TestOut’s Lead Instructional Designer over product

  • TestOut’s Lead LMS Technical Lead

NO. 2
Gather
The team will gather the following documents assist the team to understand the impact of the changes in the new version of the TestOut Product:
 
  • School’s Program Dean (Executive Sponsor)

  • School’s Program Manager or Project Manager

  • School’s Lead Instructor(s) and/or Subject Matter Expert

  • School’s LMS Technician (if LMS Integration is present)

  • TestOut’s Account Manager

  • TestOut’s Lead Instructional Designer over product

  • TestOut’s Lead LMS Technical Lead

NO. 3
Document
The team will document changes in draft form, including any changes to the following:
 
  • School’s Program Dean (Executive Sponsor)

  • School’s Program Manager or Project Manager

  • School’s Lead Instructor(s) and/or Subject Matter Expert

  • School’s LMS Technician (if LMS Integration is present)

  • TestOut’s Account Manager

  • TestOut’s Lead Instructional Designer over product

  • TestOut’s Lead LMS Technical Lead



 
The team reviews, approves, rejects and/or modifies the proposed changes. Depending on the severity of the changes, the timeframe for execution may need to be modified to fit the goals of the school and the program.

Execution Phase

The team will debrief Instructors and/or facilitators on the approved changes to the course section, when the implementation will begin and complete, and the coaching to help them be successful.

Implementing changes is a coordinated effort, within the team. However, it is likely the school’s personnel resources will lead in making all changes, facilitated by TestOut’s personnel.
As a matter of best practice, implement changes in the following order:
 
  • Implement all changes in a staging environment

  • Test changes to activities, assessments, etc.

  • Push or roll-out changes from staging environment to live environment


 
The time frame should have clear beginning and milestone dates, with ongoing “Maintenance” dates.