CPM Product Roadmap and Planning 3 — Questions and Answers
Question 1: What is an 'OKR' (Objectives and Key Results) and how does it relate to product planning?
- A software testing framework
- A goal-setting system linking high-level objectives to measurable outcomes that guide product priorities (Correct answer)
- An agile ceremony for reviewing sprint results
- A financial reporting format
Correct answer: A goal-setting system linking high-level objectives to measurable outcomes that guide product priorities
OKRs are a goal-setting framework where Objectives define what to achieve and Key Results define measurable outcomes, ensuring product work is tied to strategic goals.
Question 2: What is a 'release plan' and how does it differ from a product roadmap?
- They are interchangeable terms
- A release plan details what will be delivered in a specific release, while a roadmap shows the long-term strategic direction (Correct answer)
- A release plan covers multiple years; a roadmap covers one sprint
- A release plan is for customers; a roadmap is for engineers
Correct answer: A release plan details what will be delivered in a specific release, while a roadmap shows the long-term strategic direction
A release plan provides the tactical details of a specific upcoming release, while the product roadmap provides the broader strategic direction over a longer horizon.
Question 3: What is the 'RICE' prioritization framework?
- Relevance, Impact, Cost, Effort
- Reach, Impact, Confidence, Effort — a scoring model to objectively rank product initiatives (Correct answer)
- Risk, Investment, Customer, Execution
- Revenue, Iterations, Cost, Evaluation
Correct answer: Reach, Impact, Confidence, Effort — a scoring model to objectively rank product initiatives
RICE scores each initiative based on Reach (users affected), Impact (per user), Confidence (in estimates), and Effort (work required) to rank priorities objectively.
Question 4: Why is it important to include 'technical debt' work in a product roadmap?
- To keep engineers happy
- Because unaddressed technical debt slows future development, increases risk, and can degrade product quality (Correct answer)
- Because financial reporting requires it
- Only legacy products need this
Correct answer: Because unaddressed technical debt slows future development, increases risk, and can degrade product quality
Ignoring technical debt makes future development slower and riskier; allocating roadmap capacity to address it maintains product health and team velocity.
Question 5: What does a 'confidence level' in roadmap estimates reflect?
- The team's enthusiasm for the work
- The degree of certainty in estimates based on available information and prior experience (Correct answer)
- Customer confidence in the product
- The certainty that a feature will be well-received
Correct answer: The degree of certainty in estimates based on available information and prior experience
Confidence levels indicate how certain the team is about an estimate, helping stakeholders understand the risk and reliability of roadmap commitments.
Question 6: What is the risk of committing to a highly detailed, fixed long-term roadmap?
- It makes the team too comfortable
- It reduces flexibility to adapt to new market data, customer feedback, or strategic shifts (Correct answer)
- It causes roadmaps to become too short
- It prevents engineers from estimating effort
Correct answer: It reduces flexibility to adapt to new market data, customer feedback, or strategic shifts
Highly rigid long-term roadmaps assume certainty that doesn't exist; they prevent teams from adapting to new learning, making plans obsolete and costly to change.
CPM Product Roadmap and Planning 3
What is an 'OKR' (Objectives and Key Results) and how does it relate to product planning?