APM Agile Product Strategy and OKRs 3

Question 1

In agile product strategy, what is a 'theme' on an outcome-based roadmap?

Accepted Answer

A high-level strategic focus area grouping related initiatives that guides prioritization without locking in features

Answer

A specific user story grouping related acceptance criteria together

Answer

The visual design language applied consistently across product features

Answer

A fixed release cadence for major product version updates

Question 2

How should a product manager use competitive analysis when informing product strategy?

Accepted Answer

Identify market gaps, differentiation opportunities, and threats to inform strategic positioning decisions

Answer

Copy competitor features directly to maintain market parity at all times

Answer

Use competitor pricing exclusively to set your product's pricing model

Answer

Avoid competitive analysis entirely to prevent anchoring bias toward existing market solutions

Question 3

What is the primary risk of building OKRs around vanity metrics?

Accepted Answer

Vanity metrics may show impressive growth without indicating real business or customer value

Answer

It makes OKR tracking too administratively complex for the team to manage

Answer

Vanity metrics are not compatible with agile sprint cycles and planning

Answer

Using vanity metrics technically violates published OKR framework guidelines

Question 4

What is the recommended approach when product OKRs conflict with each other (e.g., growth vs. monetization)?

Accepted Answer

Facilitate a prioritization discussion to rank the trade-offs and clarify which objective takes precedence

Answer

Remove all conflicting OKRs and replace them with a single combined objective

Answer

Escalate every OKR conflict to the CEO to resolve on behalf of the team

Answer

Allow each team to independently optimize for their own OKR without cross-team coordination

Question 5

What fundamentally distinguishes a product strategy from a product roadmap?

Accepted Answer

A product strategy defines the WHY and HOW you will win; a roadmap communicates WHAT and WHEN you will build

Answer

A product strategy is short-term while a roadmap is multi-year by definition

Answer

A product roadmap is internal only while a product strategy is shared externally with customers

Answer

A product strategy focuses on engineering architecture decisions while a roadmap focuses on marketing plans

Question 6

In agile product strategy, what does 'continuous discovery' (as described by Teresa Torres) mean?

Accepted Answer

An ongoing practice of regularly engaging customers — at least weekly — to continuously generate and test product opportunities

Answer

Running daily sprint reviews to discover technical impediments to delivery

Answer

Continuously discovering new product categories to expand the company's portfolio

Answer

The process of finding and documenting bugs continuously throughout the product lifecycle

Question 7

What is the primary purpose of an 'assumption mapping' exercise in agile product strategy?

Accepted Answer

To identify and prioritize the riskiest assumptions underlying a strategy so they can be tested before committing resources

Answer

To document the technical assumptions made during software architecture design sessions

Answer

To map out all assumptions surfaced during the sprint retrospective for future reference

Answer

To align stakeholder assumptions about delivery timelines and release dates