CAPM Practice: Explain the components of an adaptive plan

A product roadmap provides a high-level, directional view of where the product is heading over a longer period (quarters, releases, or themes). It is intentionally less detailed than sprint-level plans, acknowledging that far-future details are unknowable. The roadmap communicates strategic direction and sequencing of major features without committing to specific sprint-level details.

**Why not A:** A product roadmap is not a contractual commitment — it is a strategic communication tool that sets direction without locking the team into specific features on specific dates. Adaptive projects explicitly recognize that far-future details are unknowable, so binding contract language would contradict core agile principles. Commitments at that level of specificity belong to a sprint plan or release agreement, not a roadmap.

**Why not C:** Prioritizing every item in the backlog is the function of the product backlog itself, not the product roadmap. The roadmap operates at a higher level of abstraction — grouping features into themes, epics, and release milestones rather than sequencing individual backlog items. Conflating the two artifacts blurs the distinction between strategic planning (roadmap) and tactical ordering (backlog).

**Why not D:** A detailed task list for each sprint is the output of sprint planning, not the product roadmap. The roadmap intentionally avoids that level of granularity because sprint-level details six months out are unreliable and would require constant revision as priorities change. Premature detail in a roadmap creates false certainty and wastes planning effort.