| Table of Contents | ||||
|---|---|---|---|---|
|
...
The passage of AB 3101 gave us the latitude we needed to deliver a modified version of CCCApply for our non-credit student population. Lifting the requirement for uniform residency determination for all students allows us to look at other questions and steps that might be omitted at the time of application. Our goal is to find balance in what is asked of the student that is applying for college while still collecting all of the information required for state and federal reporting purposes.
| Info |
|---|
| The CCC Chancellor’s Office is driving changes to ensure CCCApply supports students through the community college application and enrollment process, and is targeting development and implementation of the redesigned system in fall of 2019. Activities such as reducing the number of questions in CCCApply and creating a simpler application for non-credit students which began last fall 2018 has been bolstered by the passage of Assembly Bill 3101. The Non-Credit Application Workflow path is a project of the CCCApply Redesign Project. |
...
Development and implementation of the Non-Credit Application will roll out in phases. The first phase, development, has already begun and a soft-launch release to the Pilot environment is scheduled for February 1519, 2019 as part of the CCCApply 6.4.0 release. Below is a breakdown of the implementation project plan.
Phase 1: Development & Soft Launch
Development of the Non-Credit Application path within the Standard Application (MVP requirements) began in September 2018 and the initial version will soft-launch in February 2019.
Development requirements for the minimum viable product for release (MVP) are here.
Phase 2: Pilot Project
Beginning with the soft-launch on February 19, a college pilot of six districts* will test the new non-credit application to work out the bugs, identify issues, and ensure all post-submission data and workflow processes are ready for production release. Pilot colleges will be required to participate in extended user acceptance testing and IT staff must support the effort with full implementation and integration with their SIS systems. Bi-weekly feedback meetings will be recorded and shared with colleges.
Pilot Project Objectives:
*TBD. Depending on level of response by colleges to participate, this number may change.
Pilot User Acceptance Testing
Pilot Updates
Bugs and other issues will be prioritized for fix throughout the 12-week pilot project. A change deadline schedule is below (subject to change):
...