DegreeWorks Overview

1. DegreeWorks Overview

2. UA Quick Facts • Enrollment: 31,747 • Undergraduate: 26,234 • 8 Colleges • 150 Majors • 85 Minors • Graduate School: 4,913 • Professional: 600

3. UA Quick Fact • Number of Advisors in DW: 1,458 • Implementation Started August 2008 • Advisor Go Live: May 2009 • Student Go Live: June 2009

4. DegreeWorks Demonstration

5. Degree Checkout Using DegreeWorks

6. Degree Checkout Report • Present summary data from DegreeWorkson students who have applied to graduate • Group student by problem levels • Allow colleges to identify subset of problem students • Frees resources to concentrate on real issues impeding degree completion

7. Student Grouping • Tier 5 – Catalog not in DegreeWorks • Catalog requirements not in DegreeWorks • Tier 4 – Award • Student has satisfied all degree requirements • Tier 3 – Pending Completion. • Students at 98 percent of requirements met – in-progress courses to be completed.

8. Student Grouping • Tier 2 – Issues to be Resolved • Show 90-97 percent of requirements met. • Generally due minor issue such as lack of transfer work, course substitution, etc. • Tier 1 – Significant Issues • Less than 90 percent of requirements met • Generally due to significant transfer work missing, incorrect program of study, premature application, etc.

10. Degree Checkout • Initial Review of Degree Application • College will use report to concentrate on students with less than 98 percent of requirements met. • Final Review of Degree Application • Degree will be awarded to students with 100 percent of requirements met

11. Degree Checkout • Awarding Degree • Automatically award students with 100 percent or requirements met • Use “Mass Entry Graduation” (SHAMDEG) • Set coding to filter or use Population Selection • Requires confidence in the audit

12. Lessons Learned

13. Student Lessons Learned • Students Needed No Convincing! • DegreeWorks sold itself with • ease of use and simple navigation

14. Student Lessons Learned • Make and Keep DegreeWorks Visible • Through college/advisor communication with students • Through placement of sign-on/log-in link • Through campus marketing effort

15. Student Lessons Learned • Keep DegreeWorks accurate and up-to-date • Make sure program information is correct and current • Keep up with any plans, notes or exceptions that need to be added to students’ audits. If the tools are there, they expect their advisors to be using them

16. Student Lessons Learned • Allow for feedback • Gave students avenues through which they can communicate questions, concerns and problems. • Listened and responded to their feedback. • Were available to meet with students individually and with classes of students for Q&A sessions and continuing education on the product.

17. Advisor Lessons Learned • Letting go of paper check sheets • #1 fear on UA campus • Trepidation rooted in lack of trust in the audit/program • Audit is only as accurate as the information being relayed to the programmers • Give feedback to the correct people (more on this next)

18. Advisor Lessons Learned • Encourage Feedback • Have clearly defined channels within departments, colleges, etc. through which questions, comments, problems can be relayed • If you see a problem, tell someone • Relay student feedback

19. Advisor Lessons Learned • Is DegreeWorks going to replace me as an advisor? • DegreeWorks is there to make your job easier – not replace you • Eliminated the need for filling out check sheets or manually updating progress towards degree • Allowed for more time and more meaningful conversations between students and advisors

20. Advisor Lessons Learned • Develop strategies that work for you • Incorporate DegreeWorks into advising in ways that work for your college or department • Examples from colleges at UA • Incorporate planning into classroom assignments • Require students to create and save plans prior to advising sessions

21. Questions