EagleNet
Banner
eVA
Canvas
EagleOne Deposits
Library
Email
EagleEye
Password Changes
Directory
Forms/Documents
PURPOSE
This standard defines the university’s requirements for the management and oversight of information technology projects. Information technology projects are managed utilizing industry “best practice” guiding principles defined within PMI’s PMBOK, or as required by VITA for state oversight purposes. These principles may be tailored, as determined by the project manager and approved as appropriate to the scope, risk and cost of a project.
STANDARD
The University categorizes and manages IT projects based on a combination of overall effort, comprised of the following considerations: cost, risk and complexity. The following diagram identifies and defines these categories, or effort level thresholds.
| Overall IT Project Effort |
Low (< $5,000) |
Medium ($5,000 – $250,000) |
High (> $250,000) |
| Methodology | Managed via departmental SDLC and tools | UMW IT Project Management Artifacts | VITA CPM, Prosight and corresponding artifacts |
| Contains elements of |
Low Risk, Complexity, Cost |
Medium Cost, Risk, Complexity | High Cost, Risk or Complexity |
| Artifacts | All “Low” effort software development projects are managed and tracked in the BART system.
Other types of low effort IT projects are tracked using appropriate departmental tools. |
*Project Charter
*Risk & Complexity Analysis *Budget Project Plan Project Status Reports *These artifacts are required. Others are optional, based upon project management needs |
*Project Charter
*Project Proposal Document *Risk & Complexity Analysis *Project Plan *Project Status Reports *Project Closure Report |
UMW uses the VITA (Virginia Information Technologies Agency) complexity model (http://www.vita.virginia.gov/uploadedFiles/Oversight/Projects/ComplexityModel.xls)
as a guideline in helping to determine overall risk and complexity when an effort is in question. (Note: this standard is scheduled to be updated in Q2 of 2011)
Per the referenced complexity model, there are occasions where projects would be categorized as having a “high” level of risk or complexity even though the overall project cost is not expected to exceed $250,000. In these instances, the full range of project artifacts, as documented for “High” effort level projects, would be required.
For software development projects, the University will review (on an annual basis, as requested by the Finance Department) any software development efforts exceeding $5,000 in cost, as these may be considered an asset and tracked/depreciated as such.
RELATED INFORMATION
VITA’s Commonwealth Project Management Standards & Templates http://www.vita.virginia.gov/oversight/projects/default.aspx?id=551
“Administrative System Project Request and Change Control Procedure” document
APPROVALS AND REVISIONS
Approved: March 1, 2011 by Vice President for Information Technologies & CIO
