Product Management Product Roadmap Planning 1 — Questions and Answers
Question 1: What is the primary purpose of a product roadmap?
- To communicate the product vision and direction over time (Correct answer)
- To list all bugs to be fixed
- To track daily developer tasks
- To document customer complaints
Correct answer: To communicate the product vision and direction over time
A product roadmap communicates the high-level vision, direction, and planned milestones for a product over a set time horizon.
Question 2: Which type of roadmap organizes features by themes rather than fixed dates?
- Now-Next-Later roadmap (Correct answer)
- Gantt chart roadmap
- Release calendar
- Sprint backlog
Correct answer: Now-Next-Later roadmap
The Now-Next-Later roadmap groups work into flexible time horizons by theme, avoiding commitment to fixed delivery dates.
Question 3: What does 'outcome-based' roadmapping prioritize?
- Customer and business outcomes over feature delivery (Correct answer)
- Number of features shipped per quarter
- Developer velocity metrics
- Bug resolution rate
Correct answer: Customer and business outcomes over feature delivery
Outcome-based roadmaps focus on measurable results such as retention or revenue rather than simply shipping features.
Question 4: Which stakeholder group should a PM consult FIRST when building a new roadmap?
- Customers and end users (Correct answer)
- The legal department
- The marketing agency
- Investors only
Correct answer: Customers and end users
Customer and user insights should ground the roadmap in real problems before internal priorities are layered in.
Question 5: What is 'roadmap debt'?
- Accumulated low-value items that crowd out strategic work (Correct answer)
- Technical debt logged on the roadmap
- Unpaid licensing fees for roadmap tools
- Features removed from the backlog
Correct answer: Accumulated low-value items that crowd out strategic work
Roadmap debt refers to carry-over items and low-priority work that accumulate over time and dilute the roadmap's strategic focus.
Question 6: How often should a product roadmap typically be reviewed and updated?
- Quarterly or more frequently as strategy evolves (Correct answer)
- Only at product launch
- Once per year
- Every sprint without exception
Correct answer: Quarterly or more frequently as strategy evolves
Roadmaps should be living documents reviewed at least quarterly to reflect new data, market changes, and strategic shifts.
Product Management Product Roadmap Planning 1
What is the primary purpose of a product roadmap?