Moodle At DePauw


Published on

This presentation was orginally presented at the Midwest Moodle Moot at Goshen College on July 21, 2009.

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • We’d like to give you our story of why we switched to Moodle and how we did it, then we’d like to discuss DePauw’s approach to managing change so that other institutions can apply this model to other major changes.
  • What we’ve learned from rolling out new technologies, upgrades ect.People like there routine and changes can frustrate themFew things change faster than technology – I like to think that it changes at warp speedThe upgrade/rollout process costs productivity and moneyIT often underestimates the impact a change will make on the users
  • From what we learned, here is the model we followed for the Moodle transition and one that we will use again for subsequent technology changes.
  • Ask who will be impacted by this change? Those are your stakeholders and they deserve to be given some input on the process.These stakeholders also can offer a wealth of information on how the system is currently used and what they wish it could do – Microsoft now offers to collect usage data in Vista, but they don’t ask what we wish it could do!Making the stakeholders a part of the process will take some of the guess work out of making the decision to change
  • This timeline was adjusted as we went through the experience. Originally, we planned to retire Blackboard during the summer of 2008; however, several faculty members were still needing to transition so we extended their access to Blackboard until the middle of the fall 2008 semester. Of course, Blackboard administrators were still able to access just in case there was a special need. In December of 2008, Blackboard was history.
  • Training early adopters first will allow for you to get a baraometer reading of the new solutionAlso – They will get excited and spread the word to their colleaguesOffer training that targets different audiences, try not to intimidate novice users or bore the more advancedLeave the door open for walk-in consultations, host open labs and post lots of support materialsFor the Moodle project we had several Intro sessions early on for early adopeters and support staffMoodle user group as already mentioned offered an organic discussion for faculty and staffShowcases were given where faculty emembers presented how they use moodle for their teaching how they believe it helps A full day workshop was offered for facutly to go from 0-60 in one day!FITS summer workshop explaination
  • Here’s a chart of the three types of audiences we targeted and the kinds of training offeredOpen labs were just announced times where we would be available to help (people feel more comfortable knowing they aren’t bugging you)Intro sessions – during the transition phase early adopters were past this point so this was catered more toward new usersFaculty showcases – great for starting a discussion of how moodles features can enahance pedagogy, but might be overwhelming for a minimal userMUGS – Only useful for folks who are using moodleWorkshops- proposal based – clients are coached through to accomplish their goal
  • Admit that the tool and the transistion is not perfect and listen to how you can make it better This also will help you later when you need to implement another large changeResearch the problems – some else might have fixed the issue or another solution might exist check out or another community support forumReflecting on the whole process at the end will help improve the process next timeWe gathered this feedback via the MUGs and student workers and solutions were often found on or the NME forums
  • Results Hack implemented from to disable the preview functionInstalled the Gradebook Plus module for Moodle 1.8Moodle’s server patched to keep better timeAdded a warning to the screen
  • Adoption over time, note that blackboard was retired in the Fall of 08. Most of our courses were already moved into Moodle before than. Also note how our efforts had the additional effect of boosting the number of courses in an LMS, this was encouraging and showed us that the new system was well received even from people who never used blackboard.
  • Can’t keep everyone happy, but following this roll out model did reduce the amount of strife.Denial – I just figured out blackboard!Anger – we took these concerned into consideration and offered lots of time and resources for changingBarganing – We listened and offered an extra semester for the change!Depression – Attendance was sparse at early training sessions and user group meetings; but, as time went on, more and more instructors came to training sessions. They soon realized that creating course materials in Moodle was not as hard as they imagined.Acceptance - We have seen many instructors catch on quickly to Moodle, and get very excited about the flexibility it offers. In addition, new tools such as WIKIs and course calendars have been explored. This enthusiasm has be passed on to their collegues who then benefit from the new tools.
  • Thank you, any questions? Do you have any tips that we might want to add to our model?
  • Moodle At DePauw

    1. 1. Moodle at DePauw:A Model for Managing Change<br />Michael Gough&<br />Lynda S. LaRoche<br />DePauw University<br />
    2. 2. About DePauw<br />College of Liberal Arts and School of Music<br />Enrollment 2,298<br />Faculty (FTE) 238<br />
    3. 3. Rules of Thumb<br />People don&apos;t like change<br />Technology changes at warp speed<br />Researching, relearning and training costs productivity<br />IT can underestimate the impact of a change<br />Recipe for strife between IT<br />and the rest of the campus community<br />
    4. 4. Our Model<br />Bring stakeholders onboard<br />Identify factors pushing for change<br />Test and weigh options<br />Pilot with early adopters<br />Create a flexible roll out timeline <br />Communicate via multiple channels<br />Offer strategic support and training<br />Gather feedback<br />
    5. 5. Bring Stakeholders Onboard<br />Who’s primarily affected by the change?<br />Users: faculty and students<br />Support: Instructional & Learning Services / Information Services<br />Electronic Reserves: Library<br /> E-Services: Student information system<br />Streaming Audio / Media Resources: School of Music<br />Enable stakeholders to be an active part of the process<br />
    6. 6. Identify Factors for Change<br />Faculty Survey – Blackboard Basic<br />How are you using Blackboard?<br />What does it do well?<br />How does it lack?<br />What do you want to do with a learning management system?<br />Results – Faculty Feedback on Blackboard Basic<br />You cannot cross-link files or areas across courses.<br />It is not easy to navigate – “it’s clunky”, too many “clicks”.<br />It’s not reliable because it’s down a lot.<br />It’s good for distributing my classroom handouts, but it does not have enough interactive features.<br />It’s not learner-focused.<br />I have to fit my pedagogy into the tool instead of fitting tools into my pedagogy…it’s compartmentalized.<br />
    7. 7. Identify Factors for Change<br />Administrative Factors<br />Single sign-on capabilities (LDAP)<br />Integrate with other university systems<br />Sustainable and reliable<br />Predictable cost structure<br />Solid technical support from vendor or user community<br />Cross platform functionality<br />Customizable<br />
    8. 8. Planning Strategy<br />Faculty Driven Decision<br />Partnership between Faculty Instructional Technology Support (FITS) and the Academic Technology Advising Committee (ATAC)<br />FITS provided expertise<br />ATAC openly communicated with campus through every stage<br />ATAC made the final recommendation on what system best fit the needs of our campus<br />
    9. 9. Test and Weigh Options<br />Systems we originally researched: Sakai, Blackboard Enterprise System, Angel and Moodle<br />After further research and evaluation, the decision to focus our attention on Blackboard Enterprise System and Moodle was made<br />We already had experience with Blackboard and easily learned about the features of the Enterprise System<br />Moodle was new to us, so we spent significant time extensively testing it<br />
    10. 10. Focused Testing<br />Again, we focused our attention on feedback received from stakeholders<br />Usability of desired features<br />Flexibility of the system – capability to make changes to code, licensing restrictions, etc.<br />Integration with other campus systems<br />All features supported by Blackboard Basic must be retained<br />Robust support system<br />Implicit and explicit costs – licensing, training, support, etc.<br />
    11. 11. 1st Pilot with Early Adopters<br />The Academic Technology Advising Committee (ATAC) recommended running a pilot on Moodle<br />We sent a call out to campus and received several faculty volunteers<br />
    12. 12. 1st Pilot with Early Adopters<br />“Train the trainer” sessions were held to ensure we had sufficient staff available for supporting our pilot volunteers<br />Considerable learning was done and important information was obtained<br />The results of this first pilotwere positive, so a second pilot followed that wasequally successful <br />
    13. 13. What We Learned<br />No magic wand to easily convert courses from Blackboard to Moodle, but we did find bFree<br />Design factor in creating Moodle courses <br />Enable faculty and support staff to informally discuss what was going on – Moodle Users Group<br />Assure faculty you will be there for them as they go through the transition<br />
    14. 14. What We Learned<br />Pilot testing provided an opportunity for support staff to gain a better understanding of what would be involved in training and supporting Moodle<br />The Academic Technology Advising Committee (ATAC) decided to recommend Moodle be adopted as the sole learning management system on campus<br />Over communication is better than a lack of communication<br />
    15. 15. Create a Flexible Timeline<br />The larger the change the greater the need for careful planning and flexibility<br />Build enough time into your timeline so faculty members do not feel pushed into using a new system<br />When issues arise, listen to faculty members, let them know you understand their concerns and adapt your timeline appropriately<br />&quot;I don&apos;t have time to upgrade right now.&quot;<br />
    16. 16. Transition Timeline<br />Fall 2006 – Research, build test servers, extensive testing, “train the trainer” sessions<br />Winter Term 2007 – Training for faculty piloting system<br />Spring 2007 – First pilot<br />February 2007 – Faculty demonstrations for campus-at-large<br />March 30, 2007 – Recommendation to transition<br />Summer 2007 – Training for faculty participating in 2nd pilot<br />2007/2008 Academic Year – Provide both Blackboard and Moodle to campus<br />Fall 2007 – 2nd pilot also begins the transition to Moodle<br />Fall 2008 – Blackboard retired<br />
    17. 17. Communicate Multiple Ways<br />Open communication during every phase of this project was a key factor in making our transition successful<br />Use every avenue of communication possible<br />Newsletter published by Faculty Instructional Technology Support<br />Informative emails<br />Blog<br />Campus Newspaper<br />WGRE - our campus radio station<br />Word of mouth from early adopters proved invaluable<br />
    18. 18. Offer Strategic Support Training<br />Target early adopters first<br />Tiered training<br />Be available!<br />Moodle Transition<br />Intro to Moodle Sessions<br />Moodle User Groups (MUGs)<br />Moodle Showcases<br />Full-day Workshop<br />FITS Summer Workshop<br />&quot;I don&apos;t know where to get help.&quot;<br />
    19. 19. Moodle Training Strategy<br />
    20. 20. Gather Feedback<br />Criticism is not a bad thing<br />Implement tweaks based on feedback<br />Reflect on the whole process<br />Moodle transition process<br />Feedback gathered from MUGs and Showcases<br />Feedback from student workers<br />“They don’t listen to me.&quot;<br />
    21. 21. Lessons Learned from MUGs<br />Adding items were automatically previewed<br />Not able to edit gradebook, limited options<br />Quiz timer not accurate<br />Uploading a file to the advanced upload of files feedback removes grade and feedback<br />
    22. 22. Moodle Adoption<br />
    23. 23. Conclusions – Lessons Learned <br />The 5 Stages of LMS Grief<br />1. Denial or “I just figured out how to use Blackboard!”<br />2. Anger – Concerns over learning another system<br />3. Bargaining or “Give us one more semester!”<br />4. Depression – Low attendance at first<br />5. Acceptance or “Hey - this is cool!”<br />
    24. 24. Contact Information<br />Michael Gough, Instructional Technologist and Coordinator of Student Instructional Technology Support<br /><br />Lynda S. LaRoche, Assistant Director of Instructional & Learning Services and Moodle Support Coordinator<br /><br />Thank you!<br />