UTS PROJECT MANAGEMENT PROCESS

The purpose of the IT Project Management Methodology is to define the steps required to execute an IT project from conception to closure, integrating the project management and engineering activities, involving appropriate functions at the appropriate points, defining deliverables, and providing management oversight. The IT Project Management Methodology is consistent with the Project Management Institute’s Project Management Book of Knowledge (PMI PMBOK). The PMBOK is an industry standard that is used as the basic framework for project management procedures and activities at University Technology Services.

At the end of each stage, the Project Review Team (PRT) and/or other review teams review the outputs of the stages against a pre-defined checklist for that stage. The purpose of these reviews is to ensure that the project “stays on track”, that the appropriate resources are available to execute the next stage, that stage deliverables are met, and that the entire portfolio of projects is in line with the strategy. As such, the PRT is tasked with redirecting projects that are off-track, that no longer meet the strategic objectives or can’t be resourced at the required level.

The stages of the IT Project Management Methodology are:

IT PM Methodology Stage	Stage Description	Templates	Date
Initiation	Every project starts with an idea and this stage expands the idea into the project's business objectives. The objectives are conceptualized, justified, authorized, and funded.	Charter 12/07/2006 Initiation Stage Review Checklist 05/09/2007 Team Directory 05/12/2008 Risk Assessment 11/22/2006
Scoping	The scope sets guidelines to the project's bounds and identifies requirements and initial high level approaches to meet the project's objectives. At this time the closure criteria of the project is defined to assist in ending the project.	Requirements Checklist 04/20/2007 Scope 12/07/2006 Scoping Stage Review 05/12/2008
	Project Plan and components:	Project Plan 05/09/2007 Team Directory 05/12/2008 Communications Plan 05/15/2007 Risk Assessment 11/22/2006 Financial Information 02/27/2007 Lessons Learned 07/13/2006 Issues Log 04/13/2006 Roles and Responsibilities 11/19/2007 Quality Plan 05/14/2008
Design Planning	Design is separated into two stages when the project is procuring the solution or major components, and the design cannot be completed until a vendor/product is selected. In this case, a Vendor Impact Assessment is required (by Architecture Oversight Committee), and a Design Planning Stage review is conducted. Otherwise, the design is developed and reviewed in the Design Stage. The design planning stage is the beginning of design. Design is the how and when customer requirements will be achieved. It identifies what currently exists today and a proposal of the future state. The infrastructure is defined and special hardware and software needed is identified. Design planning does not build the detailed design, but it provides the platform for the detailed design to be developed.	Design Specification 03/19/2007 Design Planning Stage Review Checklist 04/20/2007
Design	This stage builds the detail of how the customer requirements will be met. When this stage is complete, a team will have all information needed to develop or enhance the process/application/or purchase the product to meet the customer's need. Design Planning and Design both occur in the Design Stage unless the project is procuring the solution or major components.	Design Specification 03/19/2007 Design Review Checklist 12/08/2006 Design Stage Review Checklist 04/20/2007
Development & Testing	In this stage, the process or system is being developed and tested in a test environment adhering to the detailed design specifications. The testing is reviewed in detail to determine development success. It is possible that after this stage, a team may revert back to design. This is the iterative approach.	Test Plan & Report 04/13/2006 Test Problem Entry Form 04/13/2006 Quality & Pre-Production Review Checklist 12/08/2006 Development Test Stage Review Checklist 05/15/2007 Implementation Plan 04/13/2006
Implementation	The customer uses the system to meet their business need. Implementation may be in phases in the form of a pilot or phased implementation, but the customers are using the production environment.	Implementation Plan 04/13/2006 Implementation and Closure Stage Review Checklist 05/09/2007 Transition to Operations and Support Review Checklist 05/15/2007
Closure	During closure the deliverables are formally accepted by the customer. An assessment is performed to document lessons learned to improve future projects. Project knowledge is also transferred to the appropriate people.	Lessons Learned 07/13/2006 Implementation and Closure Stage Review Checklist 12/08/2006

[BACK TO TOP]