Table of Contents absoluteUrl true
Summary
The Chancellor’s Office, the CCC Technology Center, and the Foundation for California Community Colleges, in collaboration with the community colleges and in partnership with ideas42, are redesigning the CCCApply experience with a student-centered approach in mind.
Mission: Student-centered design in action
Goals: Redesign CCCApply so that it is student-friendly, simple, straight-forward, and collects enough data to properly initiate the on-boarding of the students.
Redesign Workgroup Members: Anderson, Christopher; Deb Barker-Garcia; Bryan Miller; Tim Calhoon; Craig Hayward; Lou Delzompo; Emily Gerofsky; Emily Robinson; John Helmer (Unicon); Lu, Tonia; Laura Metune; Michelle Pena; Mike Caruso; Stephanie Murguia; Patricia Donohue; Michael Quiaoit; Randy Tillery; Andrea Reynolds; Rita Gorgan; Rob Rundquist; Justin Salenik; Tessa Carmen DeRoy; Paul Feist; Tina King.
Project Goals & Objectives
Workgroup Committee & Description | Lead | Resources | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Project Goals | Omid Pourzanjani, CCCCO Barney Gomez, CCCCO | https://digitalfutures.cccco.edu/ | ||||||||||||||||
Overarching Objectives - See Table Below
| Omid Pourzanjani, CCCCO Barney Gomez, CCCCO | Click here > AB-3101 Community colleges.
| ||||||||||||||||
Design & Business Requirements | ||||||||||||||||||
| Special Implementations User Interface Changes Glue for CCCApply
| |||||||||||||||||
Questions & Fields: Sub-committee focused on reviewing questions and data fields required at the time of application to support Redesign project objectives | Omid Pourzanjani - Lead | |||||||||||||||||
Release Schedule | ||||||||||||||||||
Redesign Release 1 Production Release: September 28, 2018 Redesign Release 2 Production Schedule: December 7
Redesign Release 3 Production Release: March 15, 2019
Redesign Part 4 Production Release: June 2019 Scope:
| Patty Donohue Tim Calhoon | Release Roadmap
| ||||||||||||||||
Phase 2: Long-Term Redesign
| CCCApply Advisory User Group CCCApply Redesign Workgroup | Shared space under-development to track meetings, decisions, requirements reviews, approvals, and quarterly progress reports. | ||||||||||||||||
Sub-Committees | ||||||||||||||||||
Non-Credit Application Committee | Patty Donohue
| NOTE: Sub-Committee meeting minutes Non-Credit Sub-Committee Meeting Minutes & Discussions - Fall 2018 | ||||||||||||||||
Low-Hanging Fruit Committee | Patty Donohue - Lead Michelle Pena MItch Leahy Stephanie Murguia | Low-hanging Fruit #1 - Changes - DEPLOYED Q1 Low-hanging Fruit #2 - (Pending) | ||||||||||||||||
Questions & Fields: Sub-committee focused on reviewing questions and data fields required at the time of application to support Redesign project objectives | Omid Pourzanjani - Lead | /wiki/spaces/PD/pages/727843091 CCCApply Field Removal Recommendation 102218.xlsx Questions to be Removed Change Requirements (Worksheet) | ||||||||||||||||
Ideas42 Study Ideas42.org behavioral study on CCCApply in response to AB3101 | Harrison Neuert - Ideas42 Emily Gerofsky - CCC Foundation | CCC Diagnosis Deck Final (002).pdf (Ideas42)
| ||||||||||||||||
Changes & Low-Hanging FruitSub-committee focused on identifying changes and revisions that support Redesign project objectives and timeline. Special Implementations User Interface Changes Glue for CCCApply
|
| Low-hanging Fruit #1 - DEPLOYED September Release Non-Credit Application Workflow /wiki/spaces/OPENAPPLY/pages/723812439 Change Management Office procedures (Amanda) | ||||||||||||||||
Communications | Omid Pourzanjani - CCCCO | |||||||||||||||||
Meetings | CCCapply Redesign Meeting Agenda 120618.docx CCCapply Redesign Meeting Minutes 102618 (1).docx |
Phase 1 Redesign Development Roadmap
This roadmap outlines the work planned or completed in the first phase of the redesign project dedicated to simplifying the current version of CCCApply.
Roadmap Planner | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overarching Objectives
The following project objectives are in response to Assembly Bill 3101. In addition, all efforts are being made to address AB705 (multiple measures) across the Core Applications.
Streamline and simplify the CCCApply experience with a student-centered approach in mind that complies with the requirements of AB3101
The Redesign Workgroup is exploring ways to redesign CCCApply to be student-friendly, simple and straightforward, and to collect enough data to initiate the onboarding of students.
Short-term Redesign:- Identify low-impact changes (low-hanging fruit) to implement to the current version
- Support non-credit students with a residency-exempt version of the Standard Application
- Incorporate recommendations from the Ideas42 behavioral study
- All-new micro-services-based form engine with new Download Client 2.0
- All-new student-centric UI with mobile-friendly, multi-language, modern support services
- Fully integrated with MyPath and SuperGlue for cohesive matriculation
- Redesign & streamline the CCCApply Standard application and get the data to colleges quicker, easier and more frequently
OUT-OF-SCOPE for Phase 1: CCCApply FY18-19 Work plan
Major overhaul to the user interface and enhancements to implement modern micro-services architecture (APIs, backend, data integrations, web services, etc.)
- streamlined data collection (major overhaul to the user interface)
- New modern, micro-services-based backend, APIs, and responsive, modern UI
- Modern deployment process
- Comply with AB705 and AB3101
- Redesign & streamline the OpenCCC Account system and get the data to colleges quicker, easier and more frequently
OUT-OF-SCOPE for CCCApply FY18-19 Work plan - See Grant: Shared Infrastructure - OpenCCC
- streamlined data collection (major overhaul to the user interface)
- New modern, micro-services-based backend, APIs, and responsive, modern UI
- Modern deployment process
- Comply with AB705 and AB3101
Support Non-Credit Students with Residency-Free Workflow
Collaborate with the CCC non-credit community and Ideas42 to design and implement a modern, user-friendly, electronic application that supports the needs of our diverse non-credit student populations - allowing colleges to collect only what's necessary at the time of application to comply with AB3101.
- Using the existing CCCApply standard application, remove all residency questions and other questions that are not required at time of application;
- Remove the Residency page and all it's questions
- Remove the Citizenship & Military Status page and all it's questions
- Remove several questions on the Needs & Interests page
- Questions, language, and flow would be determined and approved through collaboration of the CCCApply Redesign Workgroup (CO) and other stakeholders (User Groups) and supported with recommendations from Ideas42 behavioral study);
- See "Non-Credit Application Sub-Committee" meeting notes
Overarching Objectives
The following project objectives are in response to Assembly Bill 3101. In addition, all efforts are being made to address AB705 (multiple measures) across the Core Applications.
Streamline and simplify the CCCApply experience with a student-centered approach in mind that complies with the requirements of AB3101
The Redesign Workgroup is exploring ways to redesign CCCApply to be student-friendly, simple and straightforward, and to collect enough data to initiate the onboarding of students.
Short-term Redesign:- Identify low-impact changes (low-hanging fruit) to implement to the current version
- Support non-credit students with a residency-exempt version of the Standard Application
- Incorporate recommendations from the Ideas42 behavioral study
- All-new micro-services-based form engine with new Download Client 2.0
- All-new student-centric UI with mobile-friendly, multi-language, modern support services
- Fully integrated with MyPath and SuperGlue for cohesive matriculation
- Redesign & streamline the CCCApply Standard application and get the data to colleges quicker, easier and more frequently
OUT-OF-SCOPE for Phase 1: CCCApply FY18-19 Work plan
Major overhaul to the user interface and enhancements to implement modern micro-services architecture (APIs, backend, data integrations, web services, etc.)
- streamlined data collection (major overhaul to the user interface)
- New modern, micro-services-based backend, APIs, and responsive, modern UI
- Modern deployment process
- Comply with AB705 and AB3101
- Redesign & streamline the OpenCCC Account system and get the data to colleges quicker, easier and more frequently
OUT-OF-SCOPE for CCCApply FY18-19 Work plan - See Grant: Shared Infrastructure - OpenCCC
- streamlined data collection (major overhaul to the user interface)
- New modern, micro-services-based backend, APIs, and responsive, modern UI
- Modern deployment process
- Comply with AB705 and AB3101
Support Non-Credit Students with Residency-Free Workflow
Collaborate with the CCC non-credit community and Ideas42 to design and implement a modern, user-friendly, electronic application that supports the needs of our diverse non-credit student populations - allowing colleges to collect only what's necessary at the time of application to comply with AB3101.
- Using the existing CCCApply standard application, remove all residency questions and other questions that are not required at time of application;
- Remove the Residency page and all it's questions
- Remove the Citizenship & Military Status page and all it's questions
- Remove several questions on the Needs & Interests page
- Questions, language, and flow would be determined and approved through collaboration of the CCCApply Redesign Workgroup (CO) and other stakeholders (User Groups) and supported with recommendations from Ideas42 behavioral study);
- See "Non-Credit Application Sub-Committee" meeting notes
Blockers & Issues to Proposed Changes
These are issues that will be raised to the CCCApply Steering Committee and the Chancellor's Office for legal opinion and approval. They need to be addressed before we can confirm the requirements.
Discuss the fact that AB3101 does not address or provide guidance on how colleges are supposed to track and manage residency for a "non-credit" student who decides to cross over and take "credit" courses.
- Can they do that without completing the full standard application?
- Do students need to agree to "terms" that they understand the non-credit status?
Does CCCApply need to incorporate a disclaimer that non-credit students are completing the non-credit application?
Non-Credit Issues
In order to comply with the new AB3101 - we’d need the legislation to address the following questions:
IF non-credit students are not subject to residency classification requirements:
- What is their official residency status?
- Are we allowed to automatically classify them as a non-resident, according to the law?
- What fees should they be charged?
- Non-resident or resident fees if taking credit courses at the same time or transitioning to credit courses?
- Are they allowed to transition to credit courses while they are taking non-credit courses?
- If not, would they have to re-submit an application before transitioning to credit.
- If we are not collecting residency for non-credit, how does this impact apportionment?
- ? Are Non-credit non-residents not included in apportionment?
In-Scope for March Release
If the NC population does not need to be classified for residency, we can then remove all the RDD-logic questions from that special application.
Any question that begins with "As of RDD, what is your....?" we should replace that with the first day of the fiscal year?
"As of July 1st of this year, what is your...."
In-Scope for March Release
<non_credit>
<int_fg_81>
Discuss the need for Adding a new "flag" or field such as: <non-credit status = Yes{term_id} that would be included in the Noncredit application URL & downloads to indicate the student applied using the Non-Credit Application during a specific term.
Discuss that the language in AB3101 specifies that the Chancellor of the CCC has greater authority to determine how residency is determined for Non-Credit students, etc. Would this authority also allow the CCCCO to implement an "annual RDD date" or two "standard term start dates"?
Proposal: Petition the legislature to support a standard annual RDD (July 1). The benefits of this change
Change Requirements Deadlines
*Due to the current budget and team capacity, even approved changes that do meet the deadlines below are not guaranteed inclusion in the release(s).
FINAL DEADLINES | ||
---|---|---|
Change Management Activities | Q3 Release - March 2019 | Q4 Release - June 15, 2019 |
Submit Change Request | December 31, 2018 (Jan 3, 2019) | February 28, 2019 |
T-Shirt Size Estimate | January 8, 2019 | March 7, 2019 |
Budget Review | January 8, 2019 | March 9, 2019 |
Written Sign-Off on Vetted Approved Changes | January 9, 2019 | March 15, 2019 |
Resources & Capacity Estimates | ||
Story / Epic Business Requirements | January 11, 2019 | March 25, 2019 |
Technical Estimate | January 11, 2019 | March 27, 2019 |
Release Management Activities | ||
Code Freeze | January 31, 2019 | May 16, 2019 |
Pilot Release (30 Days) | February 15, 2019 | May 31, 2019 |
Pilot Release (2 Weeks) | March 1, 2019 | June 14, 2019 |
Production Release | March 15, 2019 | June 28, 2019 |