Which portfolio management document contains key dependencies?

Question

Options

• APortfolio Benefits Management Framework
• BPortfolio Stakeholder Engagement and Communications Plan
• CPortfolio Delivery Plan
• DPortfolio Resource Schedule

• A
  2% (1)
• B
  4% (2)
• C
  94% (44)

Explanation

Option C is correct because the Portfolio Delivery Plan maps out how portfolio components (programs, projects, and operations) will be executed and sequenced, making it the natural home for key dependencies - it captures what must happen before other work can begin, critical path relationships, and interdependencies between components.

Option A (Benefits Management Framework) is wrong because it focuses on how benefits will be identified, measured, and realized, not on scheduling or component sequencing.

Option B (Stakeholder Engagement and Communications Plan) is wrong because it addresses who needs to be engaged, when, and how - it's about communication strategies, not work dependencies.

Option D (Resource Schedule) is wrong because it focuses on allocating people and capacity across the portfolio, not on the logical relationships between deliverables.

Memory tip: Link "Delivery" with "Dependencies" - you cannot plan how to deliver without knowing what depends on what. The Delivery Plan sequences all portfolio components, so dependencies live there.

No community discussion yet for this question.