scrum psm-i practice test

Professional Scrum Master I

Last exam update: Dec 25 ,2025
Page 1 out of 18. Viewing questions 1-15 out of 269

Question 1

When many Scrum Teams are working on the same product, should all of their increments be
integrated every Sprint?

  • A. Yes, but only for Scrum Teams whose work has dependencies.
  • B. Yes, otherwise the Product Owners (and stakeholders) may not be able to accurately inspect what is done.
  • C. No, each Scrum Team stands alone.
  • D. No, that is far too hard and must be done in a hardening Sprint.
Mark Question:
Answer:

B


Explanation:
The correct answer is B, because the Scrum Guide 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’. An increment is a body of inspectable, done work that supports empiricism at
the end of the Sprint. The increment is a step toward a vision or goal.” Therefore, all the increments
from different Scrum Teams working on the same product should be integrated every Sprint to
enable inspection and adaptation by the Product Owner and stakeholders.

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 2

When can a Development Team cancel a Sprint?

  • A. It can’t. Only Product Owners can cancel Sprints.
  • B. When functional expectations are not well understood.
  • C. When the Product Owner is absent too often.
  • D. When the selected Product Backlog items for the Sprint become unachievable.
  • E. When a technical dependency cannot be resolved.
Mark Question:
Answer:

A


Explanation:
The correct answer is A, because the Scrum Guide states that “a Sprint can be cancelled before the
Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or
she may do so under influence from the stakeholders, the Development Team, or the Scrum Master.”
Therefore, a Development Team cannot cancel a Sprint by itself.

User Votes:
A
50%
B
50%
C
50%
D
50%
E
50%
Discussions
vote your answer:
A
B
C
D
E
0 / 1000

Question 3

Which output from Sprint Planning provides the Development Team with a target and overarching
direction for the Sprint?

  • A. The Sprint Backlog.
  • B. The Sprint Goal
  • C. The release plan.
  • D. Sprint Review minutes.
Mark Question:
Answer:

B


Explanation:
The correct answer is B, because the Scrum Guide states that “the Sprint Goal is an objective set for
the Sprint that can be met through the implementation of Product Backlog. It provides guidance to
the Development Team on why it is building the Increment.” Therefore, the Sprint Goal provides the
Development Team with a target and overarching direction for the Sprint.

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 4

How should a Development Team deal with non-functional requirements?

  • A. Ensure every Increment meets them.
  • B. Make sure the release department understands these requirements, but it is not the Development Team’s responsibility.
  • C. Handle them during the Integration Sprint preceding the Release Sprint.
  • D. Assign them to the lead developers on the team.
Mark Question:
Answer:

A


Explanation:
The correct answer is A, because the Scrum Guide states that “the definition of ‘Done’ is a formal
description of the state of the Increment when it meets the quality measures required for the
product.” Therefore, non-functional requirements should be part of the definition of ‘Done’ and
ensure every Increment meets them.

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 5

When is a Sprint over?

  • A. When the Product Owner says it is done.
  • B. When all Product Backlog items meet their definition of “Done”.
  • C. When all the tasks are completed.
  • D. When the time-box expires.
Mark Question:
Answer:

D


Explanation:
The correct answer is D, because the Scrum Guide states that “a Sprint is a container for all other
events. Each event in Scrum is a formal opportunity to inspect and adapt something. These events
are specifically designed to enable critical transparency and inspection. Failure to include any of
these events results in reduced transparency and is a lost opportunity to inspect and adapt.”
Therefore, a Sprint is over when its time-box expires, regardless of whether all Product Backlog items
or tasks are completed or not.

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 6

Scrum has a role called “Project Manager”.

  • A. True
  • B. False
Mark Question:
Answer:

B


Explanation:
The correct answer is B, because there is no role called “Project Manager” in Scrum. The Scrum
Guide states that “Scrum recognizes no titles for Development Team members other than Developer,
regardless of the work being performed by the person; there are no exceptions to this rule.”
Therefore, Scrum has only three roles: Product Owner, Scrum Master, and Developer.

User Votes:
A
50%
B
50%
Discussions
vote your answer:
A
B
0 / 1000

Question 7

What are two good ways for the Development Team to make non-functional requirements visible?
(Choose two.)

  • A. Put them on a separate list on the Scrum board, available for all to see.
  • B. Add them to the Product Backlog and keep the Product Owner posted on the expected effort.
  • C. Run the integration and regression tests before the end of the Sprint, and capture the open work for the Sprint Backlog of the next Sprint.
  • D. Add them to the definition of “Done” so the work is taken care of every Sprint.
Mark Question:
Answer:

B,D


Explanation:
The correct answers are B and D, because adding non-functional requirements to the Product
Backlog and keeping the Product Owner posted on the expected effort helps prioritize and plan them
in alignment with the product vision and goals. Additionally, adding non-functional requirements to
the definition of ‘Done’ ensures that they are met every Sprint and do not accumulate technical debt.
Reference:
Suggested Reading for Professional Scrum Master™ I

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 8

How much time is required after a Sprint to prepare for the next Sprint?

  • A. The break between Sprints is time-boxed to 1 week for 30 day Sprints, and usually less for shorter sprints.
  • B. Enough time for the requirements for the next Sprint to be determined and documented.
  • C. Enough time for the Development team to finish the testing from the last Sprint.
  • D. None. A new Sprint starts immediately following the end of the previous Sprint.
  • E. All of the above are allowed depending on the situation.
Mark Question:
Answer:

D


Explanation:
The correct answer is D, because there is no gap between Sprints in Scrum. The Scrum Guide states
that “a new Sprint starts immediately after the conclusion of the previous Sprint.” Therefore, there is
no time required after a Sprint to prepare for the next Sprint.

User Votes:
A
50%
B
50%
C
50%
D
50%
E
50%
Discussions
vote your answer:
A
B
C
D
E
0 / 1000

Question 9

In the Sprint Planning meeting, the Product Owner and the Development Team were unable to reach
a clear understanding about the highest order Product Backlog items. Because of this, the
Development Team couldn’t figure out how many Product Backlog items it could forecast for the
upcoming Sprint. They were able to agree on a Sprint Goal, however.
Which of the following two actions should the Scrum Master support? (Choose two.)

  • A. Cancel the Sprint. Send the entire team to an advanced Scrum training and then start a new Sprint.
  • B. Forecast the most likely Product Backlog items to meet the goal and create a Sprint Backlog based on a likely initial design and plan. Once the time-box for the Sprint Planning meeting is over, start the Sprint and continue to analyze, decompose, and create additional functionality during the Sprint.
  • C. Continue the Sprint Planning meeting past its time-box until an adequate number of Product Backlog items are well enough understood for the Development Team to make a complete forecast. Then start the Sprint.
  • D. Discuss in the upcoming Sprint Retrospective why this happened and what changes will make it less likely to recur.
  • E. Ask everyone to take as much time as needed to analyze the Product Backlog first, and then reconvene another Sprint Planning meeting.
Mark Question:
Answer:

B,D


Explanation:
According to the Scrum Guide1
, the Sprint Planning meeting has a time-box of eight hours or less for
a one-month Sprint. The Scrum Master ensures that the meeting is time-boxed and keeps the Scrum
Team focused on the objective. If the Development Team cannot forecast how many Product Backlog
items it can complete, it should still start the Sprint and work on the most likely items to meet the
Sprint Goal. The Sprint Backlog can be updated throughout the Sprint as more is learned. The Scrum
Master should also support the team to discuss the reasons for the lack of clarity in the Product
Backlog items and how to prevent it from happening again in the next Sprint Retrospective.
Reference:
Scrum Guide

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 answer best describes the topics covered in Sprint Planning?

  • A. What to do and who will do it.
  • B. How conditions have changed and how the Product Backlog should evolve.
  • C. What can be done and how to do it.
  • D. What went wrong in the last Sprint and what to do differently this Sprint.
  • E. Who is on the team and what team member roles will be.
Mark Question:
Answer:

C


User Votes:
A
50%
B
50%
C
50%
D
50%
E
50%
Discussions
vote your answer:
A
B
C
D
E
0 / 1000

Question 11

Which of the following is required by Scrum? (Choose all that apply.)

  • A. Sprint Retrospective.
  • B. Members must be stand up at the Daily Scrum.
  • C. Sprint Burndown Chart.
  • D. Release planning.
  • E. All of the above.
Mark Question:
Answer:

AD


Explanation:
Explanation of Correct Answer: According to the Scrum Guide1
, the only required events in
Explanation:Scrum are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. These
events enable transparency, inspection, and adaptation. The other options are not mandatory in
Scrum, although they may be useful in some contexts.
Reference:
Scrum Guide

User Votes:
A
50%
B
50%
C
50%
D
50%
E
50%
Discussions
vote your answer:
A
B
C
D
E
0 / 1000

Question 12

What is the purpose of a Sprint Review?

  • A. To take time to judge the validity of the project.
  • B. To inspect the product increment with the stakeholders and collect feedback on next steps.
  • C. To review the Scrum Team’s activities and processes during the Sprint.
  • D. To build team sprint.
Mark Question:
Answer:

B


User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 13

Who determines when it is appropriate to update the Sprint Backlog during a Sprint?

  • A. The Scrum Team.
  • B. The Product Owner.
  • C. The Developers.
  • D. The Project Manager.
Mark Question:
Answer:

C


User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000

Question 14

Who must attend the Daily Scrum?

  • A. The Scrum Master and Product Owner.
  • B. The Development Team.
  • C. The Development Team and Product Owner.
  • D. The Scrum Team.
  • E. The Development Team and Scrum Master.
Mark Question:
Answer:

D


Explanation:
According to the Scrum Guide1
, the Daily Scrum is an event for the Developers of the Scrum Team.
The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint
Backlog as necessary, adjusting the upcoming planned work. The Scrum Master and Product Owner
may attend as observers, but only if it is useful for the Developers.
Reference:
Scrum Guide

User Votes:
A
50%
B
50%
C
50%
D
50%
E
50%
Discussions
vote your answer:
A
B
C
D
E
0 / 1000

Question 15

When do Development Team members take ownership of a Sprint Backlog item?

  • A. At the Sprint planning meeting.
  • B. During the Daily Scrum.
  • C. Never. All Sprint Backlog Items are “owned” by the entire Development Team, even though each one may be done by an individual Development Team member.
  • D. Whenever a team member can accommodate more work.
Mark Question:
Answer:

C


Explanation:
According to the Scrum Guide1
, the Sprint Backlog is the property of the Developers and no one else
can tell them which items they should work on. The Developers can select any item from the Product
Backlog that they forecast they can complete within a Sprint. The Developers are self-organizing and
decide how to turn Product Backlog items into an Increment of value. Therefore, no one owns a
Sprint Backlog item, but the entire Development Team is accountable for it.
Reference:
Scrum Guide

User Votes:
A
50%
B
50%
C
50%
D
50%
Discussions
vote your answer:
A
B
C
D
0 / 1000
To page 2