CAPM Practice: Demonstrate an understanding of product roadmaps

Roadmap dependencies (technical prerequisites, regulatory sequencing, integration requirements) must be explicitly mapped to ensure items are sequenced correctly. Undiscovered dependencies can invalidate roadmap commitments when discovered mid-execution.

**Why not A:** Two features that share similar user stories are not dependencies. A dependency exists when one feature or work item cannot begin or be completed until another is finished first. Features with similar stories may be related thematically but can typically be developed independently of each other without any sequential constraint.

**Why not B:** A regulatory requirement that all features must satisfy is a constraint or compliance requirement, not a dependency in the roadmap sense. Dependencies specifically describe sequential relationships where one item relies on the completion of another. Regulatory requirements are cross-cutting concerns that apply broadly and are handled through compliance frameworks rather than dependency mapping.

**Why not D:** A feature that depends on customer willingness to pay describes a market risk or business viability concern, not a roadmap dependency. Dependencies on a product roadmap refer to technical or logical sequencing relationships between features or deliverables, such as building an authentication system before implementing user-specific dashboards. Customer demand is a separate consideration addressed through market validation.