2018 CCC Administrator UX Sub-Committee

The purpose of this advisory committee is to provide support to the CCCApply product manager and development team in the design, development, and implementation of the CCCApply admin modules in the new CCC Administrator.  

NOTE: A primary objective of this committee is to provide testing, migration, and implementation support to the CCCApply management and technical teams. See more objectives below.

Meet every 3 weeks between January 22 - June 7, 2018 to support the first release of the new CCC Administrator for CCCApply. 

1. User Acceptance Testing:  Support the Administrator development team with testing and review functionality in the following areas:

   1. HIGH PRIORITY:  Access management, User account setup and test SSO authentication

   2. HIGH PRIORITY:  Authorization testing (ensure secure access to college & district data, settings, configurations)

   3. CCCApply admin configuration, migration, and implementation in new Admin system

   4. CCCApply - onscreen text, instructions, hover help (where applicable) and user guide documentation

   5. CCCApply - review primary (global) navigation functionality: College changer, Module Menu bar, global Header navigation, application switcher

2. Support development of the Migration and Implementation Plan

   1. Review ETL and migration of college data configurations and settings

   2. Ensure all college data and settings are migrated over to  new system

   3. Identify areas that require college maintenance 

   4. Test rules and supplemental questions processing

3. Review and test new features: Majors module (filter and display Majors by meta majors, special category, or guided pathways)

   1. Setup and test the new Majors filtering options:  Category fields and Education Goal filter

   2. New college & district table contact data fields; Multiple Measures Initiative, and SPAM Filter UI screens

   3. Support testing new enhanced Majors module functionality

   4. Application landing page features

4. Support remaining development process:

   1. Review business requirements and ensure stories for MVP comply with those requirements

   2. Attend development sprint demos (every 3 weeks) and provide feedback for development & design teams

   3. Review change requests for feature enhancements

   4. Gather requirements for future enhancements

      1. map out on Roadmap for September 2018 / March 2019

      2. Track all features that haven't been prioritized or were re-prioritized for the MVP launch in May 2018.

5. Review user documentation: User guides & training videos  (User Guides, Help tutorials, etc.)