University IT Governance and Portfolio Management

The University IT governance structure is comprised of seven subcommittees and one steering committee. University and Healthcare projects have separate IT governance committees and processes.

These committees approve project requests for initiatives that anticipate work that is a new or significant upgrade to a customer-facing product or service utilized as an enterprise offering or requires an integration with an enterprise service or data source. 

IT Steering Committee (ITSC)

The ITSC creates and sustains a set of processes for IT governance and prioritization at Emory University that are timely, transparent, and clearly aligned with the university's missions. ITSC is charged with:

  • Creating and maintaining a subcommittee structure that represents the functional and technology interests of the institution.
  • Implementing strategic decision-making processes that are consistent with best practices in higher education and across other industries.
  • Reviewing and understanding the financial context for IT services and forwarding recommendations for project funding levels to Emory's Ways and Means Committee.
  • Reviewing and re-affirming prioritization decisions of the IT governance subcommittees.
  • Evaluating proposals that do not fit within the scope of the functional and technology subcommittees.
  • Working with the VP of Information Technology and CIO to communicate the status of IT initiatives to the University community.

University Subcommittees

The primary purpose of each subcommittee is to evaluate IT project requests that fall within their respective domains, approving each project's placement within strategic priorities and existing resource commitments. Membership is intentionally broad-based across the university and healthcare communities. Additional subcommittee responsibilities:

  • Understanding the governance and approval processes.
  • Understanding the financial context for IT prioritization.
  • Evaluating project requests that fit within the subcommittees' domain.
  • Evaluating resource availability and distribution.
  • Evaluating strategic importance and utility of each proposed project with a focus on maintaining architecture and security standards across campus.
  • Act as bi-directional communication channels with central IT divisions and a communication channel with the larger campus community.

Frequency

Specific meeting time, frequency and location decisions are decided by each subcommittee. Most subcommittees meet monthly for one hour.

Terms of Service

Chairs: 3 years
Members: 2 years