Answer:

AC

Explanation:
Several Sprints into a project, a key stakeholder begins using the product and finds the quality
lacking. The Product Owner (PO) agrees and shares this concern with the Scrum Master (SM). The
Scrum Master needs to determine the best way to respond.
Scrum emphasizes empiricism, which is based on transparency, inspection, and adaptation. This
means that if quality concerns arise, the Scrum Team must inspect the issue, adapt accordingly, and
ensure quality is built into the product incrementally.
✅
A. Encourage the Product Owner to include quality specifications in the Product Backlog and to
communicate the stakeholders' concerns to the Developers.
Reference from the Scrum Guide:
"The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the
single source of work undertaken by the Scrum Team."
"The Product Owner is accountable for maximizing the value of the product resulting from the work
of the Scrum Team."
Why is this Correct?
Since the Product Owner represents the stakeholders, they should translate the stakeholder’s
concerns into actionable Product Backlog Items (PBIs) that reflect quality improvements.
Developers can refine and plan these PBIs in upcoming Sprints to ensure quality is systematically
addressed.
The Product Backlog is the single source of work, meaning all quality requirements should be made
explicit there.
This approach aligns with Scrum’s empirical process of making work transparent so that the team can
inspect and adapt.
✅
C. Work with the Product Owner to understand their desired resolution and help formulate an
approach for raising the concern with the Developers.
Reference from the Scrum Guide:
"The Scrum Master serves the Product Owner in several ways, including: Helping find techniques for
effective Product Goal definition and Product Backlog management."
"The Scrum Master serves the Scrum Team in several ways, including: Helping the Scrum Team focus
on creating high-value Increments that meet the Definition of Done."
Why is this Correct?
The Scrum Master is a servant leader, responsible for facilitating collaboration between the Product
Owner and Developers so that the concern is effectively addressed.
Instead of dictating a solution, the Scrum Master guides discussions and enables the team to decide
how best to improve quality.
The Definition of Done (DoD) should be reviewed to ensure it is clear, measurable, and includes
quality standards.
This approach ensures that all stakeholders—Developers, Product Owner, and Scrum Master—
collaborate in a self-managing way to improve quality.
Incorrect Answers with Explanations
❌
B. Bring the concern to the testers to improve how the Product is verified.
Reference from the Scrum Guide:
"Developers are always accountable for: Instilling quality by adhering to a Definition of Done."
Why is this Incorrect?
Scrum does not have a separate testing team; instead, the Developers are responsible for all aspects
of quality (coding, testing, integration, etc.).
Quality should not be "verified" by an external group; rather, it must be built into the Increment from
the start.
Instead of passing the issue to testers, the Scrum Team should improve their Definition of Done to
ensure the product meets the necessary quality standards.
❌
D. Tell the Product Owner they have noted the concern and will raise this issue at the Sprint
Retrospective.
Reference from the Scrum Guide:
"The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for
improvements to be enacted during the next Sprint."
Why is this Incorrect?
While the Sprint Retrospective is useful for discussing improvements, waiting until the Retrospective
delays the resolution of a critical issue.
The Scrum Team should act immediately by addressing quality issues in the Product Backlog and
adapting their work in upcoming Sprints.
Transparency and fast feedback are key principles in Scrum—delaying discussions goes against
empiricism.
❌
E. Explain to the Product Owner that it is up to the Developers to decide on acceptable quality
standards.
Reference from the Scrum Guide:
"The Definition of Done is a formal description of the state of the Increment when it meets the
quality measures required for the product."
"If the Definition of Done for an increment is part of the standards of the organization, all Scrum
Teams must follow it as a minimum."
Why is this Incorrect?
While the Developers are responsible for meeting the Definition of Done, quality is a shared
responsibility across the Scrum Team.
The Product Owner must ensure that the product delivers value to stakeholders, which includes
meeting their quality expectations.
Ignoring the Product Owner’s concerns contradicts Scrum’s emphasis on collaboration and
transparency.

Answer:

C

Explanation:
In the Scrum framework, there is no specific role or accountability for a Tester. Instead, the responsibi
lity for quality lies with the entire Scrum Team, particularly the Developers. Scrum emphasizes cross-
functional teams, where every team member contributes to all aspects of the development process,
including testing. The Developers collectively ensure that the work meets the Definition of Done and
maintains high-
quality standards. This approach fosters collaboration, shared responsibility, and continuous improve
ment, aligning with the core principles of Scrum.

Answer:

D

Explanation:
According to the Scrum framework, the Product Owner is responsible for managing the Product Backl
og, which includes prioritizing and adding new items1. However, when a new item is introduced duri
ng a Sprint, it is crucial to involve the entire Scrum Team in the decision-
making process. This ensures that the team can assess the impact of the new item on the current Spr
int goals, capacity, and workload1. By discussing the item with the team, they can collectively decide
whether to include it in the current Sprint, defer it to a future Sprint, or handle it in another way1. Th
is collaborative approach aligns with the principles of transparency, inspection, and adaptation, whic
h are core to Scrum.

Answer:

E

Explanation:
In Scrum, the Developers have the autonomy to manage their work and the Sprint Backlog. When an
unexpected request comes in, even from someone as authoritative as the CEO, it should not be
added directly to the Sprint Backlog without discussion.
The correct approach is for the Developers to
discuss the new item with the Product Owner and the rest of the Scrum Team to understand its
impact on the current Sprint Goal and to collaboratively decide the best course of action12
.
This is in line with the Scrum values of Courage, Focus, Commitment, Respect, and Openness.
The
team must have the courage to push back on changes that could disrupt their Sprint Goal, stay
focused on their commitments, respect the agreed-upon process, and be open about the
implications of introducing new work mid-Sprint1
.
The Scrum Guide also states that once the Sprint begins, no one can force the Development Team to
work on different requirements than those they forecasted for the Sprint1
. If the CEO’s request is
deemed important enough to warrant a change in the Sprint’s direction, it may lead to a negotiation
of scope with the Product Owner or, in extreme cases, to the cancellation of the Sprint if the Sprint
Goal becomes obsolete.
However, these are decisions that should be made collaboratively by the
entire Scrum Team, not unilaterally by any single member, regardless of their position in the
company

Answer:

DE

Explanation:
https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf
Scrum is a framework for developing, delivering, and sustaining complex products. Scrum has three
roles: the Product Owner, the Scrum Master, and the Developers. The Developers are the people in
the Scrum Team who are committed to creating any aspect of a usable Increment in each Sprint. The
Developers are not limited by titles such as programmer, designer, tester, architect, engineer, etc.
The Developers are responsible for all aspects of quality, including finding and fixing bugs, tracking
quality metrics, and verifying the work of other Developers. Therefore, Scrum has no “tester” role,
and the Developers are responsible for quality.

Answer:

A

Answer:

A

Explanation:
Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value
each Sprint.
They are responsible for all product-related activities from stakeholder collaboration,
verification, maintenance, operation, experimentation, research and development, and anything
else that might be required12
.
The Scrum Team’s goal is to deliver a “Done” Increment that meets
the Definition of Done and the Sprint Goal3
.
Reference: 1: The Scrum Team | Scrum.org 2: The Professional Scrum™ Competencies | Scrum.org 3
:
The 2020 Scrum Guide | Scrum.org

Answer:

B

Explanation:
According to the Scrum Guide, the Definition of Done is a formal description of the state of the
Increment when it meets the quality measures required for the product1
.
The Definition of Done is
created by the Developers and it is used to assess when work is complete on the product
Increment1
.
The Scrum Guide also states that the Definition of Done may vary significantly per Scrum Team,
depending on the context.
The Definition of Done evolves over time and becomes more stringent as
the Scrum Team matures1
. Therefore, it is important for the Scrum Team to regularly inspect and
adapt the Definition of Done to reflect their current situation and needs.
The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for
improvements to be enacted during the next Sprint1
.
The Sprint Retrospective focuses on three
questions: What went well in the Sprint? What could be improved? What will we commit to improve
in the next Sprint?1
These questions can help the Scrum Team identify potential changes to the
Definition of Done that would increase the quality and value of the product.
Option A is incorrect because Product Backlog refinement is not a formal Scrum event, but rather an
ongoing activity that can happen at any time during the Sprint1
.
Product Backlog refinement is
mainly concerned with adding detail, estimates, and order to Product Backlog items1
. Changing the
Definition of Done during Product Backlog refinement could cause confusion and inconsistency
among the Developers and the Product Owner.
Option C is incorrect because Sprint Planning is a time-boxed event that initiates a Sprint by defining
a Sprint Goal and selecting Product Backlog items that deliver one coherent function1
.
Sprint
Planning is based on the current state of the Product Backlog and the latest Definition of Done1
.
Changing the Definition of Done during Sprint Planning could disrupt the flow of the event and affect
the scope and feasibility of the Sprint.
Option D is incorrect because prior to starting a new project is not a specific time in Scrum.
Scrum
does not prescribe any phases or stages for a project, but rather an empirical approach that relies on
frequent inspection and adaptation of both the product and the process1
. Changing the Definition of
Done before starting a new project could be premature and irrelevant, as the Scrum Team may not
have enough information or experience to define what ‘Done’ means for their product.
Reference: 1
:
The Scrum Guide

Answer:

A

Explanation:
According to the Scrum Guide, the Scrum Master is responsible for promoting and supporting Scrum
as defined in the Scrum Guide1
.
Scrum Masters do this by helping everyone understand Scrum
theory, practices, rules, and values1
.
The Scrum Master is accountable for establishing Scrum2
.
They
do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and
the organization while serving the Scrum Team as well as the larger organization2
.
Option B is incorrect because keeping track of resource allocation is not a responsibility of the Scrum
Master. The Scrum Master does not manage or control the resources of the Scrum Team or the
organization.
The Scrum Team is self-organizing and responsible for managing its own work within a
Sprint1
.
Option C is incorrect because managing the performance of the Scrum Team is not a responsibility of
the Scrum Master. The Scrum Master does not evaluate or appraise the performance of the
Development Team or the Product Owner.
The Scrum Master serves the Development Team by
coaching them on self-organization and cross-functionality, and serves the Product Owner by
ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team1
.
Option D is incorrect because the meetings and the objectives that a Scrum Team sets for itself are
not a responsibility of the Scrum Master. The Scrum Master does not dictate or prescribe what
meetings or objectives a Scrum Team should have.
The Scrum Master facilitates the Scrum Events as
requested or needed, and ensures that they are positive, productive, and kept within the time-box1
.

Answer:

BE

Explanation:
According to the Scrum Guide, the Scrum Master is responsible for coaching the Scrum Team to
improve its skills, tools and environment over time and adjust the Definition of Done
accordingly1
.
The Definition of Done is a formal description of the state of the Increment when it
meets the quality measures required for the product1
.
The Definition of Done should be possible to
achieve given current circumstances2
. Therefore, option B and E are appropriate for a Scrum Master
to do, if the Scrum Team does not have the tools and environment to completely finish each selected
Product Backlog item.
Option A is not appropriate because declaring the Scrum Team not ready for Scrum implies that there
is a fixed set of prerequisites for using Scrum, which is not true.
Scrum is a framework that can be
applied to any complex product development effort1
.
Option C is not appropriate because encouraging the Product Owner to accept partially done
Increments until the situation improves violates the principle of transparency.
Transparency requires
that the Increment is a usable product that meets the current Definition of Done1
.
Accepting
partially done Increments also increases technical debt and reduces value delivery3
.
Option D is not appropriate because refocusing the current Sprint on establishing the Scrum Team’s
environment instead of delivering an Increment goes against the purpose of a Sprint. A Sprint is a
time-boxed event that serves as a container for the other Scrum events and activities.
The goal of
each Sprint is to deliver a potentially releasable Increment that adheres to the current Definition of
Done1
.
Reference: 1
:
The Scrum Guide 2
:
Suggested Reading for Professional Scrum Master™ I 3
:
Mastering
Professional Scrum

Answer:

B

Explanation:
The best answer is B. The Developers on the Scrum Team should write the user documentation.
According to the Scrum Guide, the Definition of Done creates transparency and ensures that the
product Increment meets the quality standards required for the product1
.
If user documentation is
part of the Definition of Done, then it should be completed within the Sprint by the Scrum Team1
.
The Scrum Team should have all the skills needed to deliver the product, and if user documentation
is part of the product, then that skill should be on the team as well2
.
The Developers on the Scrum
Team are responsible for creating a plan for delivering the Increment, which includes user
documentation1
.
They can also ask for help from other more experienced writers outside the team,
or learn the skill through training or workshops2
. The other options are not consistent with the
Scrum values and principles, as they would create dependencies, delays, and waste in the product
development process.

Answer:

A

Explanation:
The answer is A. True. The Sprint Backlog is a result of Sprint Planning, and it includes the Sprint
Goal.
According to the Scrum Guide, the Sprint Backlog is composed of the Sprint Goal (why), the set
of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering
the Increment (how)1
.
The Sprint Goal is the single objective for the Sprint, and it provides
coherence and focus for the Scrum Team2
.
The Sprint Backlog is a plan by and for the Developers,
and it is updated throughout the Sprint as more is learned2
.

Answer:

C

Explanation:
The best answer is C. When multiple Scrum Teams are working together on a product, they must
mutually define and comply with the same Definition of Done.
This is because the Definition of Done
creates transparency and ensures that the product Increment meets the quality standards required
for the product1
. If each Scrum Team has its own Definition of Done, it may lead to inconsistencies,
conflicts, and technical debt in the product. Therefore, the Scrum Teams should collaborate and
agree on a common Definition of Done that applies to all Product Backlog Items and Increments.
This
way, the Scrum Teams can deliver a potentially releasable product Increment at the end of every
Sprint2
.

Answer:

ACD

Explanation:
The Definition of Done serves the following three purposes:
A . Create a shared understanding of when work is complete.
The Definition of Done is a commitment to the quality of the product increment that is part of Scrum.
It is a formal description of the state of the product backlog item or the increment when it meets the
quality measures required for the product.
The Scrum team must have a shared understanding of
what ‘done’ means and use it to assess when work is complete and transparent1
.
C . Increase transparency.
The Definition of Done increases transparency by providing everyone a shared understanding of what
work was completed and what standards were met as part of the increment.
This ensures that the
product increment is potentially releasable and that the stakeholders can inspect and provide
feedback on it2
.
D . Describe the work that must be mostly done before the Sprint is allowed to end.
The Definition of Done describes the work that must be done before the Sprint is allowed to end.
Work cannot be considered part of an increment unless it meets the Definition of Done.
The
Definition of Done is used to guide the Developers in creating a "Done", usable, and potentially
releasable product increment every Sprint3
.
B and E are not purposes of the Definition of Done.
B . Guide the Developers on how many Product Backlog items to select for the Sprint.
The Definition of Done does not guide the Developers on how many Product Backlog items to select
for the Sprint. The Developers select how many Product Backlog items they can complete within a
Sprint based on their capacity, skills, and experience.
The Definition of Done helps them ensure that
the selected items are completed to a high standard of quality4
.
E . Describe the purpose, Objective, and timebox Of each Scrum event.
The Definition of Done does not describe the purpose, objective, and timebox of each Scrum event.
The Scrum Guide describes these aspects for each Scrum event, such as Sprint Planning, Daily Scrum,
Sprint Review, and Sprint Retrospective5
. The Definition of Done is related to the product increment,
not to the Scrum events.

Answer:

C

Explanation:
The best answer is C. When multiple Scrum Teams are working together on a product, they must
mutually define and comply with the same Definition Of Done.
According to the Scrum Guide1
, “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 Scrum Guide also
states that “when multiple Scrum Teams are working together on a product, they must mutually
define and comply with the same Definition of Done. This ensures transparency and consistency
among the teams and makes their combined work potentially releasable.”
A, B, and D are not correct answers.
A . Each Scrum Team uses its own, but must make their definition clear to all other teams so the
differences are known.
This answer does not reflect the Scrum value of alignment2
. Having different Definitions of Done for
each Scrum Team can create confusion and inconsistency in the quality and completeness of the
product. It can also make it difficult to integrate and deliver a coherent and valuable Increment at the
end of each Sprint.
B . The Scrum Masters from each Scrum Team define a common Definition of Done.
This answer does not reflect the Scrum principle of self-organization3
. The Definition of Done should
be created by the Developers who are responsible for delivering the Increment, not by the Scrum
Masters who are responsible for facilitating and coaching the Scrum Teams. The Scrum Masters can
help the Developers understand and apply the Definition of Done, but they should not impose it on
them.
D . Each Scrum Team defines and uses its own. The differences are discussed and reconciled during a
hardening Sprint.
This answer does not reflect the Scrum value of focus2
. Having different Definitions of Done for each
Scrum Team can lead to technical debt or rework that requires a hardening Sprint to resolve.
A
hardening Sprint is an anti-pattern that violates the rule of delivering a potentially releasable
Increment at the end of each Sprint4
.