CAPM Practice: Demonstrate an understanding of product roadmaps
Question 26 of 67 in Demonstrate an understanding of product roadmaps
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: A large piece of functionality representing significant product capability that spans multiple iterations and is often shown at the roadmap level before being broken into smaller stories
Explanation
Epics represent substantial product capabilities (e.g., 'Self-service customer portal') that appear on roadmaps as planned work. They're later broken into features and user stories for backlog planning and iteration execution.
**Why not A:** Epics are not exclusive to roadmaps. They are commonly used in backlogs as well, where they serve as containers for related user stories that together deliver a significant piece of functionality. Epics appear at multiple levels of planning, from strategic roadmaps down to team-level backlogs.
**Why not B:** This is a playful distractor that confuses the common English meaning of "epic" with its agile usage. In product management and agile contexts, an epic is a defined unit of work representing a large capability — it has nothing to do with chronicling the history of a product's development.
**Why not D:** This distractor again plays on the everyday meaning of "epic" as something impressive or celebrated. In roadmap and agile terminology, an epic is a structural concept for grouping related work, not a recognition or celebration of a feature's success.
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