2014 Guide to IT Governance



Similar documents
IT Governance Project Ranking Guidelines Updated April 24, 2014

IT GOVERNANCE AT CARLETON UNIVERSITY

Final. North Carolina Procurement Transformation. Governance Model March 11, 2011

U.S. Department of Education. Office of the Chief Information Officer

State of Minnesota IT Governance Framework

The Integration of Strategic Planning and Portfolio Management

IT Governance. Brandeis University Library & Technology Services. Committees... 2 One steering committee and three subcommittees are created.

Project Management Office Charter

University of Wisconsin Platteville IT Governance Model Final Report Executive Summary

IT Governance Framework Summary

Appendix A - Charter of the Academic and Student Affairs Committee

ITS Project Management

Strategic Planning Procedure Manual

Associate Vice Chancellor for IT and Chief Information Officer Larry Conrad April 28, 2014

Performance Management. Date: November 2012

Shared Governance Principles and Operational Plan Andrews University

University of Rhode Island IT Governance

A New Framework for Administrative Applications Governance

CALIFORNIA GIS COUNCIL CHARTER

OFFICE OF THE CIO. PROCEDURE Informational VERSION: 1.0

The College Strategic Process

Enterprise Project Management Initiative

Project Management Office (PMO) Charter

CHARTER. Interagency Information Systems Working Group. Timber Regulation and Forest Restoration Program June 23, 2015

MIRACOSTA COMMUNITY COLLEGE DISTRICT STRATEGIC PLAN

The Fast Track Project Glossary is organized into four sections for ease of use:

Portfolio Management Professional (PfMP)SM. Examination Content Outline

The University of Tennessee IT Governance Process (Restructured)

MEMORANDUM FOR CHIEF FINANCIAL OFFICERS. Update on the Financial Management Line of Business and the Financial Systems Integration Office

PROJECT MANAGEMENT PLAN <PROJECT NAME>

Department of Administration Portfolio Management System 1.3 June 30, 2010

Project Management Methodology

Strategic Planning A PRACTICAL GUIDE FOR UNITS AND DEPARTMENTS

ILO. Information Technology Governance Committee (ITGC) Charter

Sound Transit Internal Audit Report - No

Office of the Auditor General AUDIT OF IT GOVERNANCE. Tabled at Audit Committee March 12, 2015

SYSTEM OF HIGHER EDUCATION PROCEDURES AND GUIDELINES MANUAL CHAPTER 17 COMMUNITY COLLEGE INSTITUTIONAL ADVISORY COUNCILS

Implementing a Data Governance Initiative

COMMUNICATIONS MANAGEMENT PLAN <PROJECT NAME>

Strategic Plan San Luis Obispo County Community College District

Strategic Planning Process Map

1. CALL TO ORDER/ROLL CALL John Zoglin, Chair 4:00 4:01. John Zoglin, Chair 4:01 4:02 2. POTENTIAL CONFLICT OF INTEREST DISCLOSURES

IT Governance. IT Investment Proposal Review & Submission Workshop. Agenda. University of Manitoba IT Governance Proposal Workshop. March & April 2015

Information Technology (IT) Governance

The Standard for Portfolio Management. Paul E. Shaltry, PMP Deputy PM PPMS ( ) BNS02

IT Governance Overview

Information Technology Project Oversight Framework

Data Management Standards

The Advantages of a Technology Governance

Business Plan for the. The Geospatial Platform. September 20, 2012 REDACTED

MNLARS Project Audit Checklist

Exhibit B. Clark County Desert Conservation Program Community Advisory Committee CHARTER

Advisory Council member responsibilities include:

Central Project Office: Charter

PROGRAM QUALITY ASSURANCE PROCESS

MINNESOTA STATE POLICY

IT Governance: framework and case study. 22 September 2010

Section 4 MANAGEMENT CONTROLS AND PROCESSES. Section 4

TDWI strives to provide course books that are content-rich and that serve as useful reference documents after a class has ended.

LMI Aerospace PROJECT MANAGEMENT PLAN ACCESS REQUEST PROCESS IMPROVEMENT FEBRUARY 7, 2012

Released December 18 th, 2007

IT Governance Action Team Report & Recommendations

Graduate Studies Office

James Madison University. Best Practices for Online Programs

Program Management Professional (PgMP) Examination Content Outline

Audit of Project Management Governance. Audit Report

Board of Trustees IT Subcommittee Meeting. November 3, :00-2:50 PM Harper Center 3023

U.S. Department of the Treasury. Treasury IT Performance Measures Guide

Section 6. Governance & Investment Roadmap. Executive Governance

Colorado Integrated Criminal Justice Information System (CICJIS) Program CHARTER and BYLAWS

Information Technology Governance: Key Success Factors

COMPENSATION AND CORPORATE GOVERNANCE COMMITTEE CHARTER

Guidance Note: Corporate Governance - Board of Directors. March Ce document est aussi disponible en français.

ClOP CHAPTER Departmental Information Technology Governance Policy TABLE OF CONTENTS. Section 39.1

Governance Guidelines

Financial Services FINANCIAL SERVICES UTILITIES 57 FINANCIAL SERVICES AND UTILITIES BUSINESS PLAN. CR_2215 Attachment 1

Information Technology Governance Overview and Charter

IT Governance Framework. Western Illinois University. September 2013

Superintendent Effectiveness Rubric*

POLICY AND PROCEDURES OFFICE OF STRATEGIC PROGRAMS. CDER Informatics Governance Process. Table of Contents

R U N D O. The ECU Technology Governance Framework A brief guide

Strategic Plan for the Enterprise Portfolio Project Management Office Governors Office of Information Technology... Ron Huston Director

POPHEALTH PROJECT GOVERNANCE

IT UNIFICATION Vision, Impact & Strategy. May 2015

Data Integration Initiative Semi Annual Report April State of North Carolina Office of the State Controller

OPERATIONAL IT COMMITTEE MEETING AGENDA Wednesday, September 26, :00 p.m., FAC 228D

Value to the Mission. FEA Practice Guidance. Federal Enterprise Architecture Program Management Office, OMB

IT PROJECT GOVERNANCE GUIDE

Final Report. Audit of the Project Management Framework. December 2014

Joint Operations Steering Committee Charter

Strategic Plan

Renewing our Commitment to Undergraduate Education

Performance Audit Concurrent Review: ERP Pre-Solicitation

2011 Outcomes Assessment Accreditation Handbook

Introduction to Enterprise Risk Management at UVM DRAFT

Office of the Chief Information Officer

STATE OF NORTH CAROLINA

Enterprise Business Systems Assessment. Summer 2011

5 FAM 670 INFORMATION TECHNOLOGY (IT) PERFORMANCE MEASURES FOR PROJECT MANAGEMENT

Transcription:

2014 Guide to IT Governance What is IT Governance? IT governance provides the conceptual framework, structures, processes, resources and information aligned to university strategies and objectives, enabling us to take full advantage of IT, maximizing benefits, capitalizing on opportunities and gaining competitive advantage. It also provides strategic leadership, establishes campus-wide IT priorities and policies, and is accountable and transparent to the University community. Most importantly, it is part and parcel of university governance, strategy, decision making and planning. The IT Governance structure as a whole is responsible for: Integrating institutional strategic planning with IT strategic planning. Establishing campus-wide priorities for IT initiatives that are aligned with institutional goals and priorities. Ensuring consistent communication and engagement with campus community on project investments. Providing structures and processes that influence the direction and outcomes of technology services, policies and solutions. Promoting transparency, accountability, dialogue and communication about IT investments. Establishing a project investment fund to enable the execution of investments. Good Governance Good governance is about the processes for making and implementing decisions; it is about making the right decisions and about following the best possible process for making these decisions. Good governance is about effectiveness, completeness and accountability. Good governance ensures that the institution is getting good value from IT and that the right investments are being made to enable the organization to achieve success. We can simplify this by thinking about the outcome and asking four key questions: Are we doing the right things? Are we getting the benefits? Are we doing them the right way? Are we getting them done well? 1 1 Based on the Four Ares as described by John Thorp in his book The Information Paradox, written jointly with Fujitsu, first published in 1998 and revised in 2003

To enable good governance, there are three components that constitute IT Governance: Structure o The structure component pertains to the activities, the way those activities support the goals of the university, and the people who manage those activities. o Structure components include mission, mandate, terms of reference, roles, conflictresolution mechanisms, accountability, transparency, and constituent groups. Process o The process component defines decision-making rights as well as paths and policies that are used to measure and control the way decisions are made and executed. o Process components include alignment, commitment, motivation, leadership and meaningful participation. Communication o The communication component defines how the results of processes and decisions will be monitored, measured and communicated. o Communication components include information sharing, meetings, stakeholder engagement and reporting Governance Design In 2012 the approach to renewing IT governance started with a set of objectives that identified what we are trying to achieve and how we are going to achieve this, summarized as: Make smart choices Effective engagement & analysis Align within institutional vision Futures-ready Make them quickly Small, focus decision body Rely on existing position authority Make them stick Decisions and actions viewed as legitimate Make it happen Resources identified & allocated Clear responsibilities & accountabilities To ensure a successful outcome, the following set of objectives were established as a basis for change: Ensure that all committees have clear charters including purpose, membership, communication, frequency, etc. (focusing on the right things). Ensure that all committees have clear reporting linkages and decision paths. Encourage the safe dialogue and debate on initiatives and sequencing/prioritization Refine processes to ensure initiatives are proposed, reviewed and approved in a timely manner. Ensure the process is transparent, responsive, inclusive and effective. Ensure campus/stakeholder engagement occurs at the right level with the right stakeholders. Governance Structure The IT Governance structure (Appendix A) is designed to model the institutional hierarchy and governance structure. From a strategic alignment perspective, governance is designed to align with

how institutional decisions are made. This is facilitated through the committee structures and linkages to institutional committees and governing committees such as Executive Council, Integrated Planning, Dean s Council and President s Advisory Council. Figure 1, shows a simplified IT Governance structure with a focus on the IT Executive Committee and the Priority and Governance Review Council. Board of Governors Senate Executive Council Strategic Plan Leadership Community IT Executive Committee Integrated Planning PAC Deans Council Priority and Governance Review Council University Community / Stakeholders Governance Committees Figure 1 The IT Executive Committee (ITEC) is responsible for the oversight and delivery of all IT Governance project investment decisions, including the overall strategic direction of institutional IT projects. The purpose of ITEC is to ensure the effective and efficient use of technology in enabling the university to achieve its strategy and goals within acceptable levels of risk. ITEC is tasked with and accountable for ensuring that technology services deliver value and that expected benefits from new investments are fully realized. The Priority and Governance Review Council (PGRC) is responsible for reviewing, evaluating and recommending IT Governance project investments to the IT Executive Council (ITEC), and to ensure the effectiveness of IT Governance. PGRC reviews project investments for alignment with institutional goals, evaluates the benefits and risks, and makes recommendations to ITEC for investments. The committee also creates and sustains a set of processes for IT governance and prioritization that are timely, transparent, and clearly aligned with the university's missions. Figure 2 shows all of the governance committees. The committees are structured into portfolios that represent academic, administrative, research and information technology. The portfolio approach allows for committees and sub-committees to discuss initiatives, challenges and priorities in context,

and avoid any confusion about purpose or alignment. There are four primary committees: Academic and Student Services Committee (ASSC), Administrative Systems Operations Committee (ASOC), Research Computing Advisory Committee (RCAC) and the Information Technology Advisory Committee (ITAC). IT Executive Committee Priority and Governance Review Council Academic & Student Services Committee (ASSC) Administrative Systems Operations Committee (ASOC) Research Computing Advisory Committee (RCAC) Information & Technology Advisory Committee (ITAC) Student Academic Systems Finance Westgrid Campus Systems Council Teaching, Learning, Technology Academic & Student Services Administrative Systems Human Resources Research Administration Facilities *There are a number of linkages, inter-dependencies and crossmemberships between committee and sub-committees. These are not represented on this map to enhance readability. Identity Management Project Review Information Security & Privacy Additional Sub-Committees as Required Figure 2 The purpose of the Academic & Student Services Committee (ASSC) is to recommend and prioritize academic and student systems and technology development projects (new and enhancements) that align with the operational and strategic needs of the institution. The systems governed by this committee include student administration systems (e.g., records, admissions, registration), student support administration systems (e.g., advising, services for students with a disability, student health services), and educational technology (learning management systems, test scoring, course experience survey). All plans, projects and priorities applicable to the student and academic information systems and supports listed above fall within the mandate of ASSC. The purpose of the Administrative Systems Operations Committee (ASOC) is to recommend and prioritize administrative systems projects (new and enhancements) that align with the operational and strategic needs of the institution. The systems governed by this committee include finance, budget, human resources, pensions, facilities management, development/advancement, research administration and ancillary applications. Student administration and related systems are the responsibility of the Academic

and Student Services Committee (ASSC). All plans, projects and priorities applicable to the administrative information systems listed above fall within the mandate of ASOC. The purpose of the Research Computing Advisory Committee (RCAC) is to recommend and prioritize projects (new and enhancements) in support of the research computing environment across the institution. The users of research computing have widely varied requirements; from those who use computing facilities as tools incidental to their research, to those for whom computing is central to the gathering and analysis of data, to those for whom research in computing is the primary focus of their work. Some requirements are best met at the institutional level while others require localized facilities and support. Many researchers also require access to resources further afield including access to cloud computing, remote data bases, collaborative environments, etc. The Information & Technology Advisory Committee (ITAC) will provide a forum for discussing enterprise information and technology and service changes that may have major campus impact and/or significant cost for the university. The committee will advise on reducing duplication of services and realizing economies of scale, improving quality of IT service, adopting best practices, and complying with audit requirements. For each of the committees, see the committee terms of reference for more information. Sub-committees & working Groups Sub-committees are ongoing groups who are responsible for issues and decisions in certain areas of responsibility or interest of the university. Working groups are defined as time-bound groups assigned specific problems to solve or tasks to accomplish. IT governance committees can form working groups as needed. Working groups meet for a set timeframe to accomplish specific objectives related to resolving an issue or implementing an IT strategy; they are not considered standing or ongoing governing bodies. Working group membership can consist of IT governance committee members or any qualified personnel identified by IT governance committee members. For each of the sub-committees, see the sub-committee terms of reference for more information. Governance Membership Committee membership is designed to be representative of the campus community. Generally, members are selected to represent academic, research and administrative units of varying size. Specific details of the membership designated for each committee can be found in each of the committee terms of reference. Members are recommended to the governance Chairs by governance members, by members of the campus community, or through a research process to identify potential members who represent a specific unit or group that is not currently represented in the governance membership. If specific expertise is desired or required for a particular project of governance, experts are identified and recommended to the governance Chairs. After recommendations are considered, committee members are finalized by the committee, its parent committee and/or the Priority and Governance Review Council.

Agenda Setting Members of each committee propose agenda items to be discussed in their respective committees. Agenda items can also be suggested by anyone in the university community (non-committee members) by directly contacting a committee Chair or the CIO's office. Agenda items for each committee are vetted through that committee's Chair. The committee Chairs and CIO meet regularly to coordinate the timing of committee efforts and ensure proper communication, inclusion and prioritization. Project Funding The majority of projects that are presented to IT Governance will require a source of funding. The following are several sources that are available to fund projects: Local funding is one-time funding that is provided completely from one campus department and/or unit. Shared funding is one-time funding that is provided through the cooperation and coordination of multiple departments and/or units. Hybrid funding is one-time funding that is provided by both campus departments and/or units, and by IT Governance. IT Governance funding is one-time funding that is provided only by IT Governance to fully fund a project. Where funding is provided by IT Governance, this funding is only available to cover one-time project costs. All ongoing or operating costs must be alternatively sourced and be identified in advance in order to approve project proposals. Governance Process In IT Governance, the project proposal is the starting point of turning an idea into a project. Ideas can be brought forth by anyone to a committee chair and/or the CIO, and formed into a project proposal. The purpose of the project proposal is to describe the idea, strategic alignment, compliance requirements, institutional impact and value proposition of the idea. Project proposals are developed using the project proposal template and with the assistance of a Project Manager and/or the Project Management Office. Once the proposal is complete, it is submitted to the appropriate committee and added to the IT Governance Committee Project Registry. The receiving committee will review and discuss the proposals for accuracy, completeness and alignment. The committee will then either request changes or accept the proposal. Proposals that have a limited impact, are normally less than $20,000 dollars or require limited resources can proceed to planning and execution. Proposals that exceed these thresholds must be ranked by the committee using the project ranking guidelines and submitted to its parent governance committee for review, acceptance and ranking. Once the sub-committees and parent committees have reviewed and ranked the proposals, they are submitted to the Priority and Governance Review Committee (PGRC). This committee will then complete a cross-committee project review to ensure accuracy, completeness, institutional alignment and a collective understanding of the projects. Once reviewed, the committee can then make a recommendation to the IT Executive Council (ITEC) to support the project proposal. Alternatively, if

PGRC identities that additional information or changes are required to a project proposal, the feedback will be provided to the committees and project sponsor. ITEC will review the recommendations and provide a memo to the IT Governance committees containing decisions of support, funding and any additional requirements. It is important to note that ITEC will only consider funding requests that are one-time and are normally greater than $20,000; ongoing funding will not be considered. All projects that are granted approval to plan must be assigned a Project Manager and use the Project Management Office (PMO) to coordinate the project process including monitoring and reporting of project to governance committees. Finally, prior to receiving approval to execute a project plan must be developed and submitted to the Project Review Committee (PRC) who will perform a technical review. Project Ranking The purpose of project ranking is to provide guidance to IT Governance Committees on how to collectively decide on the importance (rank) and sequence of projects to submit for funding and approval. The Project Ranking Guidelines and worksheet provides committee members with proposal evaluation criteria, enabling them to rank one or more proposals within the set of active, waiting and proposed projects. If there are existing project proposals that have been previously ranked but the project have not started, then committee members will be asked to re-rank those projects with the new ones. Once each committee member reviews and ranks project proposals, the aggregated results of project rankings by committee members will be used in committee discussions to allow the committee to reach a consensus on the project proposal rankings. The committee ranking of proposals will result in the order for which projects will be sequenced and executed once approved by ITEC.

Appendix A IT Governance Project Documents Document Project Management Methodology v5 Updated January 7, 2014 Project Proposal Template Updated April 1, 2014 Project Plan Template Updated March 26, 2014 Project Closeout Template Updated March 18, 2014 ITG Project Ranking Guidelines Updated April 24, 2014 ITG Project Ranking Worksheet Updated April 24, 2014 ITG Project Summary Template Updated April 2, 2014 ITG Project Update Template (.doc) Updated March 12, 2014 ITG Project Update Template (.xls) Updated March 12, 2014 ITG Committee Terms of Reference Template Updated March 12, 2014 Document Object (double-click to open) UVic IT PM Methodology 5.pdf UVic Project Proposal Template.dotx UVic Project Plan Template.dotx UVic Project Closeout Template.dotx ITG - Project Ranking Guidelines.docx ITG - Project Ranking Worksheet.xlsx ITG - DRAFT Project Summary Template.xlsx IT Governance Project Update Template.docx IT Governance Project Update Template.xlsx Terms of Reference Template.docx