APM Product Vision and Roadmap 3

Question 1

Which technique helps a product team evaluate whether a proposed feature aligns with the product vision before adding it to the roadmap?

Accepted Answer

Impact mapping

Answer

Impact mapping links features to goals and actors, helping teams verify that proposed work supports the product vision and strategic objectives.

Question 2

What is the PRIMARY risk of building a roadmap driven by the loudest stakeholder rather than data and customer insights?

Accepted Answer

The team builds features that don't address real customer needs, wasting resources

Answer

Stakeholder-driven roadmaps without customer validation risk prioritizing internal preferences over actual user needs, leading to low adoption.

Question 3

In Agile product management, how often should a product roadmap typically be reviewed and updated?

Accepted Answer

Continuously, with structured reviews at least quarterly or after major learning milestones

Answer

Agile roadmaps are living documents that should be reviewed continuously and formally updated at least quarterly to reflect new insights.

Question 4

A product vision states: 'To be the world's most convenient grocery delivery service.' What is a potential weakness of this vision?

Accepted Answer

It lacks specificity about the target audience and is not easily measurable

Answer

A good vision should ideally identify who it serves; 'world's most convenient' is also vague without metrics, making it hard to evaluate progress.

Question 5

When using the Kano model to inform roadmap decisions, which category of features MUST be present to avoid customer dissatisfaction?

Accepted Answer

Basic (must-be) features

Answer

Basic (must-be) features are hygiene factors — their absence causes dissatisfaction even though their presence doesn't create delight.

(APM) Agile Product Management Certification Practice Test