2012 DevLearn – Breaking the Shackles of Scorm – Tim Martin
Download as PPTX, PDF0 likes7,984 views
The document discusses how the Tin Can API aims to break from SCORM, which has become outdated and presents obstacles that hinder software and organizational development. It presents stories to illustrate issues with SCORM and how the Tin Can API seeks to better support learning experiences by allowing systems to share data about user activities in a standardized way. The Tin Can API has moved beyond an idea and into reality, but its progression relies on users demanding improvements over the status quo.
2012 DevLearn – Breaking the Shackles of Scorm – Tim Martin
- 1. Tin Can API Basics Breaking the Shackles of SCORM Tim Martin Rustici Software tim.martin@tincanapi.com @timpmartin #devlearn209
- 2. Fondly remembered 10 years ago, SCORM was a hero… of a sort
- 3. Aging… The things that made SCORM cute in his 20s became the pot belly of his 40s.
- 4. Our antagonist Look over at the whiteboard…
- 5. Talk to me… SCORM is a hero no longer. It's presenting obstacles that have led our industry's software to stagnate, and our organizations have followed.
- 6. I believe… Helpingindividuals succeed is the most important thing we can do at an organization. And as people.
- 7. Through SCORM’s looking glass Stories
- 8. Back to school Mr. Goforth and Oakley
- 9. My story David, the Software Developer
- 10. We, with a big W. We want to build software that helps people become what they aspire to be. This requires understanding people's experiences across contexts.
- 11. Standards are written to serve the intent of people. We, those of us working on the Tin Can API, want to help people succeed.
- 12. The Tin Can API is a shared language of experience, a way for systems to talk to each other about what people do.
- 13. Through Tin Can’s looking glass Stories
- 14. Back to school Mr. Goforth and Oakley
- 15. My story David, the Software Developer
- 16. Your stories
- 17. This is real The Tin Can API is no longer just an idea.
- 18. The tools will progress only as fast as you ask them to. Do not accept the status quo.
- 19. Tin Can API Basics Breaking the Shackles of SCORM Tim Martin Rustici Software tim.martin@tincanapi.com @timpmartin #devlearn209
Editor's Notes
- #2: Ask people about themselves as they come in
- #3: Associated picture: heroMy commentsContent was reusable across environments/LMSsThe government didn't have to pay for content over and overThe community came together to do something in a consistent fashionRapid authoring tools were able to existBrowser based content was possible (this was progress)We agreed upon a language for expressing a certain set of activitiesStarted, finished, passed, answered a question
- #4: Associated picture: hero with bellyMy commentsOne userOriginated in a Learning Management SystemLaunching a prescribed experienceIn an active browser session(Inconsistently)
- #5: One userOriginated in a Learning Management SystemLaunching a prescribed experienceIn an active browser session(Inconsistently)
- #6: Why did you come? Why are you here?What has SCORM done to you? Take notesAccept my own role hereStagnancyA limited picture of learningAccepting defeat by SCORMAccepting vendors who have accepted these limitations
- #7: This is what I believeAs learning professionals of many typesI believe too many tools are focused on helping companies and groups succeed. Learning is a personal experience. How do we help the individual?
- #9: Mr. Goforth (the social studies teacher) and Oakley (his adventurous student)We'll start with an experience we all share, 6th grade social studies. Each of you was a kid, or a parent, at some point.Paint a picture of MrGoforth (and conquer). His love of teaching (first day annecdote). The fact that he wants to give each kid the best experience possible.Paint a picture of Oakley, the adventurous student. The kid who cares about WWII at home. And read's Anne Frank's diary. Mr. Goforth uses technology, and has found a piece of content about WWII. He delivers that content via the school's LMS and also serves a quiz that way. He knows the following:Which students watch the content and for how longWho did well on the quiz and whether Oakley passedMaybe, just maybe, which questions caused problems for his students.
- #10: David is a 26 year old software developer with limited experience at a religious software platformTalk about the degree to which we've used SCORM based training at Rustici SoftwareConsider how we might use it: new hire training, policy acknowledgementMy ability to help David succeed is not substantially enhanced by SCORM
- #11: This is the big W, the contributors to the specificationA brief comment about isolated pictures of experienceMy bike accident as an indicator of my biking ability, or my driving ability
- #12: * This is big W again
- #13: What Tin Can isA web serviceA series of sentencesNoun – verb - object
- #15: Reminder: Social studies teacher and interested studentKindle notes from Oakley reading Anne FrankWWII app interactions from OakleySmartboard exercise where all student get credit for attending a lectureAttendance in lectures (by topic) noted by attendance systemOakley's searches indicate her unsatisfied interestTicket to Ride Europe (a European map game) indicating understanding of geography from each student
- #16: Reminder: David, Self-guided software developerExperiences at prior employer – watershedWhat does David read outside of work? Could this tell me, his employer, about the things he'd like to be working on? Could this help me to help David be what he wants to be?What if Github made statements? Would we be able to see prospective managers from their patterns of peer review?Could we see the statements issued by our Pong app and learn about patterns that would help David be more effective?
- #18: Real implementations invite to Tin Can AlleyReal, continued progress
- #19: Consider a demo at this stage if timewatershed.ws