1 / 17

The Desire2Learn (D2L) Experience Common Solutions Group Talk

Join Aisha Jackson, Program Manager for Teaching & Learning Applications, as she discusses the D2L experience at CU-Boulder. With approximately 32,000 students and 2,100 faculty, we reflect on the selection criteria, implementation schedule, and the growth of tool usage. Key issues highlighted include the lack of communication surrounding changes, risks during migration to a new file storage system, and the importance of transparency. We explore strategies for evaluating third-party integrations and improving overall communication for future changes.

deacon
Télécharger la présentation

The Desire2Learn (D2L) Experience Common Solutions Group Talk

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. The Desire2Learn (D2L) ExperienceCommon Solutions Group Talk Aisha JacksonProgram Manager – Teaching & Learning Applications Thursday, September 19, 2013

  2. ≈32,000 Students ≈2,100 Faculty

  3. Selection Criteria

  4. Implementation Schedule

  5. Growth in Usage

  6. Tool Usage

  7. And then…

  8. Root Cause D2L Said… CU-Boulder said yes, but… No consideration of risk and potential impact to CU-Boulder Lack of communication about change We weren’t informed of work We weren’t given a choice in scheduling the work • Failure while migrating CU-Boulder to new file storage system

  9. Managing After the Outage • Transparency and communication was key • Accessed the best past forward with D2L

  10. Changing Our Agreement • Consider risk and impact when making changes • Notify us of changes that have the potential of impacting our campus

  11. What’s next? Outage Related Non-Outage Related Framework for evaluating 3rd Party Integrations Making D2L easier to use • Facilitating department level contingency planning • Improving the management of D2L as a vendor

  12. Discussion and Questions… aisha.jackson@colorado.edu

More Related