ELIS – Managing Enterprise Level Learning Programs with Moodle
25
ELIS – Managing Enterprise Level Learning Programs with Moodle - Mike Churchward
description
Mike Churchward
Transcript of ELIS – Managing Enterprise Level Learning Programs with Moodle
ELIS – Managing Enterprise Level Learning Programs with Moodle -
Mike Churchward
Introduction
Remote Learner is a Moodle service provider Our focus is on simplifying the administration
and maintenance of learning programs in Moodle
Our clients are large, enterprise-level organizations that manage thousands of users and hundreds of courses
Mike Churchward
From Rod:Rd - comment: we focus on the current group of customers and prospects. Yes, we need a MUCH better filter in which we can say yes/no to and early in the process. We just had another SOW rejected because we allegedly missed what they wanted to accomplish and it took way too long to it to them.I wish we had a 100K prospects. I am sure Mike put this in as a large number. There are 66K registered sites of moodle world wide, 11K of those in the us. Bb has 12K customers To reach $50M ($40M more than today) we would have to sell 2700 more Level 3 Enterprise customers. That’s 45 new Level 3 Enterprise accounts per month for 5 years. At 10,000 users each that’s 27,000,000 users.We need bigger accounts. We need multiple $100K+ accounts. It is very doubtful that we can find this much opportunity with moodle being free and RL selling support, hosting, and professional services for a very standard, one size fits all customers.We need 400 new accounts at $100K each to add $40M.Here are our current top customers in terms of volume:PrepWorks: $636Google: $180AEA/UEN: $175Kaltura: $127CyFair: $100MCNC: $90Royal Caribbean: $86 SBCC: $82NESA: $80UNCC: $79IEEE: $69STEM: $65Massachusetts ex ofc pub safety: $64Garland: $63Midwest community college: $56TSTC: $55And there seem to be a few of these we do not want.
Mike Churchward
From BW:If we can sell a standardized, flexible platform to 100,000 clients, why do we bother with the 10 that want something else? (absolutely)We seem to focus on customizations, because they are being requested. (nature of the OSS beast, but changing)
The Needs
Our clients wanted to be able to automate large manual processes in Moodle
Our support requests frequently involved our techs helping to carry out large manual tasks
Wanted to be able to manage courses and users in groupings not provided by Moodle
Mike Churchward
Rod comment:RL goals:1. Profitably growing organization, growing faster than the elarning market place for the products/services we offer. Excellence in what we do. ($50M is a stated goal although there has been no analysis that I know of to determine how large large the market place is and what $50M would mean in terms of market penetration)2. Satisfied customers3. Satisfied employees – able to attract the talent needed to grow and satisfy customersThe goals listed in the previous slide are more how’s to achive the goals rather than the goals.
Mike Churchward
BW Comment:Provide a maintainable service-product platform attractive to financial investment. (+1)Provide our customers with the most robust, flexible, feature-rich and maintainable learning platform possible. (+1)Respond in a convincing way to Blackboard's acquisition of key Moodle partners, and possible increase in Moodle service offerings. (how to respond will be the $64k question)Become a $50M annual revenue company. (in 5 years)
Defining The Needs
Interviewed multiple clients Clients selected on previous requests and
common themes Categorization of support application
requests Gathered all data into a requirements
specification
Mike Churchward
Rod Comment:ok
Mike Churchward
BW Comment:Moodle (and leaning services via ELIS) will be core to our products and services??Other??Belief that OSS platforms should “work together”
Key Requirements
Automate large processes – user creation and management, enrolment, etc.
Automate and track learning progression Communicate to users and stakeholders in
multiple grouping categorizations
Mike Churchward
Rod Comment:Rd comment: these are good and very important from the aspect of improving moodle with our ideas but we need a complete, detailed strategy for finding what large numbers customers/prospects want to accomplish (the job they want done), what they are willing to pay to accomplish this. Additional strategies are very necessary for sales/marketing, support, infrastructure, professional services, training, ID, etc. Each of our functional areas need a set of goals and strategies that in support of the company goals.
Mike Churchward
BW Comment:Become more involved with Moodle HQ (absolutely; at least when it comes to major decisions related to Moodle’s roadmap)Become more involved with other Moodle Partners (We’ve advocated this for years and reached out to many of them)Link our development teams tighter with HQ (I’ll be surprised if HQ is open to this)
The Concepts
Organized into six essential structures: Course Description Class Instance Program Track Learning Objective User Set
All managed outside of Moodle
Mike Churchward
BW Comment:Added:Provide connections with learning content vendors
The Concepts - Programs
The Concepts – Usersets
Course Descriptions Define the meta-data, credits, duration, and
learning objectives for a course of study
Mike Churchward
BW Comment:AddedExamine content provider solutions for partnerships
Class Instances Instances of course descriptions and are
connected to Moodle courses
Class Enrolment Data User's completion, grade, credits and
learning objective status
Learning Program Group of course descriptions to track specific
learning goals (e.g. Certificate program)
Track Instance of a program; a set of class
instances with real data
Learning Objective Define goals achieved by successful activities
in a course
User Sets Hierarchical groupings of users mapping an
organizational structure
The Build - Reasons
A series of Moodle add-ons, using Moodle API's We have Moodle expertise in-house Moodle is central to our learning systems Moodle occasionally “adopts” ELIS functionality Open source provides community involvement
The Build - Problems
Occasionally Moodle changes API's and data structures that don't directly affect users
ELIS development can lag behind Moodle releases
Management of separate application with multiple version releases
Management and Distribution
Processes very similar to Moodle HQ Git-based repositories – internal and
community (mostly) automated merge and release process Unit tests, user tests and Selenium-based
automated testing Agile/Scrum development methodologies and
processes
Follow-up Feedback
Anchor clients Partners Tracker Market research
ELIS Generations – Gen One
Learning programs and reports Manual processes and interfaces External report engine (Jasper) Managed with block plug-in Minimal core changes
ELIS Generations – Gen Two
Identified problems: setup complexity, effort to integrate large enterprise data sets, difficulty configuring report engine
More automation around user sets – profile data based automation
Integration point improvements Better UI integration with Moodle New reporting engine
ELIS Generations – Gen Three
Reduce complexity / more automation Moodle 2 based – local plug-ins Results engine automation More data integration options with plug-in
system Better, configurable reports
ELIS Generations – Future
Adaptive learning features Better links to Moodle outcomes Dashboards with My Moodle More on-demand reporting Better, configurable reports Automated session start and archive More community involvement
ELIS Information
Community site: http://rlcommunity.remote-learner.net/
Repository location:https://github.com/remotelearner
Download:http://moodle.org/mod/data/view.php?d=13&rid=4894
Questions?
