CAPM Practice: Demonstrate an understanding of product roadmaps

This 'rolling wave' approach to roadmaps reflects reality: near-term work (next iteration or quarter) is well-understood and committed; medium-term work is planned but may change; long-term work is directional intent, not commitment.

**Why not B:** A product roadmap is not a commitment with equal certainty across all time horizons. Near-term items on a roadmap carry higher confidence because they have been more thoroughly researched, estimated, and validated. Items further out are inherently more speculative and subject to change as market conditions, customer needs, and organizational priorities evolve. Treating a roadmap as a fixed commitment undermines its value as a strategic planning tool.

**Why not C:** Confidence levels are commonly represented on product roadmaps and are considered a best practice. Many roadmap formats explicitly show confidence through visual cues such as color coding, graduated detail levels, or labeling horizons as "committed," "planned," and "exploratory." Omitting confidence information would mislead stakeholders into treating all items as equally certain.

**Why not D:** Far-future items on a roadmap are less detailed, not more detailed. Near-term items typically include specific features, estimated timelines, and assigned teams, while items further out are represented as broader themes or strategic objectives. This graduated detail reflects the decreasing certainty over time and allows teams to adapt their plans as they learn more.