Project Management Office (PMO)

Campus Projects

The campus projects list provides a current and comprehensive listing of all Technology Services projects. The list is intended to provide transparency and visibility for all project work, including the status and health of your project. You can view, search and filter and sort on any of the columns.

The campus project list provides the following benefits:

Serves as a repository for Technology Services project information
Helps Technology Services prioritize what needs to be done
Provides estimated project time-lines
Provides awareness of how many projects Technology Services has in progress

Project Definition

A project is defined as:

A unique endeavor (not repeated)
A distinct beginning and end
Defined by specific deliverables
Conducted by a temporary team that exists to complete the work
With a project manager responsible for its success
Defined by identifying its starting point, the goal/objectives sought, and the route between them

Project Sizing Criteria

The Technology Services Project Management Office offers an ongoing project intake process to capture, evaluate, and prioritize proposed ideas for projects, products, and services. In addition to the Annual Project Call, new project requests may be submitted throughout the year to be reviewed and prioritized.

Size Criteria for Submitting Projects PDF

	Small	Medium	Large	X-Large
Resource Hours	30 to 80 hours	81 to 160 hours	161 to 320 hours	>320 hours
Project Team Size (FTE)	1-2 people	3-6 people	6+ people	10+ people
Complexity	Problem is easily understood, solution is achievable	Problem/solution is understood	Problem is not understood/solution is unclear	Problem and solution are difficult to define and achieve
	Small modifications	More modifications to existing functionality	Moderate architectural or infrastructure changes	Cross-divisional integration and collaboration
	No new technologies	May involved new technologies	Cross-divisional integration and collaboration	Major architectural or infrastructure changes
	Similar work done in past	Precedents exist for work	Involves new technologies	No precedents exist for work
			No precedents exist for work	Team has no experience
				New technologies
Strategic Imprtance	Internal interest only	Direct impact to low-medium priority initiatives	Direct impact to medium to high priority initiatives	Campus-wide impact and relates to key strategic initiatives
Level of Change	Impact in single area of one division/college	Impact single area of number of areas	Impact to number of areas	Campus-wide impact
		Two or more divisions/colleges	Across all divisions/colleges	Across all divisions/colleges
Dependencies & Inter-related Projects	No major dependencies	Some low-risk dependencies	Some high-risk dependencies	Major high-risk dependencies

A factor that may increase the sizing of a project is the complexity of the project. For example:

Technical Complexity: This includes all technical aspects of the project, such as:

Number of technologies involved
Familiarity of team with technologies
Bleeding edge or well established technology
Number of technical interfaces
Number of other technical projects in progress

Management Complexity: This includes all business and organizational aspects of the project, such as:

Project staffing and management (team composition, size, management hierarchy etc.)
Number of parties involved (external vendors, internal departments etc.)
Change-related and Cultural issues
Stability and complexity of requirements
Political issues
Time / cost issues etc.