Scrum Master Qs & Answers

The purpose of the Assessment is to help in your preparation and

practice for any Scrum Master Certificate. This is a list of 500+ questions
this is part3 don’t forget to checkout the other parts.
1-Which of the following sets the Definition of Done?
1. The Scrum Team.
2. The Product Owner
3. The Scrum Master
4. The Developers
Which of the following sets the Definition of Done?
1. The Scrum Team.
2. The Product Owner
3. The Scrum Master
4. The Developers
explanation
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. If it is not an organizational standard, the Scrum Team must create a
Definition of Done appropriate for the product. The Developers are required to conform to the Definition
of Done. If there are multiple Scrum Teams working together on a product, they must mutually define
and comply with the same Definition of Done.
2-Which of the following statements are correct about the Sprint
Retrospective?
1. It typically occurs before the Sprint Review
2. Only the Developers participate
3. The Sprint Retrospective is to plan ways to increase quality and
effectiveness.
4. Improvements identified via the Sprint Retrospective must be
implemented in the next
5. Sprint.
Which of the following statements are correct about the Sprint Retrospective?
1. It typically occurs before the Sprint Review
2. Only the Developers participate
3. The Sprint Retrospective is to plan ways to increase quality and
effectiveness.
4. Improvements identified via the Sprint Retrospective must be
implemented in the next Sprint.
explanation
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum
Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements
are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint.
The Sprint Retrospective concludes the Sprint.
3-Which one of the following statements is correct when multiple
Scrum Teams are working on the same product?
1. There can be multiple Product Backlogs when it's possible to
divide the product into different application areas
2. There's only one Product Backlog.
3. There can be multiple Product Backlogs, but still a single
integrated Product Backlog to summarize them all.
Which one of the following statements is correct when multiple
Scrum Teams are working on the same product?
1. There can be multiple Product Backlogs when it's possible to
divide the product into different application areas
2. There's only one Product Backlog.
3. There can be multiple Product Backlogs, but still a single
integrated Product Backlog to summarize them all.
explanation
One product = one Product Backlog
4-Which outcome is expected as Scrum Teams mature?
1. Sprint Planning will no longer be needed.
2. They will improve their Definition of Done to include more
stringent criteria.
3. A Scrum Master is no longer needed.
4. The Sprint Retrospectives will grow to be longer than 3 hours.
5. There is no need for a timeboxed Sprint since timeboxes are
only for new Scrum Teams.
Which outcome is expected as Scrum Teams mature?
1. Sprint Planning will no longer be needed.
2. They will improve their Definition of Done to include more
stringent criteria.
3. A Scrum Master is no longer needed.
4. The Sprint Retrospectives will grow to be longer than 3 hours.
5. There is no need for a timeboxed Sprint since timeboxes are
only for new Scrum Teams.
explanation
Quality will not decrease over time and for many teams they will seek to increase the level of quality via
the Definition of Done.
5-Which role is the equivalent of a project manager in Scrum?
1. The team leader
2. None.
3. The Product Owner
4. The Scrum Master
5. The Developers
Which role is the equivalent of a project manager in Scrum?
1. The team leader
2. None.
3. The Product Owner
4. The Scrum Master
5. The Developers
explanation
There is no equivalent role. Aspects of project management are carried out by the Scrum
Team
6-Which Scrum accountability is responsible for sizing of Product
Backlog items?
1. The Developers.
2. The Scrum Team
3. The Scrum Master
4. The Product Owner
Which Scrum accountability is responsible for sizing of Product
Backlog items?
1. The Developers.
2. The Scrum Team
3. The Scrum Master
4. The Product Owner
explanation
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.
7-Which Scrum event is an inspect and adapt opportunity for the
Developers?
1. The Project Status Meeting
2. The Daily Scrum.
3. Design Sessions
4. Architecture review sessions
explanation
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 is a 15-minute event for the Developers of the Scrum Team.
Which Scrum event is an inspect and adapt opportunity for the
Developers?
1. The Project Status Meeting
2. The Daily Scrum.
3. Design Sessions
4. Architecture review sessions
explanation
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 is a 15-minute event for the Developers of the Scrum Team.
8-Which Scrum event is for process improvement?
1. Sprint Planning
2. O Sprint Retrospective.
3. Sprint Review
4. Daily Scrum
Which Scrum event is for process improvement?
1. Sprint Planning
2. O Sprint Retrospective.
3. Sprint Review
4. Daily Scrum
explanation
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum
Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and
their Definition of Done.
9-Which statement(s) about Scrum are not true? Select 2 answers.
1. Scrum is founded on empirical process control theory or
empiricism
2. Scrum is designed for static requirements.
3. Scrum is simple
4. Scrum will solve all your problems.

.
Which statement(s) about Scrum are not true? Select 2 answers.
1. Scrum is founded on empirical process control theory or
empiricism
2. Scrum is designed for static requirements.
3. Scrum is simple
4. Scrum will solve all your problems.
explanation
In complex environments change is inevitable. Scrum will help you find your problems but not
necessarily solve them. Scrum is a framework based on empiricism that is designed to be
simple.
10-Which statement best describes the Definition of Done?
1. The Definition of Done is a formal description of the state of the
Increment when it meets the quality measures required for the
product.
2. Passing the QA tests and having all the required documents
(BRD and FSD) in place
3. Anything that the Product Owner or the Scrum Master finds
necessary
4. Definition of Done is the acceptance criteria in Scrum
Which statement best describes the Definition of Done?
1. The Definition of Done is a formal description of the state of the
Increment when it meets the quality measures required for the
product.
2. Passing the QA tests and having all the required documents (BRD
and FSD) in place
3. Anything that the Product Owner or the Scrum Master finds
necessary
4. Definition of Done is the acceptance criteria in Scrum
explanation
The Definition of Done is a formal description of the state of the Increment when it meets the quality
measures required for the product.
11-Which statement best describes the Sprint Backlog?
1. It's composed by the Product Owner alone
2. The Sprint Backlog is a plan by and for the Developers.
3. The Sprint Backlog lists all features, functions, requirements,
enhancements, and fixes that constitute the changes to be
made to the product in future releases
4. Each of its items is assigned to a team member
Which statement best describes the Sprint Backlog?
1. It's composed by the Product Owner alone
2. The Sprint Backlog is a plan by and for the Developers.
3. The Sprint Backlog lists all features, functions, requirements,
enhancements, and fixes that constitute the changes to be
made to the product in future releases
4. Each of its items is assigned to a team member
explanation
The Sprint Backlog is a plan by and for the Developers
12-Which statement is correct when the Developers are working in
the middle of the Sprint?
1. The Sprint Backlog must be frozen
2. Scope may be clarified and renegotiated with the Product
Owner as more is learned.
3. No user acceptance tests will be conducted until the end of the
Sprint
4. The scope must be checked by the Product Owner and he or
she must provide an assessment for the Developers
Which statement is correct when the Developers are working in the
middle of the Sprint?
1. The Sprint Backlog must be frozen
2. Scope may be clarified and renegotiated with the Product
Owner as more is learned.
3. No user acceptance tests will be conducted until the end of the
Sprint
4. The scope must be checked by the Product Owner and he or
she must provide an assessment for the Developers
explanation
During the Sprint, scope may be clarified and renegotiated with the Product Owner as more is learned.
13-Which statements are correct about a Product Backlog item that
was not Done by the end of the Sprint? Select all that apply.
1. It will not be inspected at the Sprint Review.
2. It must be completed in the next Sprint
3. It will be moved back to the Product Backlog.
4. It will be demonstrated to the stakeholders at the Sprint Review
and the Product Owner will explain it is not complete yet
5. The Product Owner has to extend the Sprint until the item is
Done
Which statements are correct about a Product Backlog item that was not Done
by the end of the Sprint? Select all that apply.
1. It will not be inspected at the Sprint Review.
2. It must be completed in the next Sprint
3. It will be moved back to the Product Backlog.
4. It will be demonstrated to the stakeholders at the Sprint Review and the
Product Owner will explain it is not complete yet
5. The Product Owner has to extend the Sprint until the item is Done
explanation
The Definition of Done creates transparency by providing everyone a shared understanding of what work
was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done,
it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog
for future consideration.
14-Which statements are correct about the Sprint Retrospective?
1. It's the only time improvement may be planned
2. It is timeboxed to 6 hours in for a one-month Sprint
3. It's an opportunity for inspection and adaptation of the process
used by the Scrum Team.
4. It happens before the Sprint Review
5. The Product Owner doesn't have to be at the event
Which statements are correct about the Sprint Retrospective?
1. It's the only time improvement may be planned
2. It is timeboxed to 6 hours in for a one-month Sprint
3. It's an opportunity for inspection and adaptation of the process
used by the Scrum Team.
4. It happens before the Sprint Review
5. The Product Owner doesn't have to be at the event
explanation
Each event in Scrum is a formal opportunity to inspect and adapt, but not the only time that this may
happen. It happens at the end of each Sprint, is attended by the Scrum Team and is timeboxed to 3
hours.
15-Which of the following are the most important considerations,
when forming multiple Scrum Teams? Select 2 answers.
1. Having a mixture of senior and junior Developers in each team
2. Having enough skills for the technical layer designated to each
Scrum Team
3. Ensuring the Scrum Teams are cross-functional.
4. Having an effective mixture of skill in each team to minimize
dependencies.
Which of the following are the most important considerations,
when forming multiple Scrum Teams? Select 2 answers.
1. Having a mixture of senior and junior Developers in each team
2. Having enough skills for the technical layer designated to each
Scrum Team
3. Ensuring the Scrum Teams are cross-functional.
4. Having an effective mixture of skill in each team to minimize
dependencies.
explanation
Scrum Teams are cross-functional with all the skills needed to create a Done Increment
16-Which two of the following is true about Daily Scrum?
Select 2 answers.
1. It is a 15-minute event.
2. it is for the Developers.
3. The Product Owner provides an update at this event
4. Is held at the end of the Sprint to inspect the Increment and
adapt the Product Backlog if needed.
Which two of the following is true about Daily Scrum?
Select 2 answers.
1. It is a 15-minute event.
2. it is for the Developers.
3. The Product Owner provides an update at this event
4. Is held at the end of the Sprint to inspect the Increment and
adapt the Product Backlog if needed.
explanation
The Daily Scrum is a 15-minute event for the Developers of the Scrum Team
17-Which statements about the Sprint Backlog are true?
Select 2 answers.
1. The Sprint Backlog does not change after Sprint Planning
2. The Sprint Backlog should have enough detail that Developers
can inspect their progress in the Daily Scrum.
3. The Sprint Backlog is an ordered list of everything that is known
to be needed in the product.
4. The Sprint Backlog makes visible the work that the Developers
identify as necessary to meet the Sprint Goal.
Which statements about the Sprint Backlog are true? Select 2 answers.
1. The Sprint Backlog does not change after Sprint Planning
2. The Sprint Backlog should have enough detail that Developers can inspect
their progress in the Daily Scrum.
3. The Sprint Backlog is an ordered list of everything that is known to be
needed in the product.
4. The Sprint Backlog makes visible the work that the Developers identify as
necessary to meet the Sprint Goal.
explanation
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).
The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work
that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal.
Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned. It should have
enough detail that they can inspect their progress in the Daily Scrum.
18-Who assigns tasks to the Developers?
1. The Scrum Master
2. The Product Owner
3. The Developers themselves.
4. The project manager
5. The Development Manager
Who assigns tasks to the Developers?
1. The Scrum Master
2. The Product Owner
3. The Developers themselves.
4. The project manager
5. The Development Manager
explanation
Developers are the people in the Scrum Team that are committed to creating any aspect of a usable
Increment each Sprint.
The Developers are always accountable for:
Creating a plan for the Sprint, the Sprint Backlog and adapting their plan each day toward the Sprint
Goal.
19-Who can change the Sprint Backlog during the Sprint?
1. The Developers.
2. The Scrum Master
3. The Product Owner
4. Anyone
Who can change the Sprint Backlog during the Sprint?
1. The Developers.
2. The Scrum Master
3. The Product Owner
4. Anyone
explanation
The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture
of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal.
20-Who creates the Sprint Goal?
1. The Scrum Master
2. The Developers
3. The Scrum Team.
4. The Product Owner
Who creates the Sprint Goal?
1. The Scrum Master
2. The Developers
3. The Scrum Team.
4. The Product Owner
explanation
The Sprint Goal is a commitment by the Developers. However, it is created, negotiated and
agreed by the Scrum Team in Sprint Planning
21-Who determines when it is time to update the Sprint Backlog
during the Sprint?
1. The Product Owner
2. The Developers.
3. The Scrum Team leader
4. The Scrum Master
5. Senior Developers
Who determines when it is time to update the Sprint Backlog
during the Sprint?
1. The Product Owner
2. The Developers.
3. The Scrum Team leader
4. The Scrum Master
5. Senior Developers
explanation
The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work
that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal.
Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned.
22-Who is accountable for ensuring that the burn-down chart and
gant chart exist?
1. No one.
2. The Developers
3. The Product Owner
4. The Scrum Master
explanation
Burn-down and Gannt chart are not mandatory in Scrum
Who is accountable for ensuring that the burn-down chart and gant
chart exist?
1. No one.
2. The Developers
3. The Product Owner
4. The Scrum Master
explanation
Burn-down and Gannt chart are not mandatory in Scrum
23-Who is accountable for ordering the Product Backlog?
1. The Product Owner and the Developers
2. The Developers
3. The Product Owner and the customer
4. The Product Owner.
5. The Scrum Master
Who is accountable for ordering the Product Backlog?
1. The Product Owner and the Developers
2. The Developers
3. The Product Owner and the customer
4. The Product Owner.
5. The Scrum Master
explanation
The Product Owner is accountable for effective Product Backlog management, which
includes ordering Product Backlog items.
24-Who is in the Scrum Team? Select all that apply.
1. Supervisor
2. Scrum Master
3. Developers
4. project manager
5. Product Owner
Who is in the Scrum Team? Select all that apply.
1. Supervisor
2. Scrum Master
3. Developers
4. project manager
5. Product Owner
explanation
The Scrum Team consists of a Product Owner, Developers, and a Scrum Master
25-Who is responsible for defining the Sprint Goal during Sprint
Planning?
1. The Scrum Master
2. The Scrum Team
3. The Product Owner
4. The Developers
5. stakeholders
Who is responsible for defining the Sprint Goal during Sprint
Planning?
1. The Scrum Master
2. The Scrum Team
3. The Product Owner
4. The Developers
5. stakeholders
explanation
The whole Scrum Team collaborates to define a Sprint Goal that communicates why the Sprint is valuable
to stakeholders.
26-Who is responsible for ensuring Scrum is used correctly?
1. Product Owner
2. Scrum Master
3. Developers
4. stakeholders
Who is responsible for ensuring Scrum is used correctly?
1. Product Owner
2. Scrum Master
3. Developers
4. stakeholders
explanation
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They
do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the
organization.
27-Who is responsible for the system architecture of a product
being developed using Scrum?
1. The senior architect
2. The Developers.
3. The software architect.
4. The Product Owner
Who is responsible for the system architecture of a product being
developed using Scrum?
1. The senior architect
2. The Developers.
3. The software architect.
4. The Product Owner
explanation
The Developers are responsible for the system architecture of a product being developed using Scrum
28-Who is the owner of each Product Backlog item in the Sprint
Backlog?
1. The Developers
2. The Senior Developers
3. The Scrum Master
4. The Product Owner
Who is the owner of each Product Backlog item in the Sprint
Backlog?
1. The Developers
2. The Senior Developers
3. The Scrum Master
4. The Product Owner
explanation
The Developers are collectively responsible for the work in the current Sprint.
29-Who manages the Sprint Backlog?
1. The Scrum Master
2. The Product Owner
3. The Scrum Team
4. The Developers
Who manages the Sprint Backlog?
1. The Scrum Master
2. The Product Owner
3. The Scrum Team
4. The Developers
explanation
The Sprint Backlog is a plan by and for the Developers.
30-Who manages the work during the Sprint?
1. The Developers
2. The Scrum Master
3. The Scrum Team
4. The Product Owner
Who manages the work during the Sprint?
1. The Developers
2. The Scrum Master
3. The Scrum Team
4. The Product Owner
explanation
The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog and
update this plan each day toward the Sprint Goal.
31-Who sets the Definition of Done?
1. The Scrum Team
2. The Product Owner
3. The Scrum Master
4. The Developers
Who sets the Definition of Done?
1. The Scrum Team
2. The Product Owner
3. The Scrum Master
4. The Developers
explanation
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. If it is not an organizational standard, the Scrum Team must create a
Definition of Done appropriate for the product.
32-Who is accountable for ordering the Product Backlog?
1. The Product Owner and the Developers
2. The Developers
3. The Product Owner and the customer
4. The Product Owner
5. The Product Owner, the customer, and the Developers
Who is accountable for ordering the Product Backlog?
1. The Product Owner and the Developers
2. The Developers
3. The Product Owner and the customer
4. The Product Owner
5. The Product Owner, the customer, and the Developers
explanation
The Product Owner is also accountable for effective Product Backlog management, which
includes ordering Product Backlog items.
33-Why does the Product Owner need to care about and pay
attention to technical debt?
1. There's no reason for the Product Owner to pay attention to
technical aspects.
2. To have a better understanding of the total cost of ownership,
as affected by the ongoing maintenance cost of the product.
3. To track the performance of the team
4. To track the performance of the senior team members
Why does the Product Owner need to care about and pay attention to
technical debt?
1. There's no reason for the Product Owner to pay attention to technical
aspects.
2. To have a better understanding of the total cost of ownership, as affected
by the ongoing maintenance cost of the product.
3. To track the performance of the team
4. To track the performance of the senior team members
explanation
Technical debt may create problems in the future. When there's a lot of technical debt, the velocity
might decrease in the future, because Developers will have to deal with an increasing number of
problems. This debt might remain in the released product, and make it harder and more expensive to
maintain.
"Total cost of ownership" is the combination of production and maintenance costs of a product.
34-The Daily Standup is one of the 5 Scrum events.
1. False.
2. True
The Daily Standup is one of the 5 Scrum events.
1. False.
2. True
explanation
The correct name for the daily event is Scrum is the Daily Scrum
35-Working in Sprints means you will get more work done than
normal.
1. False
2. True
Working in Sprints means you will get more work done than
normal.
1. False
2. True
explanation
Sprints are the heartbeat of Scrum, where ideas are turned into value. They are fixed length events of
one month or less to create consistency. Despite the name, they do not guarantee you will get more
Done than normal.
36-In complex environments, what will happen is unknown.
1. True
2. False
In complex environments, what will happen is unknown.
1. True
2. False
explanation
In complex environments, what will happen is unknown
37-The Scrum framework is purposefully incomplete.
1. True
2. False
The Scrum framework is purposefully incomplete.
1. True
2. False
explanation
The Scrum framework is purposefully incomplete, only defining the parts required to
implement Scrum theory. Scrum is built upon by the collective intelligence of the people using
it. Rather than provide people with detailed instructions, the rules of Scrum guide their relationships and
interactions.
38Empiricism asserts that knowledge comes from experience and
making decisions based on what is observed.
1. True
2. False
Empiricism asserts that knowledge comes from experience and
making decisions based on what is observed.
1. True
2. False
explanation
Empiricism asserts that knowledge comes from experience and making decisions based on what is
observed.
39-Scrum events are designed to provoke change.
1. True
2. False
Scrum events are designed to provoke change.
1. True
2. False
explanation
Scrum events are designed to provoke change.
40-Adaptation becomes more difficult when the people involved
are not empowered or self-managing.
1. True
2. False
Adaptation becomes more difficult when the people involved are
not empowered or self-managing.
1. True
2. False
explanation
Adaptation becomes more difficult when the people involved are not empowered or self-
managing.
41-The Scrum Team is responsible for all product-related activities.
1. True
2. False
The Scrum Team is responsible for all product-related activities.
1. True
2. False
explanation
The Scrum Team is responsible for all product-related activities from stakeholder collaboration,
verification, maintenance, operation, experimentation, research and
development, and anything else that might be required.
Although others may do things (outside of Scrum), within the boundaries of Scrum the Scrum Team is
responsible for all product-related activities.
42-The entire Scrum Team is accountable for creating a valuable,
useful Increment every Sprint.
1. True
2. False
The entire Scrum Team is accountable for creating a valuable,
useful Increment every Sprint.
1. True
2. False
explanation
The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint.
43-Developers are the people in the Scrum Team that are
committed to creating any aspect of a usable Increment each
Sprint.
1. True
2. False
Developers are the people in the Scrum Team that are committed
to creating any aspect of a usable Increment each Sprint.
1. True
2. False
explanation
Developers are the people in the Scrum Team that are committed to creating any aspect of a usable
Increment each Sprint.
44-For Product Owners to succeed, the entire organization must
respect their decisions.
1. True
2. False
For Product Owners to succeed, the entire organization must
respect their decisions.
1. True
2. False
explanation
For Product Owners to succeed, the entire organization must respect their decisions. These decisions are
visible in the content and ordering of the Product Backlog, and through the inspectable Increment at the
Sprint Review.
45-Sprints enable predictability by ensuring inspection and
adaptation of progress toward a Product Goal at least once a
month.
1. True
2. False
Sprints enable predictability by ensuring inspection and adaptation
of progress toward a Product Goal at least once a month.
1. True
2. False
explanation
Sprints enable predictability by ensuring inspection and adaptation of progress toward a
Product Goal at least every calendar month.
46-There are many non-functional or system requirements which
the team must complete to build a valuable product. How may we
ensure that the performance requirements are addressed in the
solution? Select all that apply.
1. Add them to the Definition of Done
2. Use hardening Sprints to improve performance
3. Add them as items to the Product Backlog
4. Add a performance tester to the team
There are many non-functional or system requirements which the
team must complete to build a valuable product. How may we
ensure that the performance requirements are addressed in the
solution? Select all that apply.
1. Add them to the Definition of Done
2. Use hardening Sprints to improve performance
3. Add them as items to the Product Backlog
4. Add a performance tester to the team
explanation
It is a good practice to add performance (non-functional) requirements to Definition of Done and/or to
Product Backlog
47-The Sprint Goal is an objective set for the Sprint that can be met
through the implementation of Product Backlog items. Sprint Goals
are the result of a negotiation between the Product Owner and the
Developers. The Sprint Goal provides the following.
1. Guidance to the team on why it is developing the Increment
2. Flexibility to the team about the work in the Sprint
3. A common goal to support increased collaboration
4. All the above
The Sprint Goal is an objective set for the Sprint that can be met
through the implementation of Product Backlog items. Sprint Goals
are the result of a negotiation between the Product Owner and the
Developers. The Sprint Goal provides the following.
1. Guidance to the team on why it is developing the Increment
2. Flexibility to the team about the work in the Sprint
3. A common goal to support increased collaboration
4. All the above
explanation
The Sprint Goal is the single objective for the Sprint. Although the Sprint Goal is a commitment by the
Developers, it provides flexibility in terms of the exact work needed to achieve it. The Sprint Goal also
creates coherence and focus, encouraging the Scrum Team to work together rather than on separate
initiatives.
48-The Scrum Team discusses Product Backlog items at Sprint
Planning. As the event proceeds, the Developers start to see that
the workload selected already is greater than they can handle.
What should they do?
1. Ask the Scrum Master to stop Sprint Planning
2. Work overtime during the Sprint to complete all the work
3. Inform the Product Owner about this and monitor progress
during the Sprint
4. Remove Product Backlog items from the Sprint Backlog that is
being created
5. Ask the Product Owner to remove items from the Sprint Backlog
The Scrum Team discusses Product Backlog items at Sprint Planning. As the
event proceeds, the Developers start to see that the workload selected already
is greater than they can handle. What should they do?
1. Ask the Scrum Master to stop Sprint Planning
2. Work overtime during the Sprint to complete all the work
3. Inform the Product Owner about this and monitor progress during the
Sprint
4. Remove Product Backlog items from the Sprint Backlog that is being
created
5. Ask the Product Owner to remove items from the Sprint Backlog
explanation
Developers are always accountable for creating a plan for the Sprint, the Sprint Backlog.
49-The Product Owner is accountable for making the Product
Backlog items clear to the Developers. When many Scrum Teams
are working on the same product, one person may not be able to
do all the work required to achieve this. It will require having
multiple Product Owners.
1. True
2. False
The Product Owner is accountable for making the Product Backlog
items clear to the Developers. When many Scrum Teams are
working on the same product, one person may not be able to do all
the work required to achieve this. It will require having multiple
Product Owners.
1. True
2. False
explanation
One Product Owner = one Product Backlog. In a scaled environment they will need to find ways to scale
what they do.
50-Technical debt can be defined as the longer-term consequences
of poor design decisions. In a sense it is like any other debt - there
ought to be a clear understanding of why it is incurred, and how
and when to pay it back. What is a reason for the Product Owner to
pay attention to technical debt?
1. To understand how delivery might be affected in the future if
the level of technical debt increases
2. To track the performance of individual Developers.
3. To get feedback from stakeholders
4. There is no reason for the Product Owner to pay attention to
any technical aspects.
Technical debt can be defined as the longer-term consequences of poor design
decisions. In a sense it is like any other debt - there ought to be a clear
understanding of why it is incurred, and how and when to pay it back. What is
a reason for the Product Owner to pay attention to technical debt?
1. To understand how delivery might be affected in the future if the level of
technical debt increases
2. To track the performance of individual Developers.
3. To get feedback from stakeholders
4. There is no reason for the Product Owner to pay attention to any technical
aspects.
explanation
Accumulating too much technical debt may affect the long-term ability of the team to deliver. The
Product Owner may be restricted in maximising value if this occurs.
51-Non-functional requirements (NFRs) are requirements that
specify criteria that can be used to judge the operation of a system,
rather than specific behaviours. In Scrum, non-functional or system
requirements should always be written as user stories.
1. False
2. True
Non-functional requirements (NFRs) are requirements that specify
criteria that can be used to judge the operation of a system, rather
than specific behaviours. In Scrum, non-functional or system
requirements should always be written as user stories.
1. False
2. True
explanation
The user story practice is not mandatory in Scrum
52-When Product Backlog items are described as Done, everyone in
the team must understand what Done means. From the following
answers, choose the least accurate statement about the Definition
of Done?
1. The Product Owner creates it
2. The development organization may define it
3. It may vary depending on the product
4. It may evolve during the life of the product
When Product Backlog items are described as Done, everyone in the team
must understand what Done means. From the following answers, choose the
least accurate statement about the Definition of Done?
1. The Product Owner creates it
2. The development organization may define it
3. It may vary depending on the product
4. It may evolve during the life of the product
explanation
"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 Definition of Done creates transparency by providing everyone a shared understanding of what work was
completed as part of the Increment.
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. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for
the product.”
53-A Scrum Team is waiting for a part of the product that they need to
integrate and use to enable work in the Product Backlog. This part should
be ready in 2 months. The items at the top of the Product Backlog
currently depend on this part. What should the Product Owner do?
1. Nothing. The Developers cannot proceed with work until the
dependency is resolved.
2. Transfer the dependent Items to the Integration Team list
3. Remove the dependent Items from the Product Backlog and put them
in a special waiting
4. Make sure the dependency is visible in the Product Backlog and the
Developers have enough independent Product Backlog items for the
next Sprint.
A Scrum Team is waiting for a part of the product that they need to integrate
and use to enable work in the Product Backlog. This part should be ready in 2
months. The items at the top of the Product Backlog currently depend on this
part. What should the Product Owner do?
1. Nothing. The Developers cannot proceed with work until the dependency
is resolved.
2. Transfer the dependent Items to the Integration Team list
3. Remove the dependent Items from the Product Backlog and put them in a
special waiting
4. Make sure the dependency is visible in the Product Backlog and the
Developers have enough independent Product Backlog items for the next
Sprint.
explanation
The Product Backlog should make the dependency visible. Scrum Teams should deliver an Increment every Sprint.
54-A product vision describes the purpose of a product, the
intention with which the Product is being created and what it aims
to achieve for customers and users. The benefit of having a solid
product vision is ...
1. It helps identify the best time for releasing the product
2. It's a traditional concept, and there are no benefits to it
3. It helps the team stay focused and make better decisions
A product vision describes the purpose of a product, the intention
with which the Product is being created and what it aims to achieve
for customers and users. The benefit of having a solid product
vision is ...
1. It helps identify the best time for releasing the product
2. It's a traditional concept, and there are no benefits to it
3. It helps the team stay focused and make better decisions
explanation
A product vision is not mandated by Scrum. However, it is a good complimentary practice and
can be used to help align the decisions and development of the product.
55-A Product Backlog item is Done. What does it mean in Scrum?
1. The entire feature is complete
2. All tasks identified for the item are Done
3. The item is ready for user acceptance testing
4. No work left based on the Definition of Done
A Product Backlog item is Done. What does it mean in Scrum?
1. The entire feature is complete
2. All tasks identified for the item are Done
3. The item is ready for user acceptance testing
4. No work left based on the Definition of Done
explanation
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.
56-A new Increment must be available......
1. Before each planned release
2. By the end of each Sprint, before the Sprint Review
3. Every 2 Sprints
4. Whenever the user acceptance testing is complete
5. When the Scrum Master or the Product Owner asks for it
A new Increment must be available......
1. Before each planned release
2. By the end of each Sprint, before the Sprint Review
3. Every 2 Sprints
4. Whenever the user acceptance testing is complete
5. When the Scrum Master or the Product Owner asks for it
explanation
An Increment must be available by the start of the Sprint Review
57-A good practice in agile product development is to carry out
1. Yearly releases
2. Quarterly releases
3. Early and frequent releases
4. Releases after each Sprint
A good practice in agile product development is to carry out
1. Yearly releases
2. Quarterly releases
3. Early and frequent releases
4. Releases after each Sprint
explanation
Early and frequent release provides more opportunities for valuable feedback and learning.
58-A four-hour Sprint Planning event is common for Sprints that are
how long.
1. One week
2. One month
3. Two weeks
4. Three weeks
A four-hour Sprint Planning event is common for Sprints that are
how long.
1. One week
2. One month
3. Two weeks
4. Three weeks
explanation
Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints,
the event is usually shorter.
59-A Definition of Done drives the quality of work and is used to
assess when an item has been Done. Choose the explanation
statement about the Definition of Done
1. The Scrum Master creates it
2. The Definition of Done for the Scrum Team is used to assess
when work is Done and part of the Increment
3. It may vary depending on the product
4. The Definition of Done may be changed as the product is
developed
A Definition of Done drives the quality of work and is used to assess when an
item has been Done. Choose the explanation statement about the Definition of
Done
1. The Scrum Master creates it
2. The Definition of Done for the Scrum Team is used to assess when work is
Done and part of the Increment
3. It may vary depending on the product
4. The Definition of Done may be changed as the product is developed
explanation
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. Definition of
Done is created by the Scrum Team and may change as more is learned.
60-A company has three products. Which of the following
statements are true for the Product Owner accountability in this
situation?
Select 3 answers.
1. There must be one Product Owner for each product.
2. There can be only one Product Owner for each product
3. The same person could occupy the Product Owner
accountability for the 3 products.
4. The same person must be the Product Owner for all 3 products.
A company has three products. Which of the following statements
are true for the Product Owner accountability in this situation?
Select 3 answers.
1. There must be one Product Owner for each product.
2. There can be only one Product Owner for each product
3. The same person could occupy the Product Owner
accountability for the 3 products.
4. The same person must be the Product Owner for all 3 products.
explanation
When there's one product, there must be only one Product Owner, even if the product is
large and there are many Scrum Teams developing it.
61-By the end of the Sprint Retrospective, the Scrum Team should
have identified and planned improvements to increase its
effectiveness
1. True
2. False
By the end of the Sprint Retrospective, the Scrum Team should
have identified and planned improvements to increase its
effectiveness
1. True
2. False
explanation
By the end of the Sprint Retrospective, the Scrum Team should have identified and planned
improvements to increase its effectiveness.
62-Whenever work meets the Definition of Done we
have an Increment.
1. True
2. False
Whenever work meets the Definition of Done we
have an Increment.
1. True
2. False
explanation
Whenever work meets the Definition of Done we have an Increment.
63-The fundamental organizational unit of Scrum is
the Scrum Team.
1. True
2. False
The fundamental organizational unit of Scrum is the
Scrum Team.
1. True
2. False
explanation
The fundamental organizational unit of Scrum is the Scrum Team.
64-If we do not deliver a Done Increment by the end of the Sprint,
we must
1. Inspect & adapt in the Sprint Review & Sprint Retrospective
2. Cancel the Sprint
3. Replace the Developers
4. Reduce quality considerations in the Definition of Done to make
it more achievable
If we do not deliver a Done Increment by the end of the Sprint, we
must
1. Cancel the Sprint
2. Inspect & adapt in the Sprint Review & Sprint Retrospective
3. Replace the Developers
4. Reduce quality considerations in the Definition of Done to
make it more achievable
explanation
We must use empiricism to find ways to improve starting from the next Sprint. This is not uncommon
for teams new to Scrum and working through this is healthy and necessary to achieve increased agility.
65-A Sprint may be cancelled when
1. The Sprint Goal becomes obsolete
2. We cannot achieve the Sprint Goal
3. We want to change the work in the Sprint
4. We hit unforeseen problems
A Sprint may be cancelled when
1. The Sprint Goal becomes obsolete
2. We cannot achieve the Sprint Goal
3. We want to change the work in the Sprint
4. We hit unforeseen problems
explanation
A Sprint may be cancelled when the Sprint Goal becomes obsolete. This means it no longer makes
sense to work towards the Sprint Goal as it will not result in value being created. Even if we have
problems achieving it, or we realize it is unachievable, we continue using it to bring focus to the
work.
66-Only the Scrum Master is responsible for realizing the Scrum
values
1. False
2. True
Only the Scrum Master is responsible for realizing the Scrum
values
1. False
2. True
explanation
The Scrum Team is responsible for creating the right environment where the Scrum values
become realized. The Scrum Master may help with this an take a leading role towards it.
67-Trust is essential to effective Scrum
1. True
2. False
Trust is essential to effective Scrum
1. True
2. False
explanation
Without trust, it will be tough to take an empirical approach to work. Creating an
environment where the Scrum values exist help to build trust.
68-The 5 Scrum Values are
1. Courage, Focus, Commitment, Respect & Openness
2. Trust, Courage, Empiricism, Continuous Improvement &
Agile
3. Integrity, Respect, Responsibility, Servant Leadership &
Trust
4. Inspection, Adaption, Transparency, Servant Leadership &
Trust
The 5 Scrum Values are
1. Courage, Focus, Commitment, Respect & Openness
2. Trust, Courage, Empiricism, Continuous Improvement &
Agile
3. Integrity, Respect, Responsibility, Servant Leadership &
Trust
4. Inspection, Adaption, Transparency, Servant Leadership &
Trust
69-Spikes may be used to learn more about a Product Backlog
Item before development commences on that PBI
1. True
2. False
Spikes may be used to learn more about a Product Backlog Item
before development commences on that PBI
1. True
2. False
explanation
A spike is a learning activity before development begins and sometimes it may be useful to
learn more about the work to aid refinement.
70-Who is responsible for the sizing Product Backlog items
1. Developers
2. Product Owner
3. Scrum Master
4. Stakeholders
Who is responsible for the sizing Product Backlog items
1. Developers
2. Product Owner
3. Scrum Master
4. Stakeholders
explanation
The people who will do the work have the best insights into how long the work may take.
71-Scrum details the practices needed to complete Product
Backlog refinement
1. False
2. True
Scrum details the practices needed to complete Product Backlog
refinement
1. False
2. True
explanation
Scrum is a framework. As such it leaves the Scrum Team to select appropriate practices to
carry out effective Product Backlog refinement. It may take time and an empirical approach to find
them.
72-Product Backlog refinement includes
1. Breaking down and further defining Product Backlog items
2. Assigning PBI's to future Sprints
3. Assigning deadlines to PBI's
4. Ensuring we know everything about the PBI
Product Backlog refinement includes
1. Breaking down and further defining Product Backlog items
2. Assigning PBI's to future Sprints
3. Assigning deadlines to PBI's
4. Ensuring we know everything about the PBI
explanation
Product Backlog refinement includes breaking down and further defining Product Backlog items. The other
options may be desirable (or not) but are not required (or advised).
73-At least one actionable improvement must be added to the Sprint
Backlog each Sprint
1. False
2. True
At least one actionable improvement must be added to the Sprint
Backlog each Sprint
1. False
2. True
explanation
This was true until the 2020 update to the Scrum Guide. Now it may be desirable but it is not
required.
74-The purpose of the Sprint Retrospective is to plan ways to
increase quality and effectiveness
1. True
2. False
The purpose of the Sprint Retrospective is to plan ways to
increase quality and effectiveness
1. True
2. False
explanation
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.
75-The Sprint Retrospective is timeboxed to
1. 3 hours
2. 4 hours
3. 8 hours
4. 2 hours
The Sprint Retrospective is timeboxed to
1. 3 hours
2. 4 hours
3. 8 hours
4. 2 hours
explanation
The Sprint Retrospective is timeboxed to 3 hours. It is common (but not required) to shorten
the time box for Sprints shorter than 1 month.
76-Target delivery dates may be discussed in the Sprint Review
1. True
2. False
Target delivery dates may be discussed in the Sprint Review
1. True
2. False
explanation
If there are target delivery dates, then inspecting progress towards them at the Sprint
Review may be helpful.
77-A demo of the Increment must be carried out at the Sprint
Review
1. False
2. True
A demo of the Increment must be carried out at the Sprint Review
1. False
2. True
explanation
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.
78-The purpose of the Sprint Review is to inspect the outcome of
the Sprint and determine future adaptations
1. True
2. False
The purpose of the Sprint Review is to inspect the outcome of the Sprint and
determine future adaptations
1. True
2. False
explanation
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine
future adaptations.
79-The Sprint Review is attended by
1. The Scrum Team & stakeholders
2. The Scrum Team
3. The Developers
4. The Developers & Product Owner
The Sprint Review is attended by
1. The Scrum Team & stakeholders
2. The Scrum Team
3. The Developers
4. The Developers & Product Owner
explanation
The Sprint Review is attended by the Scrum Team & stakeholders
80-Developers must stand up at the Daily Scrum
1. False
2. True
Developers must stand up at the Daily Scrum
1. False
2. True
explanation
Standing up is a complimentary practice. It may help the Developers complete the Daily
Scrum in 15 minutes but it is not required.
81-The 15-minute timebox for the Daily Scrum may be
extended if more time is needed
1. False
2. True
The 15-minute timebox for the Daily Scrum may be extended if
more time is needed
1. False
2. True
explanation
Developers need to learn how to complete the Daily Scrum within 15 minutes. Detailed discussions
and problem solving will occur after the Daily Scrum and not all Developers would have to be
involved in these discussions.
82-The Daily Scrum is for the Developers to inspect their
progress towards the Sprint Goal and replan
1. True
2. False
The Daily Scrum is for the Developers to inspect their progress
towards the Sprint Goal and replan
1. True
2. False
explanation
The Daily Scrum is for the Developers to inspect their progress towards the Sprint Goal and
replan
83-The Daily Scrum does not have to happen every (working) day
1. False
2. True
The Daily Scrum does not have to happen every (working) day
1. False
2. True
explanation
The Daily Scrum takes place every working day during a Sprint. An expectation may be where
we are conducting one of the other Scrum events at the same time.
84-The Daily Scrum must be attended by the whole Scrum Team
1. False
2. True
The Daily Scrum must be attended by the whole Scrum Team
1. False
2. True
explanation
Developers must attend. Others may attend.
85-The Sprint Backlog must be complete at the end of Sprint
Planning
1. False
2. True
The Sprint Backlog must be complete at the end of Sprint Planning
1. False
2. True
explanation
A Sprint Goal and enough planned work to fill the first few days of the Sprint may be enough.
Most Scrum Team aim to go further than this.
86-The Definition of Done is an input to Sprint Planning
1. True
2. False
The Definition of Done is an input to Sprint Planning
1. True
2. False
explanation
It is necessary to know the Definition of Done in order to forecast the work for the Sprint.
87-The Sprint Goal is an output of Sprint Planning
1. True
2. False
The Sprint Goal is an output of Sprint Planning
1. True
2. False
explanation
The Sprint Goal is set in the Sprint Planning event.
88-Sprint Planning is optional
1. False
2. True
Sprint Planning is optional
1. False
2. True
explanation
The Sprint Planning event is required by Scrum at the beginning of each Sprint.
89-Sprint Planning must take at least 8 hours
1. False
2. True

.
Sprint Planning must take at least 8 hours
1. False
2. True
explanation
False. A timebox prescribes the maximum amount of time for an activity. There is no
minimum.
90-Each Sprint may be considered a short project
1. True
2. False
Each Sprint may be considered a short project
1. True
2. False
explanation
Each Sprint may be considered a short project. There is fixed time, potentially fixed budget
and planned (although not always) scope.
91-The length of a Sprint can be changed mid-Sprint if more
time is needed to create a Done Increment
1. False
2. True
The length of a Sprint can be changed mid-Sprint if more time
is needed to create a Done Increment
1. False
2. True
explanation
The Sprint timebox is designed to raise transparency over the true state of the product and
process. Adjusting it mid Sprint hides the underlying issues and reduces transparency.
92-The length of a Sprint can be changed?
1. True
2. False
The length of a Sprint can be changed?
1. True
2. False
explanation
True. Only at the beginning of a Sprint. It should be an infrequent change as we are aiming for
increased predictability and reduced complexity by having Sprints of a common length over
time.
93-No changes can be made inside a Sprint
1. False
2. True
No changes can be made inside a Sprint
1. False
2. True
explanation
Developers can change the Sprint Backlog at any time during a Sprint. Changes that do not
prevent the Scrum Team achieving the Sprint Goal are possible.
94-The maximum length of a Sprint is
1. 1 month
2. 1 week
3. 2 weeks
4. 4 weeks
The maximum length of a Sprint is
1. 1 month
2. 1 week
3. 2 weeks
4. 4 weeks
explanation
The maximum length of a Sprint is 1 month. Scrum Teams may set a Sprint length shorter or
equal to this maximum.
95-The Definition of Done is for the whole product
1. True
2. False
The Definition of Done is for the whole product
1. True
2. False
explanation
The Definition of Done is for the whole product, regardless of how many Scrum Teams are
working on it.
96-Adhering to a Definition of Done enables agility, increases
transparency and helps us manage expectations
1. True
2. False
Adhering to a Definition of Done enables agility, increases
transparency and helps us manage expectations
1. True
2. False
explanation
Adhering to a Definition of Done enables agility, increases transparency and helps us manage
expectations.
97-If we cannot produce a Done Increment we should not use
Scrum
1. False
2. True
If we cannot produce a Done Increment we should not use
Scrum
1. False
2. True
explanation
Producing Done Increments in less than a month may be a challenge, but that is the point.
Reducing the scope of work and the planning horizon increases agility, lowers risk and gives us the
possibility to deliver value sooner.
98-Delivering a Done Increment may not be possible each
Sprint
1. True
2. False
.
Delivering a Done Increment may not be possible each Sprint
1. True
2. False
explanation
Delivering a Done Increment is required by Scrum, but in reality, may not be possible each
Sprint.
99-Delivering a Done Increment each Sprint is required by
Scrum
1. True
2. False
Delivering a Done Increment each Sprint is required by
Scrum
1. True
2. False
explanation
Delivering a Done Increment each Sprint is required by Scrum.
100-An Increment must be tested
1. True
2. False
An Increment must be tested
1. True
2. False
explanation
Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments
work together. If it is not tested, can you be sure it meets the Definition of Done?
 By:

Follow me: https://www.linkedin.com/in/elhagag-abdalla-pmp%C2%AE-

pba%C2%AE-odoo%C2%AE-scrum%C2%AE-safe%C2%AE-89299a131/