NEOMED Technology Advisory Council

Overview

The NEOMED Technology Advisory Council (TAC) provides a framework and process for selecting new projects which best support the campus’ strategic interests and directions and provide it the most value. The intended results of the Project Prioritization process are to:

  1. Build consensus on the most important information technology projects
  2. Assure alignment with NEOMED strategic objectives for IT project prioritization
  3. Add transparency to the prioritization of technology projects
  4. Increase collaboration across the university
  5. Make the best use of limited university resources

It also helps mitigate other challenges, such as:

  1. Ad hoc requests that lack proper authorization, sponsorship, resource commitments, and funding.
  2. “First come, first served” mindset
  3. Staff spread thin among many competing projects
  4. “Everything is a priority” which results in not delivering all requested projects on time

Framework

Enterprise-wide projects are measured against the the university strategic goals and its capabilities to undertake projects. The project prioritization process includes:

  1. Project scoring – An overall weighted score is generated that represents the project’s value to the campus. The higher the score, the more value. The NEOMED Project Scoring worksheet should be performed in addition to completing the project charter, which clearly outlines the project objectives, business justification, budget, resources required, etc.
  2. Funding availability – Identify available funds to carry out the project, and location of those funds.
  3. Resource capacity evaluation – Identify which IT and/or other department staff resources are available to work on the project.

A TAC subcommittee or designated task force is responsible for doing the research required in order to complete the project charter and scoring worksheet.

The TAC uses the project charter and scoring worksheet to approve and prioritize university initiatives.

  1. Project scheduling – A project is scheduled based on its scoring, including funding, and resource capacity. A high scoring project may not be able to start immediately if resources and/or funding are not available; in turn, lower scoring projects with available resources may start ahead of a higher scoring project. Projects with a future start date can be scheduled based on the future availability of resources and funding.


As a general rule, projects in motion will not be stopped and re-started just because their relative priority has changed; however, the Technology Advisory Council retains responsibility for overall project portfolio management. From time to time, this will require adjustment of project activities based on the best interests of the institution. Some examples of reasons to halt a project include:

  1. Organizational hardship (lack of funding)
  2. Project is destined to fail
  3. Business case no longer applies
  4. Overruns are extreme (budget and time)

 

 

Was this helpful?
0 reviews

Details

Article ID: 122484
Created
Fri 12/11/20 8:58 AM
Modified
Thu 1/7/21 1:54 PM