NEW QUESTION 1
When many Scrum Teams are working on a single product, what best describes the Definition of Done? (Choose the best answer.)

• A. Each Scrum Team defines and uses its ow
• B. The differences are discussed and reconciled during a hardening Sprint.
• C. The Scrum Masters from each Scrum Team define a common Definition of Done.
• D. Each Scrum Team uses its own, but must make their definition clear to all other teams so the differences are known.
• E. All Scrum Teams must have a Definition of Done that makes their combined work potentially releasable.

Answer: D

Explanation:
According to the Scrum Guide, when many Scrum Teams are working on a single product, they must have a Definition of Done that makes their combined work potentially releasable. This ensures that there is a clear and consistent understanding of what “Done” means for the product and that there is no technical debt or unfinished work at the end of each Sprint. The other options are not valid descriptions of the Definition of Done for multiple Scrum Teams, as they either create inconsistency, confusion, or waste (such as having different definitions, discussing and reconciling differences during a hardening Sprint, or having the Scrum Masters define a common Definition of Done).

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

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

Answer: E

Explanation:
According to the Scrum Guide, the Sprint Backlog may include any items that are a decomposition of the selected Product Backlog items, such as user stories, tasks, use cases, tests, or others. The Sprint Backlog is the Developers’ plan for the Sprint, and it contains all the work that they forecast they can do to achieve the Sprint Goal and create a “Done” Increment. The other options are not valid, as they are either too specific (such as user stories or tasks) or too vague (such as tests).

NEW QUESTION 3
The time-box for a Daily Scrum?

• A. Two minutes per person.
• B. 15 minutes.
• C. 15 minutes for a 4 week sprin
• D. For shorter Sprints it is usually shorter.
• E. 4 hours.
• F. The same time of day every day.

Answer: B

Explanation:
The correct answer is B, because the time-box for a Daily Scrum is 15 minutes. The Scrum Guide states that “the Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours.”

NEW QUESTION 4
The Daily Scrum is an event that happens every day. What would be three key concerns if the frequency were to be lowered to every two or three days? (Choose three.)

• A. Opportunities to insect and adapt the Sprint Backlog are lost.
• B. Impediments are raised and resolved more slowly.
• C. The Product Owner cannot accurately report progress to the stakeholders.
• D. Too much work is spent updating the Scrum board before the meeting.
• E. The Scrum Master loses the ability to update the Gantt chart properly.
• F. The Sprint plan may become inaccurate.

Answer: ABF

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 Daily Scrum optimizes the probability that the Developers will meet the Sprint Goal. Every day, the Developers should understand how they intend to work together as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment by the end of the Sprint. If the frequency of the Daily Scrum were to be lowered to every two or three days, some key concerns would be:
Opportunities to inspect and adapt the Sprint Backlog are lost, which may result in wasted work or missed dependencies.
Impediments are raised and resolved more slowly, which may hinder the progress and quality of the work.
The Sprint plan may become inaccurate, as changes in requirements, risks, or priorities are not reflected in a timely manner.
The other options are not valid concerns, as they are not aligned with Scrum values and principles. References: Scrum Guide

NEW QUESTION 5
Which of these may a Development Team deliver at the end of a Sprint?

• A. Failing unit tests, to identify acceptance tests for the next Sprint.
• B. An increment of software with minor known bugs in it.
• C. An increment of working software that is “done”.
• D. A single document, if that is what the Scrum Master asked for.

Answer: C

Explanation:
The correct answer is C, because a Development Team should deliver an increment of working software that is “done” by the end of a Sprint. 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. 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’.”

NEW QUESTION 6
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

Explanation:
According to the Scrum Guide, a high-performance Scrum Team does not run a Release Sprint, as this is not a Scrum event. A Release Sprint is a term used to describe a Sprint that is dedicated to finalizing the product for release, such as fixing bugs, polishing features, or integrating components. This is contrary to the Scrum principle of delivering a potentially releasable Increment at the end of each Sprint, regardless of whether it is actually released or not. Therefore, the answer is false.

NEW QUESTION 7
You are the Scrum Master of a new, to be developed product. Development is going to require 45 people. What is a good first question for you to suggest the group thinks about when forming into teams?

• A. How will we make sure all teams have the right amount or expertise?
• B. What is the right mixture of senior and junior people on each team?
• C. Who are going to be the team leads?
• D. Who are the subject matter experts on each team?

Answer: A

Explanation:
The correct answer is A, because a good first question for you to suggest the group thinks about when forming into teams is how will we make sure all teams have the right amount of expertise. This question helps the group consider the cross-functionality and self-organization of the Development Teams, which are essential for delivering a potentially releasable Increment every Sprint.
References: [Suggested Reading for Professional Scrum Master™ I]

NEW QUESTION 8
True or False: An increment must be released to customers or users at the end of each sprint.

• A. True
• B. False

Answer: B

Explanation:
According to the Scrum Guide, an Increment does not have to be released to customers or users at the end of each Sprint. However, it must be in a usable condition and meet the Definition of Done. The decision to release an Increment is made by the Product Owner, based on the value and feedback obtained from stakeholders. The other option is not valid, as it implies that releasing an Increment is mandatory at the end of each Sprint.

NEW QUESTION 9
Marian is the Product Owner envisioning a project for a new release of her product. She made a projection of a release date based upon a sustained velocity of 17 completed units of work per Sprint. Over the first 3 Sprints, the average velocity was 13 for work that the Development Team estimated as 90% done. The Development Teams, feeling the need to meet the plan, figured that a velocity of 17 was within their reach.
A good way to continue is:

• A. The Development Team makes sure that all of the selected scope per Sprint is as “Done” as possible.The undone work is estimated and added to the Sprint Backlog of the next Sprint, so it doesn’t mess up the Product Backlog.
• B. Add enough people to the Development Team for the deadline to be made.
• C. The opportunity to inspect and adapt is los
• D. Opaqueness has replaced transparenc
• E. Predictability has dropped below zer
• F. The produced software is not usabl
• G. As the rules of Scrum have not been respected, it is the Scrum Master’s duty to assess whether repair is possible, or a restart with a more reliable tea
• H. If not, the Scrum Master should cancel the project.
• I. The Development Team should remind Marian to find funding for enough Release Sprints in which the remaining work can be done.

Answer: A

Explanation:
According to the Scrum Guide1, each Increment is additive to all prior Increments and thoroughly verified,
ensuring that all Increments work together. In order to provide value, the Increment must be usable. 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. Therefore, a good way to continue is for the Development Team to make sure that all of the selected scope per Sprint is as “Done” as possible. The undone work is estimated and added to the Sprint Backlog of the next Sprint, so it doesn’t mess up the Product Backlog.
References: Scrum Guide

NEW QUESTION 10
As the Development Team starts work during the Sprint, it realizes it has selected too much work to finish in the Sprint. What should it do?

• A. Inform the Product Owner at the Sprint Review, but prior to the demonstration.
• B. Find another Scrum Team to give the excess work to.
• C. As soon as possible in the Sprint, work with the Product Owner to remove some work or Product Backlog items.
• D. Reduce the definition of “Done” and get all of the Product Backlog items “Done” by the new definition.

Answer: C

Explanation:
The correct answer is C, because as soon as possible in the Sprint, the Development Team should work with the Product Owner to remove some work or Product Backlog items if they realize they have selected too much work to finish in the Sprint. The Scrum Guide states that “the Development Team may renegotiate the selected Product Backlog items with the Product Owner. If the Development Team realizes it has too much or too little work, it may renegotiate the selected Product Backlog items with the Product Owner. The Development Team may also invite other people to attend to provide technical or domain advice.”

NEW QUESTION 11
Which two ways of creating Development Teams are consistent with Scrum’s values? (Choose two.)

• A. Existing teams propose how they would like to go about organizing into the new structure.
• B. Managers personally re-assign current subordinates to new teams.
• C. Managers collaborate to assign individuals to specific teams.
• D. Bring all the developers together and let them self-organize into Development Teams.
• E. The Chief Product Owner determines the new team structures and assignments.

Answer: AD

Explanation:
The correct answers are A and D, because these ways of creating Development Teams are consistent with Scrum’s values. Allowing existing teams to propose how they would like to organize into the new structure respects their self-organization and empowerment. Bringing all the developers together and letting them self-organize into Development Teams also respects their autonomy and collaboration.
References: [Suggested Reading for Professional Scrum Master™ I]

NEW QUESTION 12
During the Sprint Retrospective a Scrum Team has identified several high priority process improvements. Which of the following statements is most accurate? (Choose the best answer.)

• A. The Scrum Team may add items to the Sprint Backlog for the next Sprint.
• B. The Scrum Team should choose at least one high priority process improvement to place in the Product Backlog.
• C. The Scrum Team should decline to add a process improvement to the Sprint Backlog when things are running smoothly.
• D. The Scrum Master selects the most important process improvement and places it in the Sprint Backlog

Answer: A

Explanation:
During the Sprint Retrospective, the Scrum Team may add items to the Sprint Backlog for the next Sprint, as stated in [5]: “The purpose of each Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team plans ways to implement improvements identified during this meeting into its way of working. By doing this it reinforces empiricism throughout its work. Improvements may be implemented at any time during a Sprint or they may be planned for subsequent Sprints.”

NEW QUESTION 13
Which two activities will a Product Owner engage in during a Sprint? (Choose two.)

• A. Run the Daily Scrum.
• B. Prioritize the Development Team’s work on the Sprint Backlog.
• C. Update the Sprint burndown chart.
• D. Answer questions from the Development Team about items in the current Sprint.
• E. Work with the stakeholders.

Answer: DE

Explanation:
The correct answers are D and E, because these are two activities that a Product Owner can engage in during a Sprint. The Scrum Guide states that “the Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.” Therefore, the Product Owner can answer questions from the Development Team about items in the current Sprint, and work with the stakeholders to understand their needs and expectations.

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

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

Answer: BD

Explanation:
According to the Scrum Guide, two intended outcomes of the Daily Scrum are identification of impediments that may prevent the Developers from achieving the Sprint Goal and a shared understanding of the most important work to be undertaken next to achieve the best possible progress toward the Sprint Goal. These outcomes help the Developers to inspect their progress, plan their work, and collaborate effectively. The other options are not intended outcomes of the Daily Scrum, as they are either irrelevant (such as updating a Scrum board) or inappropriate (such as providing a status report or an update of completed tasks).

NEW QUESTION 15
Which Scrum Values are exhibited by not building Product Backlog items that have low business value? (Choose three.)

• A. Economic Value Added.
• B. Respect.
• C. Focus.
• D. Earned Value.
• E. Courage.

Answer: BCE

Explanation:
According to the Scrum Guide1, there are five values that guide decisions within Scrum teams:
Commitment
Focus
Openness
Respect
Courage
By not building Product Backlog items that have low business value, Scrum teams exhibit respect for their stakeholders and customers, as they deliver what is most valuable and relevant for them. They also exhibit focus, as they concentrate on what matters most for achieving their Product Goal and Sprint Goal. They also exhibit courage, as they are willing to say no to low-value work and face possible conflicts or disagreements.

NEW QUESTION 16
When should a Sprint Goal be created?

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

Answer: E

Explanation:
According to the Scrum Guide1, one aspect of Scrum Teams inspecting how they work toward their Product Goal is that they create a Sprint Goal every Sprint. 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 Developers on why it is building the Increment. It also provides a basis for inspecting and adapting during the Sprint Review and Sprint Retrospective. The Sprint Goal is created during the Sprint Planning event.
References: Scrum Guide

NEW QUESTION 17
A new developer is having continuing conflicts with existing Development Team members and creating the hostile environment. If necessary, who is responsible for removing the team member?

• A. The hiring manager is responsible, because he/she hired the developer.
• B. The Scrum Manager is responsible, because he/she removes Impediments.
• C. The Development Team is responsible, and may need help from the Scrum Master.
• D. The Product Owner is responsible, because he/she controls the return on investment (ROI).

Answer: C

Explanation:
The correct answer is C, because if necessary, the Development Team is responsible for removing a team member who is creating a hostile environment. The Scrum Guide states that “development Teams are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product
Backlog into Increments of potentially releasable functionality.” Therefore, the Development Team should
manage its own composition and dynamics, and may need help from the Scrum Master to facilitate this process.

NEW QUESTION 18
What is the time-box for the Sprint Planning meeting?

• A. 4 Hours for a monthly Sprint.
• B. 8 Hours for a monthly Sprint.
• C. Monthly.
• D. Whenever it is done.

Answer: B

Explanation:
The correct answer is B, because the time-box for the Sprint Planning meeting is 8 hours for a monthly Sprint. The Scrum Guide states that “Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.”

NEW QUESTION 19
When can a Development Team cancel a Sprint?

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

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.

NEW QUESTION 20
......