APM Product Vision and Roadmap 3 — Questions and Answers
Question 1: Which technique helps a product team evaluate whether a proposed feature aligns with the product vision before adding it to the roadmap?
- T-shirt sizing estimation
- Impact mapping (Correct answer)
- Burndown chart analysis
- Retrospective voting
Correct answer: Impact mapping
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?
- The roadmap becomes too short-term focused
- The team builds features that don't address real customer needs, wasting resources (Correct answer)
- Sprint velocity increases unsustainably
- The product vision becomes too aspirational
Correct answer: The team builds features that don't address real customer needs, wasting resources
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?
- Only at annual planning sessions
- Continuously, with structured reviews at least quarterly or after major learning milestones (Correct answer)
- Once per product release cycle, regardless of duration
- Never — a roadmap should remain stable to give teams predictability
Correct answer: Continuously, with structured reviews at least quarterly or after major learning milestones
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?
- It is too customer-focused
- It lacks specificity about the target audience and is not easily measurable (Correct answer)
- It references a physical product, which limits digital expansion
- It is too inspirational for a development team to act on
Correct answer: It lacks specificity about the target audience and is not easily measurable
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?
- Excitement (delighter) features
- Basic (must-be) features (Correct answer)
- Performance (linear) features
- Indifferent features
Correct answer: Basic (must-be) features
Basic (must-be) features are hygiene factors — their absence causes dissatisfaction even though their presence doesn't create delight.
Question 6: What does a 'theme-based' roadmap communicate that a feature-based roadmap does NOT?
- Exact release dates for each deliverable
- Strategic problem areas and customer outcomes rather than specific solutions (Correct answer)
- Individual developer assignments for each feature
- The current sprint backlog priority order
Correct answer: Strategic problem areas and customer outcomes rather than specific solutions
Theme-based roadmaps group work by strategic intent or customer problem, preserving flexibility on the specific solution while communicating direction.
Question 7: Which stakeholder communication practice BEST maintains alignment on product vision during rapid organizational growth?
- Sending detailed technical specs to all departments weekly
- Holding regular vision alignment sessions and making the vision document publicly accessible internally (Correct answer)
- Restricting vision communication to the product team only
- Updating the company website homepage with each vision change
Correct answer: Holding regular vision alignment sessions and making the vision document publicly accessible internally
Regular vision alignment sessions combined with accessible documentation ensure new and existing team members remain aligned as organizations scale.
APM Product Vision and Roadmap 3
Which technique helps a product team evaluate whether a proposed feature aligns with the product vision before adding it to the roadmap?