SCORM 2.0 Requirements Workshop

LETSI hosted a SCORM 2.0 Requirements Gathering Workshop last week at IHMC in Pensacola, FL. I was absolutely amazed at the turnout, energy, enthusiasm and raw intellectual horsepower that is focused on SCORM 2.0. Somehow we managed to organize and harness the talent of about 70 people, each of whom brought something unique to the table. There’s a long way to go on the path to the next generation of learning standards, but everybody agrees that we traveled farther down that path than anybody expected in 2.5 days.

There were four primary tracks at the workshop and each track was responsible for a different subject area.

  1. LET 2.0 Use Cases and Requirements
  2. Content / Sequencing
  3. Architecture / Web Services Interfaces
  4. Market Realities and Business Drivers

Each track produced a deliverable talking about the “why” the LET world needs solutions in their area and “what” those solutions need to accomplish. I co-facilitated the Content/Sequencing track in which we concluded (among other things) that the problem of sequencing is actually much broader than the current specification addresses and that context is vitally important to any sequencing decision.

In my opinion, LETSI struck gold with the LET 2.0 track. They produced 30 use cases that describe what learning does/can/should look like. This simple exercise is going to be invaluable to the process of shaping and validating the solutions of SCORM 2.0. It is very likely that LETSI will be putting forth a “Call For Use Cases” soon to request even more requirements from the community. Personally, I would like to see hundreds of use cases submitted. The evolution of SCORM has been driven by vendors and techies for too long. We can’t make the same mistake again; the input of ISDs, teachers, instructors, trainers, etc is vitally important to ensuring that SCORM 2.0 is a success.

One of the most thought provoking ideas was put forth by Aaron Silvers. During a discussion pertaining to the structure of SCORM 2.0 and the business model for LETSI. Aaron suggested that we become the “LINUX for learning”. SCORM 2.0 is shaping up to be a bit more than just a technical standard. Aaron’s succinct elevator pitch has engaged the critical thinking part of my brain more than anything else from last week.

Creating standards in a completely open process is quite an experience and I’m told we’re actually breaking some new ground. The question that weighed heavily on my mind when we were putting this workshop together was “How do you make strategic decisions in a completely open process?”. The specific strategic decision I was pondering was what LETSI should work on first. The white papers put forth suggestions on every conceivable topic, and while LETSI has a lot of momentum, we can’t boil the ocean. On the program committee, we had to make some tough choices as to what was in the program and what was out. But, we’re not the final arbitrators, the community is…so, how do we move forward and balance efficient decision making, prioritized requirements and open process? Let us know if you have any good ideas.


  • Aaron

    Well, you certainly know how to make a girl blush 😉

    To move forward and balance the decision making, prioritizing of requirements and still maintain an open process is going to be as much “hunch” as it is study. As a group, we need to reach out to groups and individuals who’ve been successful moving both standards and software forward in open or common source spaces. Martin Dougiamas of Moodle is an obvious person we should talk to; but there are no shortage of successes in the open software/platform field. We should also reach out to people on the CSS and ECMAScript groups that were unsuccessful so we understand what NOT to do.

    As soon as we can map out an architectural “philosophy” (for lack of a better word), I think we’d be wise to reach out to communities that we’ll identify as LETSI-critical but SCORM-peripheral. These would be players and evangelists in the Business Application space (SAP, Oracle, PeopleSoft) and the Talent Management Space, particularly. We’re already talking about how to mash up our services with those kinds of applications/services. It’d be pretty genius of us to research how to do it in a way that they’d want to participate in which further supports interoperability.

    One last thing — since we’re already floating around the idea of Services Oriented Architecture, we should look at what existing SOAs can actually do. Google’s python-based AppEngine; Facebook’s application templates — there’s probably a half-dozen we can use to assert theory and make sure that what we’re putting forth is more than a specification — it’s a practice with models of what “good” looks like.

    Lastly, hard as it may be for some/all of us, we’re going to make some mistakes and being transparent is going to be difficult — it’s a new way of operating and seems counter-intuitive to everyone’s business interests. Not being a seasoned entrepreneur, I don’t have a lot of leg to stand on, but I believe there is an explosive amount of opportunity for everyone involved if we continue to think about being open, honest, transparent and assume positive intentions from all our partners.

    I’ve been nothing short of amazed and impressed at the candor and judgment with everyone involved with LETSI so far. I came with doubts. I’ve left Pensacola as an evangelist.