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
| Criteria | Small | Medium | Large |
|---|---|---|---|
| Resource Hours | 40 to 160 hours | 161 to 320 hours | More than 320 hours |
|
Project Team Size (FTE) |
1-3 people | 4-8 people | 8+ people |
|
Complexity |
Problem/solution is relatively simple/easily understood | Problem/solution is more complex, needs discovery | Problem/solution is very complex, needs lengthy discovery/research |
|
|
Technology ready | May involve new technologies | May involve new technologies |
|
|
Small modifications | Significant modifications to current architecture | Major modifications and infrastructure/architecture change |
|
|
Resources are experienced in these mods | Resources may not have experience; need additional research | Resources need to do research/ get training |
|
|
May need outside expertise | May need outside expertise | |
|
Project Stakeholders and Visibility |
Single area or department, not visible to the larger audience | Impact to several areas, entire division or population (all students or all staff). Large number of stakeholders | Impact to more than one division/population, or a campus-wide impact |
|
Level of Change/Change Management Needed |
No change management needed (Technology Services or functional team) | Change management may be needed for a number of areas or entire division (Technology Services contributes) | Campus-wide change management campaign (Technology Services fully involved in the Change management campaign) |
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.