Free Scrum Product Owner I (PSPO I) Practice Assessment

Full details on this practice assessment can be found here.

Results
59 of 60 Questions answered correctly

Your time: 00:07:22

You have reached 59 of 60 point(s), (98.33%)

Congratulations, you have scored over 85% and passed the practice assessment.

This is a good sign that you are ready to attempt the Professional Scrum Product
Owner I (PSPO I) assessment from Scrum.org.

Click ‘View questions’ below to see which you got right and wrong and review the
feedback for each question. Please note that we are unable to provide answers or
further guidance on assessment questions. You can retake the assessment if you
wish.

Do you want more practice questions? Try our Ultimate Scrum Product Owner
(PSPO I) Practice Assessment which contains 400+ questions.

Restart Practice Assessment View Questions

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
Correct Incorrect
What should the Product Owner do mid-Sprint, when the Developers realise they
will not be able to finish all the forecast Product Backlog items in the Sprint?

Punish the Developers for providing an incorrect estimate

Accept that the Developers forecast was incorrect. Help them moving
forward to forecast with greater accuracy

Report the failure of the Developers to management

Cancel the Sprint

Correct
In complex environments, forecasts are rarely 100% accurate. The Product
Owner should understand this and not see it as a failure on the part of the
Developers.

Who can tell the Developers what to work on?

The Scrum Master

The Project Manager

The COO, CEO and CTO

 The Product Owner

Correct
The Product Owner can tell the Developers what to work on via the Product
Backlog.

The Product Owner manages...

The Product Backlog

The Project

The Scrum Team

The Developers

Correct
The Product Owner is also accountable for effective Product Backlog
management
– The Scrum Guide

Ordering the Product Backlog is part of Product Backlog refinement

False
 True

Correct
Product Backlog refinement is the act of breaking down and further defining
Product Backlog items into smaller more precise items. This is an ongoing
activity to add details, such as a description, order, and size. Attributes often
vary with the domain of work.
– The Scrum Guide

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

True

False

Correct
In Sprint Planning, the whole Scrum Team collaborates to define a Sprint Goal
that communicates why the Sprint is valuable to stakeholders.

A release is mandatory at the end of every Sprint.

True

False
 Correct
The moment a Product Backlog item meets the Definition of Done, an
Increment is born.
Multiple Increments may be created within a Sprint. The sum of the
Increments is presented at the Sprint Review thus supporting empiricism.
However, an Increment may be delivered to stakeholders prior to the end of
the Sprint. The Sprint Review should never be considered a gate to releasing
value.

Why might it be important to have clearly defined Acceptance Criteria for a Product
Backlog item?

It enables the Product Owner to change requirements during the Sprint.

It makes it easier for the Scrum Master to manage the team.

It provides a common understanding of what is to be built.

It allows the Developers to know who will be testing their work.

Correct
Clearly defined Acceptance Criteria provide a common understanding of
what is to be built.

A company has two products. Which of the following is an acceptable way of forming
Scrum teams?

There should be a Chief Product Owner and one Product Owner for each
product
 There must be a single Product Owner across all products

There should be one Product Owner supported by a Junior Product

Owner

There must be a single Product Owner for each product

Correct
If Scrum Teams become too large, they should consider reorganizing into
multiple cohesive Scrum Teams, each focused on the same product.
Therefore, they should share the same Product Goal, Product Backlog, and
Product Owner.
– The Scrum Guide

When may the Product Backlog be refined?

Anytime as needed

During Sprint Planning

At the end of Sprint Planning

Right before the Sprint Review

Correct
 Product Backlog items can be updated at any time by the Product Owner or
at the Product Owner’s discretion. Product Backlog refinement is an ongoing
process.

Product Backlog management includes

Select all that apply.

Ensuring that the Product Backlog is transparent, visible and

understood

Ordering Product Backlog items

Creating and clearly communicating Product Backlog items

Developing and explicitly communicating the Product Goal

Correct
The Product Owner is also accountable for effective Product Backlog
management, which includes:
Developing and explicitly communicating the Product Goal;
Creating and clearly communicating Product Backlog items;
Ordering Product Backlog items; and,
Ensuring that the Product Backlog is transparent, visible and understood.
– The Scrum Guide

Although they may vary with the domain of work, Product Backlog items often have
the following attributes

Select all that apply.

 Description

Size

Order

Correct
Product Backlog refinement is the act of breaking down and further defining
Product Backlog items into smaller more precise items. This is an ongoing
activity to add details, such as a description, order, and size. Attributes often
vary with the domain of work.
– The Scrum Guide

The Product Owner does not have to be one person, and the accountability can be
filled by a committee.

False

True

Correct
The Product Owner is one person, not a committee. The Product Owner may
represent the needs of many stakeholders in the Product Backlog. Those
wanting to change the Product Backlog can do so by trying to convince the
Product Owner.

The Product Owner is also the owner and the creator of the Definition of Done.
 False

True

Correct
The Definition of Done is created by the Scrum Team

The Definition of Done is an input to Sprint Planning

True

False

Correct
It is necessary to know the Definition of Done in order to forecast the work
for the Sprint.

The Product Owner may delegate the responsibility of sizing work to the Scrum
Master.

False

True

Incorrect
 The Developers who will be doing the work are responsible for the sizing.
The Product Owner may influence the Developers by helping them
understand and select trade-offs.

What is Product Backlog grooming?

The old and outdated name for Product Backlog refinement

A special type of Product Backlog refinement used for software

development only

Rewriting Product Backlog items to make them easier to understand

One of the Scrum events

Correct
The term “grooming” was removed from Scrum many years ago and replaced
with refinement. This was due to negative connotations with the word in
many parts of the world.

When should the Product Owner provide feedback on the work that the Developers
are doing?

Whenever feedback can help to avoid waste.

During the Daily Scrum.

During Product Backlog Refinement.

 During the Sprint Review.

Correct
Developers can ask for feedback and the Product Owner can provide
feedback on the work at anytime in order to reduce risk and avoid waste.

Which of the following is not allowed by Scrum?

Release planning

Refactoring

Velocity tracking

Hardening Sprints

Correct
Each Sprint should result in a Done Increment. If hardening Sprints to get
work “really Done” are planned and required then the Sprints before this
point were not really Sprints.

What is an emergent, ordered list of what is needed to improve the product?

The Increment

The Sprint Backlog

 The product vision

The Product Backlog

The Sprint Retrospective

Correct
The Product Backlog is an emergent, ordered list of what is needed to
improve the product.

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

True

False

Correct
A Scrum Team must only work on a single Product Goal at any time in order
to maintain focus.

Select the timebox for each Scrum event

Sort elements
 Sprint 4 hours or less
Review

Daily 15 minutes
Scrum

Sprint
8 hours or less
Planning

Sprint
3 hours or less
Retrospective

Correct
Sprint Planning is timeboxed to a maximum of eight hours
The Daily Scrum is a 15-minute event
The Sprint Review is timeboxed to a maximum of four hours
The Sprint Retrospective is timeboxed to a maximum of three hours

Beliefs in what is valuable are merely assumptions until they are validated by
customers.

True

False

Correct
Beliefs in what is valuable are merely assumptions until they are validated by
customers.
A Product Owner is

A committee

1 person

Correct
The Product Owner is one person, not a committee.
– The Scrum Guide

The entire Scrum Team is accountable for creating a valuable, useful Increment
every Sprint.

True

False

Correct
The entire Scrum Team is accountable for creating a valuable, useful
Increment every Sprint.

What is the main role of the Product Owner at the Daily Scrum?

To track progress towards the Sprint Goal.

To discuss changes to the Product Backlog with the Developers.

 To assign tasks to the Developers for the day.

The Product Owner does not have a defined role in the Daily Scrum.

Correct
The Daily Scrum is an event for the Developers. The Product Owner does not
have a defined role in the Daily Scrum, but might attend if the Developers
request it.

How should the Product Owner respond when the Developers ask for clarification
about a Product Backlog item during the Sprint?

The Product Owner should provide the requested clarification or enable

the Developers to get it themselves

The Product Owner should defer to the Scrum Master for providing the
clarification.

The Product Owner should wait until the next Sprint Planning to provide
the clarification.

The Product Owner should tell the Developers to figure it out themselves.

Correct
The Product Owner should be available to provide clarification and further
detail about Product Backlog items to the Developers.

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

 False

True

Correct
A demonstration is 1 way to inspect the Increment. It is not the only way. The
Sprint Review is a working session and the Scrum Team should avoid limiting
it to a presentation.

The purpose of the Sprint Review is...

To inspect the outcome of the Sprint and determine future adaptations

To show Stakeholders work that is done and work that is near to

completion

To check what was done and not done during the Sprint

To review the status of the Project

Correct
The purpose of the Sprint Review is to inspect the outcome of the Sprint and
determine future adaptations.
– The Scrum Guide

The Sprint Review is the only time when stakeholder feedback is captured.
 False

True

Correct
Stakeholder feedback can be captured at any time

Evidence-Based Management is ...

A management framework to ensure the delivery of maximum value

A framework that organisations can use to help them measure, manage,

and increase the value they derive from their product delivery

A mandatory practice for Product Owners using Scrum

A methodology that organisations can use to help them increase the value
of their product

Correct
Evidence-Based Management is a framework that organisations can use to
help them measure, manage, and increase the value they derive from their
product delivery

Stakeholders may include representatives from Human Resources

 False

True

Correct
Stakeholders may include representatives from Human Resources or any
other department/role in an organisation.

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

False

True

Correct
Whilst this may be desirable, it is impossible when doing complex work.

The Product Owner is also the owner and the creator of the Definition of Done.

FALSE

TRUE

Correct
 The Definition of Done is created by the Squad

A Product Backlog is never complete

False - A complete Product Backlog should be created before starting the

first Sprint

True - As long as a product exists, its Product Backlog also exists

Correct
As long as there is a product there will be a Product Backlog containing work
that may be carried out in future.

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

False

True

Correct
A key measure of success for the Product Owner is a high value product

The Product Owner can delegate to the Developers the creation of Product Backlog
items.

False
 True

Correct
The Product Owner is also accountable for effective Product Backlog
management. The Product Owner may do this or may delegate the
responsibility to others. Regardless, the Product Owner remains
accountable.

Who is accountable for the contents of the Product Backlog?

The Product Owner

The Scrum Master

The Developers

The stakeholders

Correct
The Product Owner is accountable for managing the Product Backlog,
including adding, removing, and updating items. The Product Backlog reflects
the Product Owner’s vision and goals for the product.

Common Product Backlog item attributes are:

Commitment, courage, focus, openness and respect

 Description, order, and size

Complexity, agility, openness, commitment

Velocity, Risk, Ownership

Correct
Description, order, and size are common attributes of a Product Backlog item
although attributes often vary with the domain of work.

What happens when a Sprint Goal becomes obsolete?

The Product Owner, the Developers, and the Scrum Master negotiate
what to do next.

The Sprint may be cancelled by the Product Owner.

The Sprint continues without any changes.

The Developers decide what to do next.

Correct
The Product Owner has the authority to cancel a Sprint if the Sprint Goal
becomes obsolete, although this is generally a rare occurance.

Developers should be set stretch goals by the Product Owner as part of Sprint
Planning
 False

True

Correct
A realistic forecast should be created in Sprint Planning.

The Product Backlog may be reordered following input from Stakeholders at the
Sprint Review

False

True

Correct
During the [Sprint Review] event, the Scrum Team and stakeholders review
what was accomplished in the Sprint and what has changed in their
environment. Based on this information, attendees collaborate on what to do
next. The Product Backlog may also be adjusted to meet new opportunities.
– The Scrum Guide

Who manages the Sprint Backlog?

The Developers

The Product Owner

 The Scrum Master

The Scrum Team

Correct
Developers are always accountable for:
Creating a plan for the Sprint, the Sprint Backlog;
– The Scrum Guide

A Product Backlog item is Done. What does it mean in Scrum?

The entire feature is complete

All tasks identified for the item are Done

The item is ready for user acceptance testing

No work left based on the Definition of Done

Correct
The Definition of Done is a formal description of the state of the Increment
when it meets the quality measures required for the product.
The moment a Product Backlog item meets the Definition of Done, an
Increment is born.

The Sprint Backlog is owned by the:

 The Scrum Team.

The Product Owner.

The Developers.

The Scrum Master.

Correct
The Sprint Backlog is the set of Product Backlog items selected by the
Developers and their plan for delivering the work.

Product Backlog refinement is...

Carried out once per Sprint

An ongoing process in which the Product Owner and the Developers

collaborate

The concern of the Product Owner

A Scrum event

Correct
 Product Backlog refinement is an ongoing process in which the Product
Owner and the Developers collaborate

What is the Product Goal?

It is a high-level summary of the project scope.

It is the immediate goal that the Developers aims to achieve in the current
Sprint.

It is a long-term objective for the Scrum Team to achieve.

It is the daily objective that needs to be achieved.

Correct
The Product Goal in Scrum is a long-term objective for the Scrum Team. It
provides a direction and sets the expectation of what is to be achieved.

A new Increment must be available …...

Whenever the user acceptance testing is complete

By the end of each Sprint, before the Sprint Review

Before each planned release

Every 2 Sprints
 When the Scrum Master or the Product Owner asks for it

Correct
An Increment must be available by the start of the Sprint Review

Why does Scrum require the Product Backlog to be ordered rather than prioritised?

Scrum requires both order and priority

Order and priority are always the same thing

Order is better than chaos

Multiple PBI's can have the same priority. The can only be one position
in the Product Backlog when it comes to order.

Correct
Multiple Product Backlog items can have the same priority whereas there
can only be one order in a Product Backlog. Order ensures that it is clear
what the Scrum Team will work on first. Prioritisation may not make this as
transparent.

Who can add items to the Product Backlog?

Only the Product Owner or the Developers

 Only the Scrum Master

Anyone, but the Product Owner remains accountable for the Product
Backlog

Only the Developers

Correct
Anyone can propose a new item for the Product Backlog. Only the Product
Owner is accountable for the Product Backlog.

Stakeholders may not talk to the Developers during a Sprint

True

False

Correct
Stakeholders can (and probably should) talk Developers during a Sprint
about work relating to the Sprint Goal.

Who must ensure the Product Backlog is refined to a state that it is ready?

Stakeholders

The Product Owner

 The Developers

The Business Analyst

Correct
The Product Owner is also accountable for effective Product Backlog
management. This would include ensuring it has been refined. In practice, the
Scrum Team will collaborate the refine the Product Backlog.

Sprints help the Scrum Team to limit work-in-progress.

True

False

Correct
The Sprint helps the Scrum Team to limit work in progress. In Sprint Planning
the team plans enough work for 1 Sprint only.

A product could be a service

True

False

Correct
 A product could be a service, a physical product, or something more abstract.

Awareness of which of the following may be required for a Product Owner to

maximize value?

Select all that apply.

Customer feedback

Unit test results

Scrum Team velocity

Product vision

Correct
The product vision (while is not mandatory in Scrum) describes the purpose
of the product. Customer and user feedback may help understand value.
Velocity is not directly connected to value, and the results of unit tests is a
technical matter that Developers may need to pay attention to.

SCRUM stands for

Self-organising Collaborative & Reflective Universal Method

Safe Controlled Response Under Management

Nothing. It is not an acronym

 Super Creative Really Useful Method

Correct
Scrum is not an acronym and never has been. In some early papers, it was
written as SCRUM and this has stuck around and served to confuse some
people.

When is the Scrum Team allowed to interact with the stakeholders?

The Sprint Retrospective

The Sprint Review

Anytime where it will help the Scrum Team deliver value

The Daily Scrum

Correct
The Scrum Team may interact with the stakeholders anytime when it is
appropriate and helpful.

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

False
 True

Correct
The Product Owner should have an understanding of the potential market
for the product

The Product Owner must ensure that enough Product Backlog items are selected at
the Sprint Planning event in order to satisfy the stakeholders.

False

True

Correct
Through discussion with the Product Owner, the Developers select items
from the Product Backlog to include in the current Sprint.

Cancelling a Sprint is

Something we should do whenever we hit problems

Something we must never do

A common practice that should be used regularly

 Disruptive and wasteful

Correct
Cancelling a Sprint is disruptive and causes waste. We only do it when the
Sprint Goal becomes obsolete.

The Product Owner must attend the Sprint Retrospective

True

False

Correct
The Scrum Team attends the Sprint Retrospective. The Product Owner is
part of the Scrum Team.