Another Tuesday, another acronym! Today we’re going to be talking about SCORM!<\/p>\n
SCORM stands for Sharable Content Object Reference Model and more or less dictates how e-learning content must be programmed in order to work with other e-learning software, such as Learning Content Management Systems (LCMS’) or Learning Management Systems (LMS’). The SCORM website provides a nice explanation of how SCORM let’s code and software play well with one another, so to speak.<\/p>\n
As the name alludes to, SCORM creates ‘sharable’ content, which is essential when it comes to saving a business’ hard earned profits. Why? Well – before the days of SCORM, organizations may have contracted out training requirements to many different providers who all used their LMS of choice – creating a high volume of duplication, and likely less consistency. Now that SCORM exists, organizations can re-use training programs more easily than in the past.<\/p>\n
Why is SCORM a sought after client requirement? Well. When clients dictate they want SCORM conformant or compliant e-learning product, they’re doing this to ensure that the developed e-learning product will function within any LMS they wish to launch the product within. Adhering to the SCORM standard will greatly help ensure your e-learning products are well-equipped for interoperability.<\/p>\n
Right now, Tin Can API is foraging ahead to become the next generation of SCORM (let’s face it; SCORM is an old-timer; don’t get me wrong – a tried and true old-timer, but everyone needs to evolve), and will become the new standard within coming years – more on Tin Can API in another post.<\/p>\n
Still curious about SCORM? There’s a lot to it, and I’ve definitely only skimmed the top of \u00a0explaining it, but\u00a0Learningpool provides a great infographic<\/a> that should explain anything I’ve left out!<\/p>\n <\/p>\n