Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

THIS IS A DRAFT AND A WORK IN PROGRESS.  ALL COMMENTS ARE APPRECIATED.

Unable to render {include} The included page could not be found.

Summary

After receiving the completed template, requests are logged and categorized. This is sometimes followed by a technical evaluation by the OIT manager to supply additional information on the work involved.

Request Type   

Detail

Campus requests

  • These are for new systems or system enhancements which affect or are visible to the campus.
  • They meet the needs of campus departments, functional offices, or individual units.

Internal requests

  • These are usually projects which are not directly visible to the campus community.
  • These projects could include major hardware, software, or framework upgrades that impact OIT staff.
  • These sometimes involve back-end work to campus systems, or requests to asses and introduce new tools, utilities or technical solutions.
  • Internal requests are generally submitted by OIT staff.

Mandated requests

  • These include requests that are mandated by the Federal or State Government, UC Office of the President, Auditors, or other regulatory agencies.
  • These requests often contain compliance deadlines that the campus must meet.

Less than 80 hours' work or Cancelled requests

  • This category includes campus requests that are found to be less than 80 hours of work after a technical review has been completed (see below).
  • The person submitting the request may also cancel their reques for a number of reasons.
  • If the request is not well defined and no additional information is provided when asked for by OIT, the request may be cancelled.

Work Estimate / Technical Evaluation

  • Campus requests are routed to the project manager for technical evaluation and time estimate.
  • The hours estimated for the project are based on a general understanding of the project and its scope.
  • Estimated hours for development projects should include all phases of the development effort including requirements gathering, design, coding and testing, documentation, and implementation. Estimates for other projects should include time for installations, coordination, tracking, and implementation.

Project Budget

  • An initial budget for the project will be derived based on the project's estimated hours.  This is a ballpark estimate which may be revised once the project has been scheduled and the requirements are more completely understood.
  • If resources and skill leves are available to cover the budget for the project, work on the project will be scheduled accordingly.

  • No labels