CAPM Practice: Demonstrate an understanding of product roadmaps
Question 44 of 67 in Demonstrate an understanding of product roadmaps
Show answer & explanation
Correct answer: Item name/theme, time horizon (now/next/later or quarter), business rationale or goal, and potentially confidence level
Explanation
Roadmap items typically show: what (theme or feature name), when (time horizon), why (business goal or customer value), and sometimes the confidence level. Technical details, assignments, and exact costs belong in implementation planning, not the roadmap.
**Why not B:** Exact development hours, assigned developers, and line-by-line cost breakdowns are implementation planning details, not roadmap-level information. Roadmaps are intentionally higher-level, showing strategic direction and time horizons rather than granular execution details.
**Why not C:** Database schema, API endpoints, and technical implementation details belong in technical design documents, not the product roadmap. Roadmap items communicate what will be delivered and why, not the technical approach to building it.
**Why not D:** Individual team member assignments and performance metrics are project management and HR concerns, not roadmap content. Roadmaps communicate product direction to stakeholders, not internal team management details.
Key Concept
This question covers Demonstrate an understanding of product roadmaps under Demonstrate an understanding of product roadmaps (Business Analysis Frameworks).
All 1,500+ CAPM questions are free
Sign up to track your progress, see detailed analytics, and get personalized study recommendations.
Sign Up Free