Enrollment Management Project Request Form

Open

Last Modified: Nov 13, 2024

Directions for Use

Section One - General Project Information

• Submitted by: Should be one of the Enrollment Management Directors.

• Brief project description: High-level, non-technical, short summary (2-3 sentences) of the project.

Section Two - Project Details

Project Type

• Emergency: This type of project typically will not be submitted via this project form. These are projects that are urgent for continued business operations. I.e. Cal State Apply continued modifications.

• Fix/Minor: Typically will not require approval or project form submission. These include CO delivered maintenance packs, bug fixes, and other minor changes to existing programs.

• Major Development: These are projects more complex than minor enhancements that require approval. These typically require formalized requirements gathering/discovery, timelines, testing plans, and a project manager assigned. These projects should have a wide-ranging impact to the campus or Enrollment Management.

High-Level Objectives

• Guidelines: Two or more bullet points of high-level non-technical objectives of the project. Include how the project affects students.

Section Three - Detailed Project Description

• Guidelines: Beyond technical details of the project also include key responsibilities (who will be testing, who will be planning ongoing meetings, etc).

Section Four - Project Scope

Development Complexity

• High: This classification of project typically is the most challenging with a number of components and interfaces. Examples of objects and projects include:

  • 81+ hours development and 40+ hours testing

  • Self-service projects touching delivered objects  Data modeling/analysis type logic

  • Modifications to delivered Oracle or CSU baseline projects

  • Third party integrations (external systems)

  • Involvement of multiple IT/functional teams

• Medium: This classification of project usually contains a number of new objects such as PeopleSoft pages, processes, and/or reports. Examples of objects and projects include:

  • 31-80 hours development and 20+ hours testing

  • New reports (but with some basis on existing reports)

  • Work Center design with Queries

  • PS Query involving cross unit data (i.e. AD + SR + AA, etc.)

  • Involvement of single IT/functional team

• Low: This classification mostly focuses on quick fixes and minor enhancements to existing processes and reports. Examples include:

  • 20-30 hours development and 10+ hours of testing

  • Fixes and enhancements to existing programs

  • New document types or modifying existing letter templates

  • New sub-reports

  • Involvement of single development and functional member

Testing Complexity

• High: High Complexity (40+ hours)

  • Regression testing of existing functionality

  • Full unit/integration testing

  • Requires fully developed test plan with many scenarios delivered Oracle or CSU baseline projects

• Medium: Medium complexity (20-39 hours)

  • Limited impact on other processes

  • Unit/integration testing

  • Requires testing but not as fully detailed as with higher complex projects

• Low: Low complexity (10-19 hours)

  • Limited to no impact on other processes

  • Unit/integration testing

  • Some simple scenarios and output checked

Estimated Hours

Add the max hours selected from Development Complexity, Testing Complexity, and an additional 20% to arrive at estimate for hours of time needed to complete project. I.e. [High Complexity project (81 hours) + Medium Testing (39)] * 1.20 = Mix 144 hours.

Impact Field Definition

• High: Wide campus impact affecting a number of departments or strategic planning initiatives.

• Medium: Campus impact affecting a large group of student populations or departments with college-level impact.

• Low: Localized impact affecting a small group of students or impact limited to a few departments.