About OIT
Project Portfolio - Project Process
OIT Project Definition
- An OIT Project represents a new service, expanded service, college-wide implementation, or terminated service.
- An OIT Project will require the use of multi-team personnel (CSIS, Applications and Special Projects, Instructional Services).
- An OIT Project requiring new budget consideration must be submitted and approved in time to meet COE budget or Student Tech Fee budget development.
- An OIT Project will be developed using the OIT planning template and monitored using MS Project 2003.
- An OIT Project will have representatives performing the roles identified in the OIT Project Model: Project Lead, Project Manager, Team Member, Communications Manager, Professional Development Manager, Security and Quality Control Manager.
- OIT Project documentation should be kept in the shared drive in the Project folder. Individual project folders can be placed inside this main project folder.
- Any request from the Dean or an Assoc. Dean must come through the Exec. Director.
OIT Team Project Definition
- Team Projects require no or extremely limited multi-team personnel.
- Team Projects are included in the routine management or responsibilities of the team.
- Team Projects should be planned using appropriate tools.
- Team Projects will be led by the team lead of the unit.
- Team Projects are the responsibility of the team lead for results, customer satisfaction, and resources allocation based on yearly, approved OIT budget or student tech fee.
- It is recommended but not required that team leads use MS Project 2003 to monitor work.
- Team leaders must update the OIT Leadership Team during weekly meetings concerning Team Projects.
- A Team Project can be identified as one that should move to OIT Project status by the OIT Exec. Director or OIT Leadership Team.
Project Phases
| Planning | Define project objectives and parameters | Determine major activities Estimate effort and duration Assess resource needs | Skills and/or Tools Work breakdown structure Skills inventory |
| Build-up | Assemble team Review plan with team |
Develop project schedule Assign people and resources to tasks Motivate team |
Skills and/or Tools Behavioral styles and assessment Team building Gantt/PERT/CPM |
| Main Implementation |
Control Changes Monitor and report progress |
Review and approve completed work Deliver project products |
Skills and/or Tools Conflict management Communication |
| Phase-Out | Develop plan for reallocation of team | Evaluate performance Close project |
Skills and/or Tools Debrief "lessons learned" Follow - up plan if required Continuous improvement recommendations for process |
August 2006
Role descriptions of project team members
|
|
|
 |