1 / 14

Picking a Better Learning Management System (LMS)

Picking a Better Learning Management System (LMS). Why Choose an New LMS?. Out growing WebCT Campus Edition (CE) # of students approaching WebCT CE technical limitations System stability Database Architecture Data Integrity Data Security Faculty and Student Issues Related to Ease of Use

kylee-patterson
Download Presentation

Picking a Better Learning Management System (LMS)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Picking a Better Learning Management System (LMS)

  2. Why Choose an New LMS? • Out growing WebCT Campus Edition (CE) • # of students approaching WebCT CE technical limitations • System stability • Database Architecture • Data Integrity • Data Security • Faculty and Student Issues Related to Ease of Use • Growing need & opportunities for “Branding” SPC and non-SPC programs

  3. Start Up • Timeframe – 1 month • Decision to move forward with feasible study • Formed LMS Evaluation Committee with three subgroups: feature set, architecture, and total cost of ownership • Web Site Developed to inform SPC staff and faculty http://it.spcollege.edu/lms/

  4. Lessons Learned – Start Up • Pick participants for the committee that do not have a bias to one LMS • Communication, communication, communication!! • This will be a long process

  5. Due Diligence – Phase I • Timeframe – 6 -7 months • Staff review and analysis of all systems • Site visits by 4 of the vendors • LMS Olympics – Side by side comparative evaluation of the 4 vendors (LMS Doc) • Evaluation tool created to narrow to 2 finalists (Rubric for Evaluation Doc) • Site visits by the two finalists • Feature set group recommends ANGEL

  6. Lessons Learned – Phase I • Do an RFP • Make contact early with each vendor and develop a good working relationship with the sales reps. • Get names and a contact person from each institution using the LMS being evaluated from the vendors. • Communication, communication, communication!!

  7. Due Diligence – Phase II • Timeframe – 3 – 4 months • Detailed TCO (Total Cost of Ownership) is developed • Architecture group obtained evaluation license of both finalists • On site installation and evaluation 0f WebCT Vista v2.0 & ANGEL v6.0 • Architecture group recommends ANGEL

  8. Lessons Learned – Phase II • Consider all possible costs (TCO): • Licensing • Hardware • Vendor Services • HR • Cost of not purchasing a new LMS • Make sure to have Information System people involved in the evaluation from the beginning • Determine the profitability of the company • Communication, communication, communication!!

  9. Due Diligence – Phase III • Timeframe – 1 month • Last review of latest releases – ANGEL 6.1 and WebCT Vista 3.0 • Re-confirm LMS Committee groups selection & conclusions

  10. Lessons Learned – Phase III • Because the process can be long, new releases of your choices may become available. • Communication, communication, communication!!

  11. Final Recommendation & Approval • Timeframe – 2 -3 months • TOG Review & Concurrence • President Briefing, Feedback, Direction • Cabinet Review & Approval • Board Review & Approval • Informed Competing Vendors

  12. Conclusions • Take your time. SPC spent almost 13 months making a decision • Involve many faculty and other special groups in the evaluation committee • Involve senior management, CIO, V.P. of Student and Educational Services • Make sure some of the people on the evaluation committee do not have bias on one system or another

  13. Conclusions • Make sure you have a total consensus on a choice. Do not use majority voting • Do not make migration from one system to another as highly weighted as the feature set

  14. Questions and Answer Time

More Related