CAPM Practice: Demonstrate an understanding of product roadmaps

Committing to exact feature delivery dates far in advance creates false certainty and damages credibility when plans inevitably change. Roadmaps should show direction and sequence rather than precise commitments for work that's too far away to estimate reliably.

**Why not A:** High-level themes and strategic objectives are appropriate roadmap content. They communicate the direction and purpose behind planned work, helping stakeholders understand why specific initiatives are prioritized and how they connect to organizational strategy.

**Why not B:** Business rationale for roadmap priorities is valuable roadmap content. It helps stakeholders understand the reasoning behind sequencing decisions and builds confidence that the roadmap reflects thoughtful strategic analysis rather than arbitrary ordering.

**Why not D:** Planned releases and milestones are appropriate roadmap elements, especially for near-term work. They provide useful reference points for coordination and planning. The issue is with committing to exact dates for distant features, not with showing releases and milestones at appropriate levels of certainty.