Program and Portfolio Risks

Uncertainties that arise at the program or portfolio level and have consequences for the projects contained within that program or portfolio.

Key Points

  • These risks originate above individual projects and can affect multiple projects simultaneously.
  • They are typically owned and coordinated by program or portfolio leadership, with linkage to project teams.
  • Responses often require cross-project coordination, shared decisions, and possibly reallocation of resources or funding.
  • They should be tracked in program/portfolio risk registers and referenced in project risk registers for visibility and alignment.

Example

A companys portfolio depends on a new enterprise platform contract. If contract negotiations are delayed, several projects using that platform will face schedule slips and cost increases. The portfolio manager owns the risk, coordinates mitigation across projects, and each project cross-references the portfolio risk in its own register.

PMP Example Question

A project manager learns of a potential portfolio-level budget cut that may reduce funding across several projects. What is the best action?

  1. Record it only in the project risk register and create a project-specific response.
  2. Escalate it to the program/portfolio risk register and coordinate a shared response, while cross-referencing it in the project register.
  3. Ignore it until the budget cut is formally approved.
  4. Immediately reduce project scope without engaging program or portfolio leadership.

Correct Answer: B — Escalate to the program/portfolio risk register and coordinate a shared response

Explanation: Because the uncertainty originates at the portfolio level and affects multiple projects, it should be owned and managed at that level, with the project linking and aligning its actions accordingly.

ICS/OT Incident Response Plan: Write One That Works

Most OT incident response plans fail before anyone writes a word: no sponsor, no charter, no agreement on who decides. This workshop course takes you from a blank page to a plan your site approves and your operators can follow.

Each of the eight sections writes one chapter of your plan: the authority and scope, the inputs, severity in the language of the plant, command and decision rights, response steps, recovery and the readiness library.

You get the plan template, more than 40 templates and worksheets, 21 worked examples and a capstone with a full model answer.

50 videos, 7.7 hours. US$147 one-time through HKSM Courses. 30-day money-back guarantee when 50% or less consumed.

Explore the Course


ICS/OT Incident Response Plan course preview

Build the Sprint Reporting System, Not Another Prompt

AI Systems with Claude is our own course for Scrum Masters and Agile Project Managers, taught against one running project across eight teaching sections. You build five working systems and keep them: the sprint report machine, the retro intelligence system, the stakeholder comms engine, the backlog health monitor, and the risk and dependency tracker. Direct from HK School of Management and Technology, not on Udemy.

See What Is Included