Portfolio Prioritization

 

  • As staff and faculty identify technology/process/data issues or needs, they enter a ticket via our TeamDynamix Client Portal. Tickets are triaged by the Helpdesk and assigned to the appropriate ticketing group.
  • Enterprise Applications leadership and/or architects review tickets to determine complexity. Complex tickets are converted to a Project Request.
  • All new Project Requests are reviewed weekly by the PMO and a project manager liaison is assigned.
  • The PMO liaison works with the requestor to complete a project charter.
  • The PMO works with the appropriate division prioritization team to review the project charter(s) and answer the questions from the scorecard to provide the project request(s) with a score. The division prioritization team then prioritizes the request(s) within their division based on score and other relevant factors.
    • The score is comprised of questions that align to both value and risk.
  • The PMO works with the Cross-Division Prioritization Team (comprised of divisional prioritization teams) quarterly to review the prioritized requests from each division and make decisions on the most important project requests to be scheduled.
  • The PMO works with the Enterprise Applications (EA) leadership team to determine capacity and schedule the prioritized project requests until capacity is full.
  • The PMO maintains a portfolio calendar of prioritized projects.

Note that as new project requests are entered almost daily, the process above is perpetual.  There is continuous refinement of the prioritized requests and the portfolio calendar.  However, once a project is started, we do our best not to impact an active project.