CAPMEasy

CAPM Practice: Demonstrate an understanding of product roadmaps

Question 10 of 67 in Demonstrate an understanding of product roadmaps

Pick an answer below — you'll get the explanation instantly, no signup.

How frequently should a product roadmap be reviewed and updated?

Show answer & explanation

Correct answer: Regularly (typically quarterly at minimum) to reflect new learning, changing priorities, customer feedback, and market conditions

Explanation

Product roadmaps should be living documents reviewed and updated regularly. Markets change, customers provide feedback, technical discoveries alter what's possible, and business priorities shift — all requiring roadmap adjustments.

**Why not A:** Daily roadmap reviews are excessive and counterproductive. Roadmaps are strategic planning tools that operate at a higher level than daily sprint activities. Reviewing them daily would create instability and undermine their purpose as a stable directional guide.

**Why not B:** Waiting for formal change requests before updating a roadmap is too rigid. Market conditions, customer feedback, and organizational priorities evolve continuously, and a roadmap must adapt to remain relevant — not only when formal scope changes occur.

**Why not D:** A roadmap created once and never updated becomes obsolete quickly. Refusing to adapt the roadmap actually erodes stakeholder trust rather than maintaining it, because stakeholders lose confidence in a plan that ignores changing realities.

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