Post on 27-Dec-2015
transcript
How we trained our way to the world of MAUI
Kati Bates & Josh HutchisonUniversity of Iowa
Thursday, November 8, 20121:45 p.m. – 2:45 p.m.
Made
At
University of
Iowa
MAUI
Planning our Trip to MAUI
Mainframe integration and migration to MAUI
Itinerary
Campus Buy In Campus Advisory Committee
(Deans, Directors, Faculty) Campus Wide Open Houses for Academic
Users (MAUI developers , big kahunas) Student Academic Users Group (Colleges, Departments, Registrar staff…) Email, Meeting Minutes, Communication with
users
All Aboard!
Pilot Participants with Diverse Population (Undergrad/Graduate/Professional/Off Campus Programs)
Internal Focus Groups (Registrar Staff with Programmers to develop specialized screens)
System Integrations (Vendor Products: Courseleaf, U.Achieve, NOLIJ, Ad Astra, Platinum, Unitime, Synapsis)
Testing with Pilot Groups, Registrar Staff, Programmers (Screens functional and stable)
Pre-Departure Checklist
Universal Storage for Help Documents / Meeting Minutes / Historical Documentation / Rules and Crosswalks (Wiki was decided on)
Sort and Maintain the Wiki page (Who would create and update content / grant access for users)
Help Screens (Ease of use, searchable, printer friendly)
Test MAUI / JIRA (Used to find bugs, request improvements and report to developers)
On Board Assistance:Concierge Service
Advertise TrainingSession Announcements (In person & via
email)Faculty & Staff Invites
Utilize Registration & Tracking via the University of Iowa Self-Service System
Allowed for Attendance Recordsand Survey Results
Captain’s Announcement
Go Live with Individual Modules at each phase of development
Unique Training opportunities depending on your role on campus Lectures Hands On Training (Small groups / One on One) Simple Short Sessions to avoid information overload Q & A Opportunities Handouts
First Voyage
Things we planned for and things we didn’t expect to encounter Hearing Impaired (Hired a sign
language interpreter) Visually Impaired (Utilized users own
unique software) Mobility Issues (All rooms handicap
accessible)
Encounters
Setting up Access Roles (Everybody wants everything)
Change difficult for users (We’ve always done it that way!)
Negative feelings (Workload increased for some users due to decentralization)
Performance Issues (Slow page loads, Error 500s) Communication issues with Programmers
(Different wavelengths for prioritization)
Rough Seas
Time commitment to training / testing / presenting while maintaining normal workload
Office reorganization (Additional MAUI responsibilities plus staff additions)
Mandatory training required by departments led to some negative comments
Technical Failures (Last minute room changes, projector bulb burn out)
Code Rollouts during presentations
More Rough Seas
Benefits and Improvements All in one system, no need to jump
between programs More departmental ownership and
responsibility Workflow led to a more streamlined
approval process Data captured for historical records
Calm Seas & Sandy Beaches
Keep a positive attitude Sense of humor Treats / Food (Always helpful) Opportunities for departments to
train their own staff Constant and consistent updates
Fun & Games
One on one Small Groups Troubleshooting (Email / Phone) Tailor made training (Focused on
unique areas)
Ongoing
Short PowerPoint presentations on web New Hire Training program Refresher Training New Module training as developed Advanced as needed or requested
Future Trips
Q & A