CAPMHard

CAPM Practice: Demonstrate an understanding of product roadmaps

Question 13 of 67 in Demonstrate an understanding of product roadmaps

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

A product manager is asked to commit to a feature delivery date 18 months out. Why should they be cautious about committing?

Show answer & explanation

Correct answer: 18 months out falls in the high-uncertainty zone of the cone of uncertainty — committing to a specific date and feature set that far in advance will likely create false expectations and require difficult future renegotiation

Explanation

The further into the future, the less predictable delivery becomes. Committing to specific features and dates 18 months out creates expectations that market changes, technical discoveries, or priority shifts may make impossible to keep — damaging trust when the roadmap must change.

**Why not A:** Avoiding all future commitments is impractical and unhelpful. Stakeholders and business planning require some forward-looking direction. The issue is not avoiding commitments entirely but being appropriately cautious about specificity at long time horizons where uncertainty is high.

**Why not B:** 18-month commitments are not inherently legally binding or requiring special executive sign-off. They are problematic because of the cone of uncertainty — the further out the commitment, the less predictable the actual delivery, creating unrealistic expectations rather than legal obligations.

**Why not C:** There is no PMI standard limiting product roadmaps to 12-month horizons. Roadmaps can extend to any time horizon appropriate for the business context. The concern with 18-month commitments is about prediction accuracy and expectation management, not a standards-imposed limitation.

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