Roadmaps may be prepared to show different elements, and at the beginning they may not provide details of the various components. As a high-level plan at the portfolio level, the roadmap:

Question

Options

• AIdentifies internal and external dependencies
• BServes as a master schedule to show the timing of approved components
• CContains all the details of program and project roadmaps
• DServes to identify issues

• A
  73% (27)
• B
  8% (3)
• C
  3% (1)
• D
  16% (6)

Explanation

A portfolio roadmap is a high-level strategic document that shows how components relate to each other and to the organization's strategic objectives over time. A key function is to identify internal dependencies (between portfolio components) and external dependencies (with outside organizations, market conditions, or regulatory requirements). This is essential for sequencing and coordinating work. Option B is incorrect because the roadmap is not a detailed master schedule; schedules exist at the program and project level. Option C is incorrect because the portfolio roadmap deliberately omits granular details found in lower-level roadmaps. Option D (identifying issues) is not the roadmap's primary purpose-that belongs to risk and issue logs.

No community discussion yet for this question.