Professional Documents
Culture Documents
UCLA IT GOVERNANCE
TABLE OF CONTENTS 1 IT GOVERNANCE OVERVIEW ............................................................................................... 1 1.1 1.2 1.3 1.4 2 3 4 5 6 STEP 1- PROJECT IDENTIFICATION.......................................................................................... 1 STEP 2 - PROJECT CLASSIFICATION ........................................................................................ 2 STEP 3 IT PROJECT PORTFOLIO MANAGEMENT ..................................................................... 3 STEPS 4-5 IT PROJECT GOVERNANCE CONFIGURATION ........................................................ 3
PROJECT CLASSIFICATION WORKSHEET ....................................................................... 4 GOVERNANCE PROCESS TRIGGERS .................................................................................. 7 IT GOVERNANCE ARRANGEMENTS MATRIX.................................................................. 8 IT GOVERNANCE PROCESS FRAMEWORK ...................................................................... 9 IT GOVERNANCE PROCESS FLOW DIAGRAM ............................................................... 10
IP1133-PDG-NNA V1.2
04/24/06
PAGE i
UCLA IT GOVERNANCE
REVISION HISTORY 03/09/2006 03/23/2006 04/24/2006 Version 1.0 Version 1.1 Version 1.2 First Draft Second Draft Third Draft
1 IT GOVERNANCE OVERVIEW
This document provides an overview of the IT Project Governance process at UCLA. IT Governance comprises of the leadership, organizational structures, and processes to ensure that UCLAs IT capabilities continue to sustain and extend its strategies and objectives. The UCLA IT Governance structure specifies the decision rights and accountability framework to encourage desirable behavior in using IT to further the Universitys mission. This desirable behavior is characterized by: Integration of IT strategic planning with campus strategic planning Appropriate accountability for IT initiatives Transparency - IT plans and investments are made visible beyond their origination point (subject to the application of some defined thresholds). Adoption of a broad campus-wide view A willingness to share and use IT best practices across the UCLA community Entrepreneurial spirit and creativity in applying IT Participants understanding the value of the governance process and actively participating in it
The overall IT Project governance process flow is shown in Figure 1. A larger version of this diagram may be found on page 10 of this guide. The overall process is broken down in six major steps and these are described in broad terms in this section. The remaining sections of this document provide more specific guidance on certain key aspects of the governance process.
PAGE 1
OIT A major source of information for this step is the identification of such projects through the annual campus strategic planning process. In addition, some projects may arise on an ad hoc basis in response to emergent needs. It is neither necessary nor practical for all IT Projects to pass through the entire IT Governance Process described in this guide. The intent of the governance process is to apply good judgment and to focus attention and resources only on those projects that truly require it and that have the greatest impact on the campus. The primary means of making this judgment is human interaction. Thus this process step requires dialog and discussion between OIT, ITMG and other stakeholders to make an initial assessment on what projects to pass through the process and what projects to filter out. Key questions asked at this stage are: Does project need outside funding? How is project aligned with strategic direction? What is the project motivation (is there a legal mandate?) What is the end user impact of the project? Is there a reason to fast track the project? Will the project be controversial?
Based on this initial assessment some projects will move on through the process to Step 2 for further governance consideration, some will be deemed to not require any further IT Governance, and some will be fast tracked through the process. It is important to note that this step does not constitute the official approval of a project, it simply decides if a project should move through a more rigorous governance process. Project approvals remain with the Executive Sponsors of an IT project.
These questions should be answered in a project classification meeting between the Project Manager, the Project Sponsor and an OIT director (with other participants as required). As a guideline this meeting should require no more than one hour. Although the worksheet uses a simple scoring mechanism to encourage discussion, the classification process should not be an empirical exercise. The worksheet is intended as an aid and guide for the project classification discussion. Ultimately the combined knowledge and experience of the participants should determine the appropriate Project Class that makes sense. The resultant project classification is then used to steer the project through the governance process. Class 1 Projects are considered to be low risk and do not need to continue any further in the governance process. They can therefore proceed normally. Class 2-5 Projects move on to Step 3.
IP1133-PDG-NNA DRAFT
4/24/2006
PAGE 3
OIT
UCLA IT GOVERNANCE IT SOLUTION COMPLEXITY 5. Technology/Technique/Process What is the knowledge, skills and expertise of the project team in employing the chosen technologies, techniques, methods and processes to be used on the project? 6. Product Maturity (If purchased) If software packages or commercial software products are to be included the solution, what is the general maturity of these products and their usage within other institutions of higher education? 7. Solution Complexity What is the level of technical complexity of the solution? 8. System Interface Profile What is the complexity of the required system interfaces for the solution in terms of the number software interfaces that need to be developed? 9. IT Architectural Impact What is the architectural impact of the solution in terms of how it will fit with IT Architectural standards (data, applications and technology), and coexist and integrate with other applications? 10. Maintainability What is the degree of complexity of maintaining the application in terms of the level of technical skills required and the specific availability of those skills to UCLA? DEPLOYMENT COMPLEXITY 11. Process Impact What is the implementation scope, boundaries and expected degree of change on academic or administrative processes? 12. End User scope of impact What is the implementation impact in terms of the range and types of campus personnel affected? 13. Project Profile What is the degree of acceptance and readiness level of the affected user constituency for the solution? 14. Project Motivation To what degree is the project being driven by an external mandate from the Federal, State or UCOP level? Project Budget The total estimated development costs for the project (hardware, software, facilities, and people). Ongoing Cost The estimated average annual maintenance cost for the application. This should include regular hardware and software upgrades and maintenance, hosting fees, and vendor support.
IP1133-PDG-NNA DRAFT
4/24/2006
PAGE 5
OIT Project Class The assigned project class (High 5 to Low 1) based on overall scoring and the group discussion.
UCLA IT GOVERNANCE
IP1133-PDG-NNA DRAFT
4/24/2006
PAGE 7
OIT
Descriptions of the Governance Entities may be found on the OIT website (http://www.oit.ucla.edu/it_governance.htm).
This framework is based on the work of Peter Weill & Jeanne W. Ross, IT Governance. Harvard Business School Press, 2004.
UCLA IT GOVERNANCE
IP1133-PDG-NNA DRAFT
4/24/2006
PAGE 9
OIT
IP1133-PDG-NNA DRAFT
4/24/2006
PAGE 1