Updated Prioritized Program or Portfolio Backlog

The current, ranked list of program or portfolio work that has been refreshed to include new or revised user stories, approved change requests, newly identified risks, and any reordering of existing items. In this context, users are the people or organizations that directly use the product, service, or result; they can be internal or external, and in some cases the customer and the user are the same.

Key Points

  • A living, prioritized backlog at the program or portfolio level that changes as new information emerges.
  • Updated by adding new user stories, incorporating change requests, recording new risks, refining stories, and reprioritizing items.
  • Users are direct consumers of the outcome and may be inside or outside the organization; sometimes users and customers are the same.
  • Prioritization reflects strategic alignment, value, risk, dependencies, and capacity across teams.

Example

During a quarterly portfolio review, a compliance change request is approved, a critical security risk is identified, and several user stories are refined based on feedback from internal operations staff and external clients. The portfolio owner updates the prioritized backlog by adding the new items, adjusting acceptance criteria on existing stories, and moving the security-related work to the top to address the newly discovered risk.

PMP Example Question

After a governance review, new user stories are proposed, a change request is approved, and a significant risk is discovered. Which artifact should be revised to reflect the new ordering of work across multiple programs?

  1. Risk register
  2. Change log
  3. Updated Prioritized Program or Portfolio Backlog
  4. WBS dictionary

Correct Answer: C — Updated Prioritized Program or Portfolio Backlog

Explanation: The prioritized backlog is the central, ordered list of work at the program/portfolio level and should be updated to capture new stories, approved changes, newly identified risks, and reprioritization. The risk register and change log are also maintained, but they do not drive the cross-program ordering of delivery items.

ICS/OT Cybersecurity Fundamentals — Security Built for Industrial Systems

Industrial control systems cannot be secured like ordinary IT. A forced reboot, aggressive scan, or incompatible patch can interrupt production and create real safety consequences. Effective OT security begins with understanding the systems, constraints, and risks unique to industrial environments.

This course gives IT professionals, engineers, operators, and security practitioners a practical foundation in ICS threats, zone and conduit design, risk assessment, passive asset visibility, and vendor evaluation. You will learn how IEC 62443, NIST CSF, and MITRE ATT&CK for ICS apply where availability and safety come first.

Eight reconstructed incidents—including Stuxnet, Triton, Ukraine 2015, Colonial Pipeline, and PIPEDREAM—show how attackers move through OT environments, what they target, and which defenses could have changed the outcome.

Watch the course preview, then build the vocabulary, frameworks, and judgment needed to take credible first steps in ICS/OT cybersecurity.

Explore the Course


ICS/OT Cybersecurity Fundamentals course preview

Lead with clarity, influence, and outcomes.

HK School of Management offers a practical Leadership for Project Managers course for real projects, tight deadlines, and cross-functional teams. Learn to set direction, align stakeholders, and drive commitment without relying on title. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More