CAPM Practice: Demonstrate an understanding of product roadmaps

A feature-based roadmap organizes planned work around product capabilities — grouping features by theme or release. It's common in product management and bridges strategic direction and development planning.

**Why not A:** A technical specification document showing how each feature will be built is a design document, not a feature-based roadmap. A roadmap shows what will be built and roughly when at a strategic level, while technical specifications detail the implementation approach at a much lower level.

**Why not B:** A roadmap created by software developers listing only coding features is too narrow. Feature-based roadmaps are product management artifacts that include customer-facing capabilities, not just technical coding tasks. They are typically created by product managers in collaboration with stakeholders, not by developers alone.

**Why not D:** Showing only one feature per quarter regardless of scope is an arbitrary constraint that no roadmap methodology prescribes. Feature-based roadmaps show planned capabilities organized by time horizon, and the number of features per period depends on scope, complexity, and team capacity, not a fixed limit.