PSPO focused

Common Product Backlog item attributes are?

Description, order, and size.

What attributes do Product Backlog items often have (select all that apply)?

Description, order, and size.

The Product Owner must use burn-down charts to track progress.

False – Scrum does not prescribe any specific tracking tools; burn-down charts are optional practices.

The Product Owner is a project manager in Scrum.

False – Scrum has no project manager role; responsibilities are distributed across Scrum Team accountabilities.

Velocity is a mandatory measure of success for the Product Owner.

False – Scrum does not require velocity; success is measured by value delivered, not output metrics.

The Product Owner must ensure enough Product Backlog items are selected in Sprint Planning to satisfy stakeholders.

False – Developers select the work for the Sprint based on forecast; PO does not “satisfy stakeholders” through Sprint scope.

A demo of the Increment must be carried out at the Sprint Review.

False – Sprint Review is not a demo; it is a collaborative inspection and adaptation session.

What happens when a Sprint Goal becomes obsolete?

The Product Owner may cancel the Sprint.

Which of the following is not allowed by Scrum?

Hardening Sprints – because every Sprint must produce a Done Increment; otherwise previous Sprints were not truly complete.

SCRUM stands for?

Scrum is not an acronym – it is a framework name, not a shortened form of words.

One of the accountabilities of the Product Owner is to create the Sprint Goal before Sprint Planning.

False – Sprint Goal is created collaboratively during Sprint Planning by the whole Scrum Team.

When should the Product Owner provide feedback on Developers' work?

Whenever feedback can help avoid waste.

The Product Owner should be aware of the marketplace for the product.

True – understanding market and users helps maximize product value.

Before the first Sprint, the Product Backlog must contain everything we will develop.

False – Scrum works with emergent requirements; it is impossible to know everything upfront.

The Sprint Backlog is owned by:

The Developers.

What is Product Backlog grooming?

The old and outdated name for Product Backlog refinement – term is no longer used in Scrum.

What should the Product Owner do mid-Sprint when Developers cannot finish all forecast items?

Understand forecasts are uncertain and help the team adapt and learn; do not treat it as failure.

How should the Product Owner respond when Developers ask for clarification during the Sprint?

Provide clarification or enable them to get it – PO must be available to reduce uncertainty.

The Definition of Done is an input to Sprint Planning.

True – it is needed to understand what “Done” means for forecasting work.

The Product Owner does not have to be one person; it can be a committee.

False – Scrum explicitly states PO is one person to avoid conflicting priorities.

A product could be a service.

True – Scrum defines product broadly (service, physical product, digital, etc.).

A Scrum Team must only work on a single Product Goal at any time.

True – focus is required; multiple goals reduce clarity and alignment.

When must a new Increment be available?

Before the Sprint Review – otherwise there is nothing meaningful to inspect.

Who manages the Sprint Backlog?

The Developers.

Product Backlog refinement is...

An ongoing collaboration between Product Owner and Developers to break down and clarify work.

What is the Product Goal?

A long-term objective that provides direction and focus for the Scrum Team.

Timebox for Sprint Planning?

Up to 8 hours.

Timebox for Daily Scrum?

15 minutes.

Timebox for Sprint Review?

Up to 4 hours.

Timebox for Sprint Retrospective?

Up to 3 hours.

What does the Product Owner do between Sprints?

Sprints have no gap – next Sprint starts immediately, so work continues seamlessly.

Beliefs about value are assumptions until validated by customers.

True – Scrum is empirical; value must be tested in real use.

A release is mandatory at the end of every Sprint.

False – Increment must be usable, but release is optional and can happen anytime.

The Product Owner manages what?

The Product Backlog.

A Product Owner is:

One person, not a committee – ensures clear accountability and decision-making.

Why must Product Backlog be ordered rather than prioritised?

Order provides a single, clear sequence of work; priority alone can be ambiguous or duplicated.

Ordering Product Backlog is part of refinement.

True – refinement includes ordering, sizing, and clarification.

Who can add items to the Product Backlog?

Anyone can propose items, but Product Owner is accountable for what enters and how it is ordered.

Product Backlog may be reordered after Sprint Review input.

True – Sprint Review often provides new insights that affect ordering.

A Product Backlog is never complete.

True – as long as a product exists, backlog evolves continuously.

What is an emergent, ordered list of work?

Product Backlog.

Stakeholders may include HR representatives.

True – stakeholders can be anyone impacted by or interested in the product.

Stakeholders may not talk to Developers during a Sprint.

False – direct collaboration is allowed and often encouraged if it supports value delivery.

Sprints help limit work in progress.

True – Sprints create a fixed timebox and focus on a small set of work.

Who is accountable for creating a valuable Increment every Sprint?

The entire Scrum Team – value is a shared responsibility.

Who is accountable for Product Goal?

Product Owner – responsible for defining and communicating the Product Goal.

The Product Owner is owner of Definition of Done.

False – DoD is created by the Scrum Team (or organization standard).

Who can tell Developers what to work on?

Product Owner (via Product Backlog).