Welcome to the Campus Solutions 9.2 Advisory Group Meeting

1. Welcome to the Campus Solutions 9.2 Advisory Group Meeting Click here for phone number and passcode if you’d like to join by phone. • Instructions for listening via telephone is found on the screen’s top left. Note: the meeting invite had the wrong information – it is different for every user. • For listening ease, please mute your microphone/phone. • Save questions for the end or ask in the chat window. • This will be recorded and uploaded to our Training & Documentation page after the presentation along with the slides. Mute microphone and disable camera Open chat or view other participants

2. Campus Solutions 9.2 Advisory Group Meeting1-31-19 Betsy Watts, Project Manager CS 9.2 Subcommittee Tom McNaughton, Dee Muir, Crystal Tangsrud

3. Roll Call

4. Meeting Purpose Discuss the following • Advisory Group Homework • Module Updates • Decisions • Communication • Tiles • AG Communication • Project Status & Timeline • Testing and Sign Off • Training • Students & Faculty • Website Updates

5. Advisory Group Homework • Advisory Group Suggestions, Comments and Feedback • New Features & Functionality – Videos & Documentation Name something you liked • Name something you didn’t like • Access to Demo Environment Feedback • Was it easy to navigate? • Did it help with understanding the new system? • Survey Results Comments • Other Homework Discussed Later

6. Project Status Quick indicators that highlight the health of the project • Green: The project is performing to plan. G • Yellow: A problem has a negative effect on project performance but can be dealt with by the project manager or project delivery team. Y R • Red: There are significant issues with the project. G G G Y

7. Project Status • Demo Environment - Available • No Modifications or Customizations • Reviewed new features, functionality, look & feel • Dev Environment - Available • Modifications and Customizations included • Initial testing completed and cleanup continues • Evaluating which modifications and customizations can be removed • Evaluating which new features can be included by Go Live or after • Test Environment - In Progress • Expected Available Feb 15th

8. Draft Project Timeline • Test Environment - Feb 15th Available (11 weeks) • Technical focus is rewriting/testing code and integration testing • Functional testing continues • Wrap up changes to end-user security • Create documentation & training plans  • Stage Environment - May 3rd Available (10 weeks) • User acceptance testing • Technical team responds to any issues raised by the testers • Deliver training • Finalize detailed plan for deployment • Go-Live Production is July 12th Weekend • Query Environment will be available July 22nd – Working to improve date

9. Module Updates • Campus Community • Admissions • Student Finance • Student Records/Academic Advisement • Financial Aid • Ancillaries

10. Draft - Testing Specifics

11. Decision Making • Majority of decisions will be made by the project team • Module specific changes will be decided by the BA’s in close partnership with key stakeholders during FUG meetings • General changes will be discussed in the Advisory Group meetings • Dispute Resolution • The PeopleSoft Executive Steering Committee will review any business processes that the project team and stakeholders cannot agree on, or that are deemed out of scope.

12. CS User Group Training • Seeking Advisory Group Feedback • Pre-Survey Results indicated that many respondents preferred on site training. Now that you’ve been in the system, do you feel this is needed? • Currently, plans are to do the following: • Job Aids will be published on website • Live Blackboard training will be provided • Both general and module specific • Training will be recorded & available on website • Do these sound good? Are other options needed?

13. Campus Communication • General Communication to All • (Faculty, Staff & Students) • We will provide boiler plate materials electronically so campuses can customize and disseminate • Updates will also go to CIO Council • The next two slides will cover student and faculty communication with general discussion to follow

14. Students • Assumptions • We assume that all campuses will be communicating with students and may take advantage of the boiler plate documents we provide. • Feedback from the Peoplesoft Governance/Listening Tour suggested we reach out to the NDSA CTS Advisor Group. • Engagement • Working with NDSA – CTS Advisory Task Force Chair William Fleck • CTS Advisory Task Force demonstration planned for Feb • Training • NDSA didn’t think training necessary since it’s easier than the current system • Suggested brief tutorial along with contact information for additional help • Communication • NDSA suggested sending an email to all students about the change • One in May and another one right before Go Live • NDSA will include information about the upgrade in their newsletter

15. Faculty • Assumptions • We assume that all campuses will be communicating with students and may take advantage of the boiler plate documents we provide. • Engagement • Student Records User Group will devise strategy • Training • Communication Page intentionally left blank to solicit your suggestions and to spark conversation

16. Campus Communication • Other suggestions for communication? • Students • Faculty • Staff • How soon before Go Live should notification start?

17. Tile Recommendations Thoughts on locking down specific tiles Student Home Page Other Services Tile Help Center Information Tile (Following Slides)

18. Tile Recommendations Help Center Navigation

19. Tile Recommendations Information Center Tile

20. Website Update • Job Aids • New Navigation • Favorites • Shortcut key functionality • Glossary • FAQ’s • General Updates: Query cleanup

21. AG Communication Decided against using Microsoft Teams Plan to communicate via email Next Meeting: Thursday, Feb 28 @ 10 am

22. Measuring Project Success How should we measure project success? Pre-Upgrade 9.2 Survey feedback Staff Faculty Students

23. Open Discussion Forum