We take two looks at which versions of SCORM are being used.
The first charts the usage of each SCORM version over time. This chart reflects the percentage of courses that were imported into SCORM Cloud during a given month that use each version.
The second chart looks at the people who are using each standard. Each slice of this pie reflects the number of SCORM Cloud users who have uploaded a package that uses that SCORM version.
Are we realizing the "-ilities" of SCORM? Much of the SCORM model is predicated on a vision of multiple-SCO courses that allow for reuse, mixing and matching. In the real world though, many people just want their content to work and deploy simple, single-SCO courses.
These charts show how many courses are more advanced than a simple, single-SCO as well has how many SCOs are typically used in multi-SCO courses.
SCORM 2004's sequencing specification provides powerful capabilities when deploying multiple-SCO courses, but many say it is overly complicated, unreliable and not worth the effort (and thus not used). This chart shows the percentage of content that is actually making use of sequencing.
Adoption of a standard is important. SCORM Cloud is an important community tool for those involved with the testing and development of SCORM content. Its usage is illustrative of the overall adoption of SCORM.