SummaryAfter receiving the proposal, it is logged and categorized. Request Type | Comments |
|---|
Campus requests | - This includes systems or system enhancements which affect or are visible to the campus users.
- These can be broken down into:
- Projects that can be satisfied with existing team resources
- Projects that need resources beyond those assigned to the team. These projects will need to go through an additional review phase.
| Internal requests | - These projects are usually not visible to the campus community and may include hardware, software, or system upgrades.
- These sometimes involve back-end work to campus systems, or requests to assess and introduce tools, utilities or technical solutions.
- Internal requests are typically submitted by OIT staff.
| Mandated requests | - These requests are usually mandated by the Federal or State Government, UC Office of the President, Auditors, or other regulatory agencies.
- They often contain compliance deadlines that the campus must meet.
|
Work Estimate / Technical Evaluation- Proposals are routed to the responsible OIT manager for technical evaluation and time/budget estimate.
- Estimated hours for development projects should include all phases of the development effort including requirements gathering, design, coding and testing, documentation, training and outreach, and implementation. Estimates for other projects such as vendor software should 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 Budget- An initial budget for the project will be derived based on the project's estimated hours, any software licensing and hardware or equipment costs, training and possibly consulting costs. This is a ballpark estimate which may be revised once the project has been scheduled and the requirements are more completely understood.
|