PSPO Product Goal and Strategy 2

Question 1

What is product strategy in the context of PSPO?

Accepted Answer

The plan for how the product will achieve its vision and deliver value to users and the business

Answer

The technical architecture decisions made by Developers

Answer

A marketing plan for the product launch

Answer

The Sprint-by-Sprint implementation schedule

Question 2

What is a product roadmap and how does it relate to the Product Backlog?

Accepted Answer

A roadmap communicates the strategic direction and likely evolution of the product; the backlog is its operational expression

Answer

A roadmap replaces the Product Backlog in long-term planning

Answer

A roadmap is a contract with stakeholders for fixed deliverables

Answer

A roadmap is maintained by the Scrum Master

Question 3

Why should a Product Owner avoid over-committing to long-term roadmap details?

Accepted Answer

Because markets and user needs evolve, making rigid long-range plans obsolete quickly

Answer

Because Developers cannot plan more than one Sprint ahead

Answer

Because stakeholders should define long-term plans

Answer

Because Scrum prohibits planning beyond the current Sprint

Question 4

What is a Minimum Viable Product (MVP) and why is it relevant to a PSPO?

Accepted Answer

The smallest version of a product that allows validated learning about customers with minimal effort

Answer

A product with the lowest possible quality

Answer

A prototype used only for internal testing

Answer

A product release with no features removed

Question 5

How should a Product Owner handle technical debt in the product strategy?

Accepted Answer

Include technical debt items in the Product Backlog and balance addressing debt with delivering new value

Answer

Ignore it since it is a Developer concern only

Answer

Resolve all technical debt before adding new features

Answer

Delegate all technical debt decisions to the Scrum Master

Question 6

What does 'product thinking' mean for a Product Owner?

Accepted Answer

Focusing on outcomes and user value rather than just output and feature delivery

Answer

Thinking only about features requested by stakeholders

Answer

Planning all product features in advance before any Sprint

Answer

Thinking about the technical implementation first