scrum PSPO-I Exam Questions

Questions for the PSPO-I were updated on : Dec 01 ,2025

Page 1 out of 12. Viewing questions 1-15 out of 178

Question 1

How should a Scrum Team deal with non-functional requirements?
(choose the best answer)

  • A. Manage them during the Integration Sprint prior to the Release Sprint.
  • B. Assign them to the lead developers on the team.
  • C. Ensure every Increment meets them.
  • D. Make sure the release department understands these requirements, but it is not the Scrum Team's responsibility.
Answer:

C

User Votes:
A
50%
B
50%
C
50%
D
50%

Explanation:
In Scrum, non-functional requirements are part of the quality and completeness criteria for the
product. They should be incorporated into the Definition of Done, ensuring that each Increment
meets these requirements, making it potentially shippable and usable by stakeholders .

Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 2

Which three of the following are feedback loops in Scrum?
(choose the best three answers)

  • A. Sprint Review.
  • B. Refinement Meeting.
  • C. Daily Scrum.
  • D. Sprint Retrospective.
  • E. Release Planning.
Answer:

ACD

User Votes:
A
50%
B
50%
C
50%
D
50%
E
50%

Explanation:
In Scrum, feedback loops are essential mechanisms that allow for inspection and adaptation at
regular intervals. The three feedback loops from the options provided are:
Sprint Review (A): This is a feedback loop that occurs at the end of the Sprint to inspect the
Increment and adapt the Product Backlog if needed. It involves stakeholders and provides an
opportunity to inspect the progress towards the Product Goal.
Daily Scrum ©: This is a daily feedback loop for the Developers to synchronize their work and plan for
the next 24 hours. It helps in identifying challenges and creating a plan to achieve the Sprint Goal.
Sprint Retrospective (D): This feedback loop occurs after the Sprint Review and before the next Sprint
Planning. It is an opportunity for the Scrum Team to inspect itself and create a plan for improvements
to be enacted during the next Sprint.
The Refinement Meeting (B) is not considered a feedback loop but rather an ongoing process of
adding details to Product Backlog items. Release Planning (E) is not a formal event in Scrum and thus
not a prescribed feedback loop.
Reference: The Scrum Guide and the Professional Scrum Product Owner™ (PSPO I) materials describe
these events as integral parts of the Scrum framework that serve as feedback loops1

Discussions
vote your answer:
A
B
C
D
E
0 / 1000

Question 3

One of the Scrum events is the Daily Scrum. What are two intended outcomes of the Daily
Scrum?
(choose the best two answers)

  • A. An update of completed tasks and of the remaining work so the Scrum Master can plan the next day.
  • B. An updated Scrum board to make Sprint progress transparent for the stakeholders.
  • C. A status report for the upper management indicating what each individual has done, will be doing, and what is impeding him/her.
  • D. Identification of impediments that may prevent the Developers from achieving the Sprint Goal.
  • E. A shared understanding of the most important work to be undertaken next to achieve the best possible progress toward the Sprint goal.
Answer:

DE

User Votes:
A
50%
B
50%
C
50%
D
50%
E
50%

Explanation:
The Daily Scrum is a 15-minute event for the Developers to synchronize activities and create a plan
for the next 24 hours. This meeting is designed to inspect progress toward the Sprint Goal and adapt
the Sprint Backlog as necessary. The intended outcomes are to identify any impediments that may
prevent the Developers from achieving the Sprint Goal (D) and to foster a shared understanding
among the Developers of what work is most important to undertake next in order to make the best
possible progress toward the Sprint Goal (E). It is not a status update meeting for the Scrum Master
or upper management, nor is it primarily about updating Scrum boards for stakeholder transparency.
Reference: The Scrum Guide and the resources provided by Scrum.org on the Daily Scrum emphasize
these outcomes as essential to the effectiveness of the Daily Scrum event12
.

Discussions
vote your answer:
A
B
C
D
E
0 / 1000

Question 4

At the end of a Sprint, a Product Backlog item worked on during the Sprint does not meet the
Definition of Done. What two things should happen with the undone Product Backlog item?
(choose the best two answers)

  • A. Review the item, add the done part of the estimate to the velocity and create a Story for the remaining work.
  • B. If the stakeholders agree, the Product Owner can accept it and release it to the users.
  • C. Do not include the item in the Increment this Sprint.
  • D. Put it on the Product Backlog for the Product Owner to decide what to do with it.
Answer:

CD

User Votes:
A
50%
B
50%
C
50%
D
50%

Explanation:
According to the Scrum Guide, if a Product Backlog item does not meet the Definition of Done, it
should not be included in the Increment for the Sprint1
. The item is considered unfinished and
therefore cannot be part of the Increment that may be released or presented as ‘Done’.
The undone
work should be re-estimated and put back on the Product Backlog for the Product Owner to prioritize
for future Sprints2
. This ensures transparency and maintains the integrity of the Increment’s quality.
Reference: The Scrum Guide provides clear guidance on handling undone work and emphasizes the
importance of the Definition of Done as a quality standard for the Increment1
.
The Professional
Scrum Product Owner™ (PSPO I) materials also align with this approach, underscoring the Product
Owner’s role in managing the Product Backlog and ensuring that only ‘Done’ items are considered
for release

Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 5

When Developers are having trouble delivering an Increment because they do not understand a
functional requirement, what should they do?
(choose the best answer)

  • A. Partially complete the functionality, and discuss the remaining work at the Sprint Review.
  • B. Add a specialist to the Development Team.
  • C. Collaborate with the Product Owner to determine what is possible and acceptable.
  • D. Defer the work to a more appropriate Sprint.
Answer:

C

User Votes:
A
50%
B
50%
C
50%
D
50%

Explanation:
In Scrum, when Developers encounter difficulties in delivering an Increment due to a lack of
understanding of a functional requirement, they should collaborate with the Product Owner. This
collaboration is crucial as the Product Owner has the responsibility to clarify the items in the Product
Backlog and to ensure that the Development Team understands the work to be done. The Product
Owner is accountable for maximizing the value of the product and must work with the Development
Team to find out what is feasible and acceptable for the Increment being developed. This approach
aligns with the Scrum principle of collaboration and self-organization within the Scrum Team.
Reference: The Scrum Guide and the Professional Scrum Product Owner™ (PSPO I) materials
emphasize the importance of collaboration between the Product Owner and the Development Team
to ensure a clear understanding of the Product Backlog items and to optimize the value of the work
being done

Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 6

Who has the final decision about the order of items in the Product Backlog?
(choose the best answer)

  • A. The Scrum Master.
  • B. The Stakeholders.
  • C. The Scrum Team.
  • D. The Developers.
  • E. The Product Owner.
Answer:

D

User Votes:
A
50%
B
50%
C
50%
D
50%
E
50%

Explanation:
In Scrum, the Product Owner is responsible for maximizing the value of the product resulting from
the work of the Development Team. One of the primary ways the Product Owner does this is by
managing the Product Backlog, which includes clearly expressing Product Backlog items, ordering the
items to best achieve goals and missions, and ensuring that the Product Backlog is visible,
transparent, and clear to all. This means that the Product Owner has the final authority on the order
of items in the Product Backlog, as they are best positioned to understand the strategic and market
value of the work to be done.
Reference: The Scrum Guide and the Professional Scrum Product Owner™ (PSPO I) study materials,
specifically the sections on ‘Managing Products with Agility’ and ‘Understanding and Applying the
Scrum Framework’, which outline the accountabilities of the Product Owner in managing the Product
Backlog

Discussions
vote your answer:
A
B
C
D
E
0 / 1000

Question 7

True or False: A high-performance Scrum Team ensures that each Increment is complete by running a
Release Sprint.

  • A. True
  • B. False
Answer:

B

User Votes:
A
50%
B
50%

Explanation:
The concept of a “Release Sprint” is not found in the Scrum Guide or the Professional Scrum Product
Owner™ (PSPO I) materials. Scrum does not require a separate Sprint for releasing an Increment.
According to Scrum, each Increment must be usable and potentially releasable at the end of every
Sprint, which means the product should be in a releasable state irrespective of whether the Product
Owner decides to release it or not. The idea of a Release Sprint is not aligned with Scrum’s principle
of continuous delivery and the definition of “Done”.
Reference: The Scrum Guide and the Professional Scrum Product Owner™ (PSPO I) study materials
emphasize the importance of the Increment being releasable after every Sprint without the need for
an additional Release Sprint12
.

Discussions
vote your answer:
A
B
0 / 1000

Question 8

True or False: To get started in terms of what to build, Scrum requires no more than a Product
Owner with enough ideas for a first Sprint, Developers to implement those ideas, and a Scrum
Master to help guide the process.

  • A. True
  • B. False
Answer:

A

User Votes:
A
50%
B
50%

Explanation:
Scrum is a framework that is designed to be lightweight and easy to adopt. To get started with
Scrum, the minimal requirements are indeed a Product Owner with enough ideas for a first Sprint, a
Development Team to implement those ideas, and a Scrum Master to facilitate and guide the
process. This aligns with the core principles of Scrum, which emphasize self-organization,
collaboration, and the ability to deliver increments of value quickly and frequently.
Reference: The Scrum Guide outlines the roles within a Scrum Team and the necessity of having a
Product Backlog with enough ‘Ready’ items to fill a Sprint.
The guide also emphasizes the importance
of having a clear definition of ‘Done’ before starting the first Sprint

Discussions
vote your answer:
A
B
0 / 1000

Question 9

The Scrum Master observes the Product Owner struggling with ordering the Product Backlog.
What is an appropriate action for the Scrum Master to take?
(choose the best answer)

  • A. Offer the Product Owner help in understanding that the goal of ordering the Product Backlog is to maximize value.
  • B. Suggest that the Developers order the Product Backlog to be sure that it is a feasible ordering of work.
  • C. Encourage the Product Owner to work with the Developers to see which items technically are fastest to implement.
  • D. Suggest the Product Owner extend the Sprint, so he can have more time to order the Product Backlog.
  • E. Present the Product Owner with an ordered Product Backlog to use.
Answer:

A

User Votes:
A
50%
B
50%
C
50%
D
50%
E
50%

Discussions
vote your answer:
A
B
C
D
E
0 / 1000

Question 10

Which of the following are true about the length of the Sprint?
(choose the best answer)

  • A. The length of the Sprint should be proportional to the work that is done in between Sprints.
  • B. All Sprints must be one month or less.
  • C. Sprint length is determined during Sprint Planning, and should hold the time it will take to build the planned features in the upcoming Sprint, but does not include time for any testing.
  • D. Sprint length is determined during Sprint Planning, and should be long enough to make sure the Scrum Team can deliver what is to be accomplished in the upcoming Sprint
Answer:

B

User Votes:
A
50%
B
50%
C
50%
D
50%

Explanation:
The Scrum Guide states that “Sprints are the heart of Scrum where ideas are turned into value”. It
also states that “Sprints have consistent durations throughout a development effort. A new Sprint
starts immediately after the conclusion of the previous Sprint”. Furthermore, it states that “Sprints
are limited to one calendar month. When a Sprint’s horizon is too long the definition of what is being
built may change, complexity may rise, and risk may increase”. Therefore, the correct answer is B.
The other options are not acceptable, as they contradict the Scrum principles of empiricism, self-
organization, and adaptation.
Reference:
The Scrum Guide
, section 3.1. Sprints
Professional Scrum Product Owner I (PSPO I) Learning Path
, section 2.2. The Product Owner and the
Sprint

Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 11

User documentation is part of your Definition of Done. However, there are not enough technical
writers for all teams. Your Scrum Team does not have a technical writer. What should the
Scrum Team do?
(choose the best answer)

  • A. The Developers on the Scrum Team should write the user documentation.
  • B. Wait until you have a technical writer on your Scrum Team to take care of this.
  • C. Form a separate team of technical writers that will work on an on-demand basis for the various Product Owners. Work order will be first in, first out.
  • D. Let the user documentation remain undone and accumulate until after the last development Sprint. It will then be done by any available technical writers.
Answer:

A

User Votes:
A
50%
B
50%
C
50%
D
50%

Explanation:
The Scrum Guide states that “the Developers are the people in the Scrum Team that are committed
to creating any aspect of a usable Increment each Sprint”. It also states that “the Developers can do
the work of any other role on the Scrum Team, as long as accountability is met”. Therefore, the
Developers on the Scrum Team should write the user documentation, as it is part of the Definition of
Done and the work needed to deliver a “Done” Increment. The other options are not acceptable, as
they violate the Scrum values of commitment, focus, and respect, and they create dependencies,
delays, and waste.
Reference:
The Scrum Guide
, section 2.2. Developers
Professional Scrum Product Owner I (PSPO I) Learning Path
, section 2.3. The Product Owner and the
Definition of Done
Professional Scrum Product Owner I (PSPO I) Sample Questions
, question 12

Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 12

A Scrum Team is a cohesive unit of professionals that consists of which of the following?
(choose the best three answers)

  • A. One Product Owner.
  • B. Developers.
  • C. Customers.
  • D. One Scrum Master.
  • E. Users.
Answer:

ABD

User Votes:
A
50%
B
50%
C
50%
D
50%
E
50%

Explanation:
The Scrum Guide defines a Scrum Team as “a cohesive unit of professionals focused on one objective
at a time, the Product Goal”. It also states that “the Scrum Team consists of one Scrum Master, one
Product Owner, and Developers”. Therefore, the correct answer is A, B, and D. Customers and users
are not part of the Scrum Team, but they are important stakeholders who provide feedback and input
to the Product Owner and the Developers.
Reference:
The Scrum Guide
, section 2.1. The Scrum Team
Professional Scrum Product Owner I (PSPO I) Learning Path
, section 1.1. The Scrum Team
Professional Scrum Product Owner I (PSPO I) Sample Questions
, question 1

Discussions
vote your answer:
A
B
C
D
E
0 / 1000

Question 13

What may be included in the Sprint Backlog?
(choose the best answer)

  • A. User Stories.
  • B. Tasks.
  • C. Use Cases.
  • D. Tests.
  • E. Any of the above (or others) which are a decomposition of the selected Product Backlog items.
Answer:

E

User Votes:
A
50%
B
50%
C
50%
D
50%
E
50%

Explanation:
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for
delivering the product Increment and realizing the Sprint Goal1
.
The Sprint Backlog is a forecast by
the Developers about what functionality will be in the next Increment and the work needed to
deliver that functionality into a “Done” Increment1
.
The Sprint Backlog makes visible all the work
that the Developers identify as necessary to meet the Sprint Goal1
. The Sprint Backlog can include
any items that the Developers deem necessary to achieve the Sprint Goal, such as user stories, tasks,
use cases, tests, or others.
The Sprint Backlog is a plan with enough detail that changes in progress
can be understood in the Daily Scrum1
.
Reference:
The Scrum Guide
, section 3.3. Sprint Backlog
Professional Scrum Product Owner I (PSPO I) Learning Path
, section 2.2. The Product Owner and the
Sprint
Professional Scrum Product Owner I (PSPO I) Sample Questions
, question 11

Discussions
vote your answer:
A
B
C
D
E
0 / 1000

Question 14

Which of these may a Scrum Team deliver at the end of a Sprint?
(choose the best answer)

  • A. Failing unit tests, to identify acceptance tests for the next Sprint.
  • B. A single document, if that is what management asked for.
  • C. An Increment of software with minor known bugs in it.
  • D. A valuable, useful Increment that meets the Definition of Done.
Answer:

D

User Votes:
A
50%
B
50%
C
50%
D
50%

Explanation:
The Scrum Guide states that “the Increment is the sum of all the Product Backlog items completed
during a Sprint and the value of the increments of all previous Sprints”. It also states that “at the end
of a Sprint, the new Increment must be ‘Done’, which means it must be in useable condition and
meet the Scrum Team’s definition of ‘Done’”. Therefore, the Scrum Team must deliver a valuable,
useful Increment that meets the Definition of Done at the end of a Sprint. The other options are not
acceptable, as they do not meet the criteria of being valuable, useful, or done.
Reference:
The Scrum Guide
, section 3.4. Increment
Professional Scrum Product Owner I (PSPO I) Learning Path
, section 2.1. The Product Owner and the
Development Team
Professional Scrum Product Owner I (PSPO I) Sample Questions
, question 10

Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 15

When should a Sprint Goal be created?
(choose the best answer)

  • A. A Sprint Goal is not mandatory in Scrum.
  • B. It should have been created in the previous Sprint during Product Backlog refinement.
  • C. It must be established before Sprint Planning in order to begin planning.
  • D. During Sprint Planning.
  • E. At any time during the Sprint.
Answer:

D

User Votes:
A
50%
B
50%
C
50%
D
50%
E
50%

Explanation:
The Sprint Goal is a short statement that gives the Sprint a purpose, direction, and focus. It is created
by the entire Scrum Team during Sprint Planning, based on the Product Owner’s draft and the
Developers’ input. The Sprint Goal is then added to the Sprint Backlog and guides the Developers’
work during the Sprint.
Reference:
What is a Sprint Goal?
The Sprint Goal
How to Write and Use a Sprint Goal (With 5 Templates)

Discussions
vote your answer:
A
B
C
D
E
0 / 1000
To page 2