Proposal Review Process

After OIT receives a project proposal, it is logged and classified.

Project Class	Comments
Campus	This includes projects which affect or are visible to campus (non-OIT) users.
Internal	These projects are usually not directly visible to campus users and include such things as infrastructure, hardware, software, and system upgrades. These sometimes involve back-end work to campus systems, or requests to assess and introduce tools, utilities or technical solutions.
Mandate	These projects represent work resulting from mandates from federal or state agencies, UC Office of the President, auditors, or other regulatory agencies. They often contain compliance deadlines that the campus must meet and the generally result in re-evaluation of other priorities to free up resources.

Proposals are reviewed by a Project Review Team (PRT) consisting of a number of senior technical OIT staff and subject matter experts.
The PRT selects (or confirms) a team within OIT that will be responsible for in-depth technical evaluation, time and budget estimate, and possibly implementation of the project.
Estimated hours for development projects include all phases of the development effort including requirements gathering, design, coding, testing, documentation, training, outreach, and implementation. Estimates for other projects such as vendor software include time for installations, coordination, tracking, training, and implementation. Often, Memorandums of Understanding (MOUs), and Service Level Agreements (SLAs) will be required for special projects.

Project Proposal Process
Overview
Identifying a Project
Submitting a New Project
Project Naming Standard
Process Flow Diagram
Project Proposal Review Process
Project Scorecard
Project Execution & Monitoring

Reporting
Project Logs
Project Archives