If you don’t know what SCORM is, you are probably lucky, and unless you have a good reason to dig into it, I suggest you read below and never think of it again.
I remember the first time I heard about SCORM (Sharable Content Object Reference Model) - it was 2004 and we wanted to follow a standard when creating our new content authoring tool. I remember feeling excited by the concept of a standard to share content between Learning Management Systems (LMS) - it made a lot of sense that we ensured our new course content followed this standard.
I printed the hundreds of pages that made up the SCORM 2004 standard and spent the weekend trying to stay awake as I read it….
The thing we quickly realised is that to be fully SCORM compliant, we’d have to implement a lot more database calls than we needed, it would make our software bloated and hard to maintain. So we built only the parts we needed at the time, and expanded and modified it over the years as needed - we liked to say we are SCORM compatible, rather than compliant.
Over the years, we built SCORM players inside our LMS (called ILS), a SCORM compliant content controller for Moodle and utilised SCORM as a standard way to export content from our native content authoring system.
All of these developments worked fine, but when we started on our latest LMS (simply called Intuto), we actively decided not to mention or use SCORM. This is because it isn’t fun or easy for end users. The acronym itself shows that - try saying SCORM to a manager who just wants their staff trained and watch their eyes glaze over, or maybe look at you skeptically wondering if you are making things up to confuse them. Worst of all, authors can’t change content on the fly if it’s a SCORM package loaded into the LMS.
That said, over time we have realised there are some good reasons why we should support SCORM:
Aged care continues to face a massive shortage of staff. According to a recent union...
Keep up to date with Intuto's blogs.