CAPM Practice: Demonstrate an understanding of product roadmaps

Confidence levels make uncertainty explicit rather than hiding it behind false precision. Near-term items might show 90% confidence; items 12 months out might show 40%. This honest communication manages expectations and prevents disappointment when plans change.

**Why not B:** A confidence level indicator on a roadmap addresses delivery certainty, not commercial viability. It communicates how likely a specific item is to be delivered as planned, which is a project-level concern. Market success predictions belong to business case analysis, not roadmap confidence indicators.

**Why not C:** Customer satisfaction scores from past features are a form of historical data used in product analytics, not a roadmap confidence indicator. Confidence levels are forward-looking assessments of delivery likelihood, not retrospective measures of how similar features were received by customers.

**Why not D:** A confidence level on a roadmap is not a subjective assessment of team capability by a project manager. It reflects the inherent uncertainty in planning — items further in the future naturally have lower confidence because more variables are unknown. It is a planning transparency tool, not a performance evaluation.