CAPM Practice: Demonstrate an understanding of product roadmaps

Roadmap scope defines what the product will and won't address strategically. A clear scope prevents endless feature addition (roadmap creep) and helps teams say no to requests outside the product's strategic direction — maintaining coherent product focus.

**Why not A:** Budget is a constraint on the roadmap, not its scope. Scope defines the boundaries of what the product will and will not include in terms of capabilities and themes. Financial planning supports the roadmap but does not define the breadth of the product's strategic direction.

**Why not C:** A project manager's authority relates to governance and decision-making, not scope. Scope in the roadmap context is about the range of capabilities planned for the product. Approval authority is a separate concern related to organizational roles and change management processes.

**Why not D:** The number of sprints is a measure of timeline and effort, not scope. Scope defines what is included in the product's strategic direction, while sprint count reflects how long delivery will take. Confusing scope with schedule is a common misunderstanding that can lead to poor planning decisions.