Lifecycle of an IT Project
Learn more about Information Technology Governance and how decisions are made that impact which projects are chosen for development.
IT Project requests can be generated by all seven divisions of the university and come from many sources such as ideas from staff, meetings with departments across campus, and strategic objectives supported by divisional leadership.
For a more in-depth and continually updated version of this site, .
Step 1. Idea generation and collection
The IT Services business relationship management staff members meet monthly with the divisional representatives to gather their project requests and then work with the divisions to build a business case for each project request.
At this point, IT Business Analysts create a Project Request to track the life of that particular idea. This helps get the request in front of the appropriate teams and groups.
Step 2. Value Engineering
When the list of projects desired by the divisions and the business case benefits have been developed for these requests, value engineering reviews the requests. This group is composed of IT Services staff members who meet weekly to determine the effort, team assignment, and best path to complete the requested work.
Step 3. Change and Continuous Improvement Committee (CCIC)
After Value Engineering determines the timeline and team best suited for the work, the Change and Continuous Improvement Committee reviews and (hopefully) approves the project requests.
For more information about CCIC, .
Step 4. Project Pre-Planning and Execution
Once the value engineering work is completed and CCIC approves, the requests then are put on hold until close to the time slotted for the project to begin. At this time, a pre-planning session is held to determine who, what, how, and when the new solution can be built and tested.
And finally...
The project is assigned a more accurate timeline, and work begins!