UVA Logo
IRM-010: University Information Technology Project Management

Date: 06/09/2006 Status: Final
Last Revised: 09/08/2021
Policy Type: University
Oversight Executive: Vice President and Chief Information Officer
Applies To:

Academic Division, the Medical Center, and the College at Wise.

Reason for Policy:

The University is committed to continuously improving the delivery of information technology (IT) solutions within budget, on schedule, within scope and in such a way as to best contribute to accomplishing the University’s strategic mission. This policy furthers that goal by establishing the common and consistent application of project management best practices in the management of IT projects. A uniform project management framework promotes consistency and better control of IT projects, thereby reducing risks and increasing project successes.

Definition of Terms in Statement:
  • IT Project:A project having as its primary purpose the creation of a unique information technology product or service.
  • Project:A temporary endeavor undertaken to create a unique product, service, or result (PMBOK Guide - Sixth Edition).
  • Project Management:The application of knowledge, skills, tools, and techniques to mitigate risk, control budget, and manage scope of tasks.
Policy Statement:

Institutional and unit information technology projects are managed in accordance with best practices promoted by the nationally recognized Project Management Institute (PMI), appropriately tailored to the specific circumstances of the University. For example, project managers possess professional credentials and/or an appropriate level of project management training or experience. Projects that engage leading IT consulting or software development firms to assist with project management may apply additional best practices provided by these firms.

Methods used for project auditing, such as Independent Verification and Validation (IV&V), are aligned with industry best practices, consultant expert guidelines, and known industry accepted standards such as Institute of Electrical and Electronics Engineers (IEEE) Standard 1012-2012 for System and Software Verification and Validation, International Standards Organization (ISO) 9001:2015 series, and Software Engineering Institute Capability Maturity Model (SEI-CMM). These methods are tailored to the Higher Education environment by internal departments and in coordination with consultants as warranted.

Exclusions: The scope of this policy does not extend to research projects, research initiatives, or instructional programs.

Information Technology Services has posted an overview of the University’s IT Project Management Framework, along with procedures, templates, and tools.

Compliance with Policy:
Failure to comply with the requirements of this policy may result in (1) disciplinary action up to and including termination or expulsion in accordance with relevant University policies; and (2) the University taking measures that may impact the school, department, or unit. The University also recognizes that there may be business needs or academic pursuits that require deviation from this policy or the use of different standards. Any deviation from this policy or the use of different standards requires coordination with and approval from the Contact Office to remain compliant with the requirements of this policy.

Questions about this policy should be directed to the Office of the Vice President & Chief Information Officer.

Policy Background:

The Commonwealth of Virginia Restructured Higher Education Financial and Administrative Operations Act of 2005 grants institutions additional authority over financial and administrative operations, on condition that certain commitments to the Commonwealth are met. The University of Virginia’s Management Agreement with the Commonwealth provides full delegated responsibility for management of the institution’s information technology project management and project auditing activities.

Major Category:
Information Resource Management
Next Scheduled Review:
Approved By, Date:
Board of Visitors, 06/09/2006
Revision History:
Updated 9/8/21; 5/27/14.