CAPM Practice: Demonstrate an understanding of product roadmaps
Question 23 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: The process of managing changes to the roadmap — who can propose changes, who approves them, and how changes are communicated — maintaining integrity while allowing necessary adaptation
Explanation
Roadmap governance prevents the roadmap from becoming a free-for-all where anyone can add features, or a rigid document that can't adapt. It balances flexibility (the roadmap must change) with control (changes should be deliberate and communicated).
**Why not A:** Roadmap governance is not government or regulatory oversight. It is an internal organizational discipline for managing how roadmap changes are proposed, evaluated, approved, and communicated within the product team and its stakeholders.
**Why not C:** This confuses governance with legal document management. Roadmap governance concerns decision-making authority and change control processes, not the legal filing or archival of roadmap documents.
**Why not D:** While a PMO may participate in governance, this answer is too narrow. Roadmap governance encompasses the full lifecycle of change management — who proposes changes, how they are evaluated, who approves them, and how decisions are communicated — not just a single approval gate.
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