1 / 13

DegreeWorks Implementation

West Virginia University’s. DegreeWorks Implementation. Contents. Introduction Time Line Pilot Programs Testing Training Validation Marketing Lessons Learned. Introduction. WVU rocked by scandal in 2007-2008 Series of AACRAO and other recommendations to improve process and integrity

adler
Download Presentation

DegreeWorks Implementation

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. West Virginia University’s DegreeWorks Implementation

  2. Contents • Introduction • Time Line • Pilot Programs • Testing • Training • Validation • Marketing • Lessons Learned

  3. Introduction • WVU rocked by scandal in 2007-2008 • Series of AACRAO and other recommendations to improve process and integrity • No registrar’s office before July 2009 (Combined Admissions and Records) • WVU also did not have an online degree audit system instead relying on paper check sheets • As part of the remediation (and AACRAO’s recommendations), WVU purchased Degree Works and began implementing it as quickly as possible

  4. Time line • Spring 2009 – Purchase Software • Fall 2009 – First Staff hired for project • Nov. 2009 - First Training with Developer • Summer 2010 – Pilot Launch • Feb., June 2010 - Additional staff hired for project • January 2011 – Go Live Undergraduate Programs

  5. Pilot Programs • Implementation began with pilot schools to work out any issues with the system • A new degree audit tool was initially for advisors and selected majors as part of the University’s pilot program • Pilot schools were selected based on their curricula • Program requirements provided significant meaning as part of the pilot

  6. Pilot Programs • Included undergraduate programs from four colleges within the university • Able to obtain valuable feedback from students and advisors • The new degree audit system allows students—with just a few clicks— to review, monitor and track their degree requirements • There were a few minor issues related to transfer credits and instances of students either not knowing their degree required a course or realizing a particular class didn’t fulfill a particular requirement

  7. Testing • Quantitative vs Qualitative • Comparison of Test and Production Environment • Originally looked at 25 students for each feature or update and did not look at the interactions with all of the features • Later, we analyzed how the features were interacting together and discovered this was more effective

  8. Training Introduction to DegreeWorks How to search for students How to read an audit How to trouble-shoot How to Get a Clean Audit Checking data from Banner Exceptions processing Features Focuses on new features

  9. Validation • What did NOT Work • Large Group testing • Email Validation • What DID Work • One on One testing • Updates via-phone during testing meetings • Documentation Sheets • Sign-Off Forms

  10. Marketing • Postcards • Posters • Video • Bus Shelter Ad

  11. Lessons Learned • Become a friend with the Action Line • Attend the DegreeWorks Symposium early and often • Develop buy-in from central IT • Develop buy-in from departments • Appropriately resource project • Develop your core strategies in advance • Test each feature thoroughly • Avoid assumptions

  12. Questions

  13. For additional information please visit http://registrar.wvu.edu/dw Jerry.Ross@mail.wvu.edu Kent.Campbell@mail.wvu.edu Kylie.Edmond@mail.wvu.edu Contact Information

More Related