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 7 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.

What types of projects need to go through the prioritization process?

  • Any project that involves resources from a campus unit that plans to offer a developed or vendor system for the entire campus.
  • Any project that will interface with an Enterprise system.
  • Any project that wishes to utilize funding from the central pool of  IT dollars.

How are cost estimates developed?

Cost estimates are based on a time and materials model.   First, available discretionary resources are assessed, and if available, factored into the project proposal. Then, additional resources such as contract staff are added. Rates for contract staff will vary, depending on the role. Some common rates include:
Developers - $60/hr
Typical application or vendor consultants  - $220/hr
 

What happens if requirements need to be added after a project has been approved?

If requirements need to be added after the project has started, the project cost will go up. If the project costs exceed 110% of the original estimate, the project must go back to the OIT Oversight Committee. The project may be cancelled if significant increases in the project cost impact the business case.

What happens if a project doesn't meet its target implementation date?

If the project duration increases more than 125%, it must go back to the OIT Oversight Committee for review.

Will projects that are approved begin immediately?

Not necessarily. The availability of internal resources, such as analysts, subject matter experts and developers varies over time. To guarantee their availability would require staffing at a very high, inefficient level. Projects will be started based on a combination of factors including their submission dates, value, functional priority and availability of resources.

What kind of technical review do projects go through?

The Enterprise Architecture and Technology Review Committee's purpose is to review all significant projects to ensure compliance with existing campus or UC-wide technology standards, or to work with the appropriate staff to extend those standards in a manner that fits with our strategic technology direction.  This committee also coordinates University-wide technical initiatives, such as bringing in a new Content Management System or Workflow solution.

Is every sponsor group required to fund their own project or is there a University/Campus budget to fund these projects? If there is a University/Campus budget, how much of a budget has been established in order that we may submit realistic proposals?

There are some central pool IT funds available. The priority for central funds is highest for projects that affect the entire campus however, in some cases, priorities that impact at a single department may also obtain funding.

Is there a way to see the detail of the proposals that are on the project list website?

Project status and schedule are available under the Reporting section.

Are all projects assigned a quantitative rating?

All significant projects that are expensive, complex, or higher risk, are rated based on a list of business and risk criteria. Smaller projects are only approved or disapproved.

Should I go through OIT before purchasing software?

Yes - OIT will help you get the best value for the investment,  oversee the security of any acquisition, and ensure that the vendor contract is written with standard guidelines and contract language to minimize risks.

How will OIT set priorities and timelines for projects and tasks in the offices included in the consolidation? What principles will be followed? Who will have input into that decision-making process and who will make the final decisions? What appeal process will exist if an administrative unit manager wants to challenge one of those decisions?

How will a department  have significant input to and influence on the priority-setting process and the determination of project/task due dates?

The current organizational structures of OIT and of the OIT Steering Committee have excluded the managers of the administrative offices targeted for consolidation. Why? Shouldn't these managers have input as a group into the decision-making process within OIT? Shouldn't they have significant representation on the OIT Steering Committee? 

Will OIT publish detailed service levels (in terms of response time to initial requests, number of projects completed on time, quality of service, etc.) that OIT guarantees to meet or exceed in most cases? That is, what standards of performance does OIT commit itself to meeting?

 

  • No labels