APM Agile Product Strategy and OKRs 2

Question 1

What is the primary difference between 'output metrics' and 'outcome metrics' in agile product strategy?

Accepted Answer

Output metrics track what was built or delivered; outcome metrics measure the business or customer value achieved

Answer

Output metrics measure team velocity; outcome metrics measure customer satisfaction scores

Answer

Output metrics are used in Scrum; outcome metrics are used in Kanban frameworks

Answer

Output metrics are lagging indicators; outcome metrics are always leading indicators

Question 2

In a NOW-NEXT-LATER roadmap format, what does the 'NEXT' column typically represent?

Accepted Answer

Well-defined, high-priority work coming in the near future (typically 1–3 months) not yet started

Answer

Features currently in active development during the ongoing sprint

Answer

Work planned for the next sprint regardless of strategic value

Answer

Features that have been deprioritized to an indefinite backlog

Question 3

What is 'opportunity scoring' (as developed by Tony Ulwick) used for in agile product strategy?

Accepted Answer

Prioritizing product opportunities based on customer-reported importance versus current satisfaction levels

Answer

Calculating the ROI for features already shipped to production

Answer

Measuring sprint velocity against a pre-defined target velocity

Answer

Evaluating vendor bids for third-party product development

Question 4

How do product vision and OKRs relate to each other in agile product management?

Accepted Answer

The product vision provides long-term direction; OKRs define measurable quarterly steps toward that vision

Answer

The product vision replaces OKRs in organizations that use the Scrum framework

Answer

OKRs are set independently of the product vision to allow quarterly flexibility

Answer

Product vision is reset quarterly to remain aligned with each OKR cycle

Question 5

What does 'strategic alignment' mean in agile product management?

Accepted Answer

Ensuring the product backlog, team OKRs, and company strategy coherently point toward the same goals

Answer

Ensuring all sprint tasks are equally distributed among team members

Answer

Aligning the product roadmap with the engineering team's technical preferences

Answer

Synchronizing product releases with marketing campaign schedules

Question 6

What is the 'Jobs to be Done' (JTBD) framework primarily used for in agile product strategy?

Accepted Answer

Understanding the underlying customer motivations and circumstances that lead them to use a product

Answer

Defining the work breakdown structure for sprint tasks

Answer

Documenting the role descriptions for each product team position

Answer

Scheduling product releases to align with customer purchase cycles

Question 7

How should a product team respond when sprint work is not aligned with the current quarter's OKRs?

Accepted Answer

Review and refocus sprint goals so the sprint work contributes to OKR achievement

Answer

Continue sprint work as planned since OKRs are fixed and cannot influence active sprints

Answer

Remove the OKRs from tracking until the sprint completes

Answer

Escalate immediately to management to have OKRs adjusted to match the sprint plan