CAPM Practice: Demonstrate an understanding of product roadmaps

Roadmap alignment ensures vertical consistency: portfolio strategy → product roadmap → release plan → iteration plan. When these levels align, every sprint advances the product roadmap, which advances portfolio goals, which advances organizational strategy. Misalignment creates wasted work.

**Why not A:** Roadmap alignment is not about visual formatting or making documents look consistent. Alignment refers to ensuring that strategic objectives, priorities, and timelines are coherent across organizational levels so that portfolio, program, and product roadmaps collectively support the same goals.

**Why not B:** Alignment does not mean that all stakeholders agree without any changes or negotiation. Achieving alignment typically requires iterative discussion, trade-offs, and adjustments to ensure that roadmaps at different levels are mutually supportive while respecting each level's constraints and priorities.

**Why not D:** While team-level buy-in on implementation details matters, roadmap alignment across organizational levels is a strategic concern. It focuses on ensuring that higher-level portfolio decisions cascade appropriately into program and product roadmaps, not merely on whether individual team members agree on how to execute tasks.