FY 24/25 Product Roadmap

The CVC Exchange requires continuous improvement and remediation of the product platform. This is an ongoing cycle to address:

Prior Tech Debt and Manual Processes from the Original Minimum Viable Product (MVP) release - These elements were identified at the outset of the platform as necessary or desirable for streamlining operations (e.g. integration for student eligibility analysis, financial aid streamlining, etc.) These are identified for future product enhancements and rolled out through Release Management as they are developed.
Feature Requests and Identified Needs - As usage of the Exchange grows, new functionality is inevitably identified as desirable or necessary for continued expanded use of the service. These features are identified through production support tickets, solicited user feedback, and requests from Exchange stakeholders such as the Consortium and other user groups. The product team actively reviews requests and input from these various channels and determines items for planned future development. Additionally, the product team identifies other required planned improvements to the platform to keep up with security needs, new technical capabilities and trends, best practices from the field, and discovery from User Acceptance Testing (UAT) during Quality Assurance reviews and implementations.

The CVC product roadmap is intended to outline and ensure the body of product development work is organized with the following goals in mind.

Prioritization
Identifying and prioritizing features and improvements based on user needs and business objectives
Transparency
Providing stakeholders, including colleges and the Chancellor’s Office, with a clear view of what to expect in the future
Risk mitigation
Identifying potential challenges and risks early in development
Communication
Articulating strategic thinking behind the proposed product improvements and the plan for getting there

Prioritization: All work is organized into Quarterly Sprints and provides an outline for the planned improvements and new functionality to be added in the upcoming Fiscal Year. Development items are categorized by quarter with issues/tickets grouped into sprints based on the order in which they must be delivered to achieve a new functional element. For example, if adding a new workflow, workflow business requirements and design elements are delivered prior to engineering/coding, QA, and so on. Issue planning prioritizes all work with vendor teams based on the following criteria.

Priority 1. Resolve Functional Production Issues (product not working as designed) - These items are constantly triaged, top priority, other work may be deprioritized in the sprint as appropriate

Priority 2. Identified Strategic Enhancements (adding functional improvements that increase engagement with the platform, reduce workload for stakeholders, or improve end-user experience with the product, or are necessary for Exchange implementation in upcoming or current cohorts) are often tied to contract deliverables with vendor teams as required improvements to the service. This work is planned over time.

Priority 3. Prioritized Enhancements (quality of life improvements for users, administrators, stakeholders, etc. that have been identified as necessary for resolving identified operational shortcomings in the product, or reducing friction points in the service). This work is reviewed regularly upon availability in the sprint and LOE.

Priority 4. New Ideas (recommendations or feature requests from end users that are desirable, but do not provide required functionality for maintaining operations. These may include LOE review or SPIKE analysis and technical research). This work is reviewed periodically throughout the year as deve resources become available.

Themes: CVC also organizes work around specific themes or functional areas for focused improvements. These are tied to contract deliverables with the CVC vendor teams and include specific elements of required functionality. The themes for the 24/25 FY are outlined below.

Fraud Prevention
Addition of CALGETC Transferability Search Option
Accessibility Enhancements
Data Access Improvements
eTranscript Automation
Administrator UX Improvements
Session Management Enhancements
Release Management Streamlining

Production Issue Management | Prioritization & Status

As production issues are reported from students and colleges, we make those items a top priority. Below are all the production issues that have been reported and the status of each issue for this fiscal year.

Legend For Status

in progress = In Development
blocked = Blocked
Done = Finished/Closed
not done/closed = No work was done to/no longer needed
backlog = Work not started

Legend For Priority

Low
medium
high

Roadmap Forecast Overview (Projections)

This chart shows a forecast of what JIRAs were projected to be worked on/finished in each quarterly sprint in this fiscal year. However; due to shifting priorities, not all of these will be selected for development, worked on, or finished in the quarter. For a real-time view into what was finished in each sprint, see the quarterly sprint tables below.

Detailed Quarterly Sprints

Legend For Status

backlog = Dev work has not started
in progress = In Development
blocked = Blocked
testing/review = In Testing
Done = Finished/Closed
not done/closed = No work was done to/no longer needed

Legend For Priority and Dev Effort

Low
medium
high

Q1

Q2

Q3

Q4