Course Versioning: What is the best practice?

Discussion created by Will Baldwin on Oct 4, 2019
Latest reply on Nov 8, 2019 by Rose Rienton

Like • Show 1 Like1
Comment • 3

Course Versioning: What is the best practice?

Scenario: We have a SCORM course, “Cybersecurity Awareness”. We update the course annually so in our old LMS we would publish a “Cybersecurity Awareness 2017”, “Cybersecurity Awareness 2018”, “Cybersecurity Awareness 2019” and so on. This way on the report we would know what version of the course the learner completed.

Options

Publish one SCORM course, “Cybersecurity Awareness” and annually update the SCORM package and set the SCORM Enrollment Migration Options: “Move enrollments when completed and a new course version exists”
Publish one SCORM course and annually change the title to reflect version changes, “Cybersecurity Awareness 2018.1” and set the SCORM Enrollment Migration Options: “Move enrollments when completed and a new course version exists”
Publish a new SCORM course for every version “Cybersecurity Awareness 2020”, “Cybersecurity Awareness 2021”, “Cybersecurity Awareness 2022”
SOME OTHER SCHEME

Outcomes

Heidi Hess-Bynum

Oct 21, 2019 6:01 AM

Hi Will Baldwin,

We typically follow Option #3. For example, we have a quarterly course that's assigned out though ours is built natively in Bridge. I just duplicate the course, make any necessary edits, and then publish it as 2019 Q3 blah blah. This way a learner could be potentially enrolled in all three quarters of the course.

We use this method for several reasons.

Since the reporting is now separated by course, we can easily see if everyone completed the version of the course they needed to when we run reporting.
It allows us a synchronous enrollment, which is beneficial as some of the learners need to be informed the training is coming out.
It also allows us to maintain the integrity of each version of the course. Since the courses stand alone, we can see exactly what the content was for each release. (The benefit of SCORM is keeping your older course versions.)

We don't enroll new hires in previous versions of the course. I think this is important to note because you could have a learner be enrolled in all 3 versions at the same time. There is a supplementary course they receive that brings them up to speed and then the quarterly release everyone gets at the same time without a rolling enrollment. We use a CSV enrollment when we release it.

I hope this helps,

Heidi

2 people found this helpful

Actions

Rose Rienton

@ Heidi Hess-Bynum on Nov 8, 2019 11:07 AM

@Heidi Hess-Bynum,

I like your suggestion since we also create our courses directly on Bridge. Lately, we started buying SCORM contents and have had a successful demo last week.

Thank you for your continued help!

Actions

Jonathon Batson Oct 24, 2019 4:17 PM

Will,

We use a combination of Opt 2 and 3, with an added a 'change log' to the first page of the course.

For a mandatory policies where any changes need to be agreed to asap for legal purposes it provides the user with a reference to changes in the course.

Acceptable Use Policy v1.1, 2019-03-30

Acceptable Use Policy v1.2, 2019-07-30 . ( includes change log from v1.1)

1 person found this helpful

Actions

3 Replies

Heidi Hess-Bynum Oct 21, 2019 6:01 AM
Hi Will Baldwin,

We typically follow Option #3. For example, we have a quarterly course that's assigned out though ours is built natively in Bridge. I just duplicate the course, make any necessary edits, and then publish it as 2019 Q3 blah blah. This way a learner could be potentially enrolled in all three quarters of the course.

We use this method for several reasons.
- Since the reporting is now separated by course, we can easily see if everyone completed the version of the course they needed to when we run reporting.
- It allows us a synchronous enrollment, which is beneficial as some of the learners need to be informed the training is coming out.
- It also allows us to maintain the integrity of each version of the course. Since the courses stand alone, we can see exactly what the content was for each release. (The benefit of SCORM is keeping your older course versions.)
We don't enroll new hires in previous versions of the course. I think this is important to note because you could have a learner be enrolled in all 3 versions at the same time. There is a supplementary course they receive that brings them up to speed and then the quarterly release everyone gets at the same time without a rolling enrollment. We use a CSV enrollment when we release it.

I hope this helps,

Heidi
2 people found this helpful
Like • Show 1 Like1
Actions
- Rose Rienton @ Heidi Hess-Bynum on Nov 8, 2019 11:07 AM
  @Heidi Hess-Bynum,
  
  I like your suggestion since we also create our courses directly on Bridge. Lately, we started buying SCORM contents and have had a successful demo last week.
  Thank you for your continued help!
  Like • Show 2 Likes2
  Actions
Jonathon Batson Oct 24, 2019 4:17 PM
Will,
We use a combination of Opt 2 and 3, with an added a 'change log' to the first page of the course.
For a mandatory policies where any changes need to be agreed to asap for legal purposes it provides the user with a reference to changes in the course.

Acceptable Use Policy v1.1, 2019-03-30
Acceptable Use Policy v1.2, 2019-07-30 . ( includes change log from v1.1)
1 person found this helpful
Like • Show 0 Likes0
Actions

Course Versioning: What is the best practice?

Course Versioning: What is the best practice?

Options

Outcomes

Related Content

Recommended Content