Attempt 1

All questions
Question 1: 
Skipped
No one but the Scrum Team is allowed to attend the Sprint Planning.

True

False

(Correct)

Explanation
The work to be performed in the Sprint is planned at the Sprint Planning. This plan is
created by the collaborative work of the entire Scrum Team.

The Developers may also invite other people to attend to provide technical or domain
advice.

Question 2: 
Skipped
What action should a Scrum Master take if the Developers have decided that
Retrospectives are no longer necessary?

Extend the Sprint time-box in order to fit the Retrospectives.

Comply with the team's decision.

Start facilitating more productive and useful Retrospectives.

(Correct)
 

Suggest reducing the frequency of the Retrospectives.

Question 3: 
Skipped
Who is responsible for crafting the Sprint Goal at the Sprint Planning? (choose the best
answer)

The Product Owner

The Developers

The Scrum Team

(Correct)

The Scrum Master

The Key Stakeholders

Explanation
After the Developers forecast the Product Backlog items it will deliver in the Sprint, the
Scrum Team crafts a Sprint Goal.
Question 4: 
Skipped
The Sprint Backlog must be detailed enough so that…

Stakeholders can monitor progress at task level

 

The Product Owner can understand what everyone is working on

Every task is identified when the Sprint Backlog is first created

Changes in progress can be understood in the Daily Scrum

(Correct)

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.

Question 5: 
Skipped
A Daily Scrum is consistently taking longer than 15 minutes. Which statement best
describes what should be done? (select 1)

The Scrum Master should facilitate the event in a way that keeps it to the
time box

(Correct)

The Developers should leave at the end of the 15 minutes

 

A 2nd Daily Scrum should be held at the end of the day

The Developers should take the additional time that they need in the Daily
Scrum
Question 6: 
Skipped
Once the Definition of Done is decided upon, it may never change.

False

(Correct)

True
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 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.

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.
Question 7: 
Skipped
When multiple teams are working on the same product, who should make sure that
their outputs can be integrated into one Increment?

The Developers and the Product Owner

The Product Owner

The Scrum Master

The Scrum Teams

(Correct)

Explanation
It's up to the whole Scrum Teams to find their way and ensure that their outputs will
create an integrated Increment that is potentially releasable.
Question 8: 
Skipped
If it's not possible to complete the Sprint Backlog, who would try to resolve it?

The Scrum Master

The Developers and the Product Owner

(Correct)


 The Product Owner

The Scrum Team

The Developers
Explanation
First of all, it's OK of the Sprint Backlog is not complete until the end of the Sprint.
However, we would try to complete it if it's possible. When the Developers find out they
are behind schedule they will ask the Product Owner for help and the two roles together
will adjust the work (tasks), or reorder the times to make sure the highest value will be
created at the end of the Sprint.
Question 9: 
Skipped
How much work must the Developers do to a Product Backlog item they select for a
Sprint?

All development work and at least some testing

As much as they have informed the Product Owner will be done for every
Product Backlog item they select in conformance with the Definition of
Done.

(Correct)

As much as it can fit into the Sprint. Any remaining work will be transferred
to a subsequent Sprint

A proportional amount of time on analysis, design, programming, testing

and documentation
Question 10: 
Skipped
Who can do the work to ensure the Product Backlog is refined to a state that it is useful?

(Select 2)

The Business Analyst

Stakeholders

The Developers, with support from the Product Owner who is still
accountable for it

(Correct)

The Product Owner

(Correct)

Question 11: 
Skipped
A company has three products. Which two of the following are acceptable way of
forming Scrum Teams?

There can be one Product Owner for each product

(Correct)


 There must be a single Product Owner for all products

There can be a single Product Owner for all products

(Correct)

There must be a unique Product Owner for each product

Explanation
When there's one product so  one Product Backlog, there can be only one Product
Owner, even if the product is large and there are many Scrum Teams. If there are 3
products so 3 Product Backlogs, 3 different Product Owner position are needed. And it's
possible that those 3 different roles are done by the same individual.
Question 12: 
Skipped
When does inspection occur?

At the Sprint Review

Frequently, but not so often that gets in the way of work.

(Correct)

When the Product Owner finds necessary

All the time

Explanation
All Scrum events are opportunities for inspection and adaptation. Inspection makes
adaptation possible and that's why it's important. However, like anything else in Agile,
we just like to have "enough" of it.
Question 13: 
Skipped
The Increment must be released at the end of every Sprint

True

False

(Correct)

Explanation
The Increment can be released at the end of every Sprint, but it is not mandatory.
Question 14: 
Skipped
Who must attend the Daily Scrum?

The Developers and Product Owner

The Scrum Master and Product Owner

The Developers and Scrum Master

The Developers

(Correct)
 

The Scrum Team

Explanation
The Developers use the Daily Scrum to inspect progress toward the Sprint Goal and to
inspect how progress is trending toward completing the work in the Sprint Backlog. The
Daily Scrum optimizes the probability that the Developers will meet the Sprint Goal.
Everyday, the Developers should understand how it intends to work together as a self-
organizing team to accomplish the Sprint Goal and create the anticipated Increment by
the end of the Sprint.
Question 15: 
Skipped
As a Product Owner, how would you minimize the dependencies between the different
Scrum Teams working on the same product.

By creating the special Sprint to remove all the dependencies.

By asking the Scrum Master to remove that "impediment".

By identifying those dependencies and re-order the Product Backlog

accordingly.

(Correct)

By dividing the Product Backlog into several Product Backlogs for each
Scrum Teams.
Explanation
The Product Owner must take the dependencies into consideration to order the Product
Backlog (along with the value of the Product Backlog Items or any criteria that seems
relevant to the Product Owner).
Question 16: 
Skipped
Why is it important that there is only one Product Owner per product? (Choose 3
answers)

The Developers always know who determines priorities.

(Correct)

It helps the economy by increasing employment.

It is clear who is accountable for the ultimate success of the product.

(Correct)

It helps avoid barriers to effective communication and rapid decision

making.

(Correct)

The Scrum Master knows who will be his back-up whenever he goes on
vacation.
Question 17: 
Skipped
Which factor(s) should be considered when deciding to release an increment?

The risks associated with releasing

 

The cost and benefits of upgrading

Customers ability to absorb the new release

All answers are some possible things that should be considered when
deciding to release an increment

(Correct)

Question 18: 
Skipped
At the end of the Sprint, all items are done except for one that is almost done. What
should be done with this item?

It can be added to the Increment if the customer accepts it.

Demonstrate it in the Sprint Review meeting, if the item is presentable in its

current state.

Do not include it in the Increment.

(Correct)

It can be added to the Increment if the user acceptance tests are done.
Explanation
a. Everything in the Increment must be Done; i.e., 100% DONE! If an item is not done, we
won't include it in the Increment and send it back to the Product Backlog.

b. The Increment contains only 100% DONE items.

c. We only present the Increment, and the Increment contains only the DONE items.

d. The Increment contains only 100% DONE items.

Question 19: 
Skipped
Who monitors the remaining work of the Product Backlog?

The Developers

The Product Owner

(Correct)

The Scrum Team

The Scrum Master

Explanation
The Product Owner is responsible for measuring the progress of the project and
tracking the remaining work in the Product Backlog. The Developers are responsible for
measuring the progress of the Sprint and tracking the remaining work in the Sprint
Backlog.
Question 20: 
Skipped
During the Sprint Planning the Product Owner crafts a Sprint Goal.


 True

False

(Correct)

Explanation
During the Sprint Planning the Scrum Team crafts a Sprint Goal.
Question 21: 
Skipped
How much of the Sprint Backlog must be defined during the Sprint Planning meeting?

Just enough to understand design and architectural implications

The entire Sprint backlog must be identified and estimated by the end of
the Sprint planning meeting

Enough so the Developers can create its best forecast of what it can do, and
to start the first several days of the Sprint

(Correct)

Just enough tasks for the Scrum Master to be confident in the Developers'
understanding of the Sprint
Question 22: 
Skipped
Which of the following is a way of decreasing technical debt?

Improving the Definition of Done

 (Correct)

Hiring an external auditor

Explanation
There's usually room for improving the Definition of Done. A good definition will let less
technical debt pass on to the next Sprints. Technical debt is minor shortcomings in the
code that makes it less than "good enough" and therefore creates risks in the future. It
usually decreases velocity in the future (because the team has to fix the shortcomings)
and as some of the debt might remain in the final product, the maintenance cost will
increase as well. Another Agile way of reducing technical debt is continuous refactoring.
Question 23: 
Skipped
There can be multiple Definitions of Done when multiple teams are working on the
same product.

False

(Correct)

True
Explanation
According to the Scrum Guide of 2020:
"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."
Question 24: 
Skipped
When several Scrum Teams are working on the same product, what is the most
important concern from the list below?

Sharing a common Definition of Ready.

 

Reducing / eliminating dependencies between the different Scrum Teams.

(Correct)

Making sure that each Scrum Team has enough work.

Starting and ending the Sprints at the same time. 

Explanation
Minimizing the dependencies between the Scrum Teams is the main challenge of Scaled
Scrum.
Question 25: 
Skipped
What is the recommended size for a Scrum Team?

At least 9

6 or fewer people

10 or more people

10 or fewer people

(Correct)

Explanation
The Scrum Team is small enough to remain nimble and large enough to complete
significant work within a Sprint, typically 10 or fewer people. In general, we have found
that smaller teams communicate better and are more productive.
Question 26: 
Skipped
What is one way that the scrum master serves the Product Owner?

All answers are correct

By planning scrum implementations within the organization

By helping find techniques for effective Product Goal definition and Product
Backlog management

(Correct)

By coaching the Developers in self-organization

Explanation
The Scrum Master serves the Product Owner in several ways, including:

● Helping find techniques for effective Product Goal definition and Product Backlog
management;

● Helping the Scrum Team understand the need for clear and concise Product Backlog
items;

● Helping establish empirical product planning for a complex environment; and,

● Facilitating stakeholder collaboration as requested or needed.

Question 27: 
Skipped
Who is responsible for communicating the vision of the product to the Scrum Team?
 

The Developers

The Product Manager

The Scrum Master

The Product Owner

(Correct)

Question 28: 
Skipped
The Scrum Master is responsible for?

Ensuring Scrum is understood and enacted

(Correct)

Coordinating the work of the Developers

Solving all impediments

Delivering the Product on budget and to the agreed schedule

Explanation
The Scrum Master serves the organization in several ways, including:

● Leading, training, and coaching the organization in its Scrum adoption;

● Planning and advising Scrum implementations within the organization;

● Helping employees and stakeholders understand and enact an empirical approach for
complex work; and,

● Removing barriers between stakeholders and Scrum Teams.

Question 29: 
Skipped
The Product Owner must attend the Sprint Retrospective

True

(Correct)

False
Question 30: 
Skipped
Who determines when it is appropriate to update the Sprint Backlog during a Sprint?

The Product Owner

The Project Manager

The Developers

(Correct)
 

The Scrum Team

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.
Question 31: 
Skipped
A Product Owner wants advice from the Scrum Master about estimating work in Scrum.
Which of these is the guideline that a Scrum Master should give?

Scrum forbids estimating

Estimates must be in relative units

Product Backlog items must be estimated in story points

Estimates are made by the Developers

(Correct)

Estimates are made by the Product Owner, but are best checked with the
Developers
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.
Question 32: 
Skipped
How much time is required after a Sprint to prepare the next Sprint?
 

Enough time for the requirements for the next Sprint to be determined and
documented

The break between Sprints is time-boxed to 1 week for 30 days Sprints, and
usually less for shorter sprints

All of the above are allowed depending on the situation

Enough time for the Developers to finish the testing from the last Sprint

None. A new Sprint starts immediately after the end of the previous Sprint

(Correct)

Question 33: 
Skipped
Which of the following is a valid service from the Scrum Master to the Product Owner?
(choose the best answer)

Act as the middleman between the Product Owner and the Developers, as
requested or required

Helping find techniques for effective Product Goal definition and Product
Backlog management.

(Correct)
 

Helping the Product Owner order the Product Backlog items in order to
maximize value.

Act as a proxy when the Product Owner is not available to the team.
Explanation
The Scrum Master serves the Product Owner in several ways, including:

● Helping find techniques for effective Product Goal definition and Product Backlog
management;

● Helping the Scrum Team understand the need for clear and concise Product Backlog
items;

● Helping establish empirical product planning for a complex environment; and,

● Facilitating stakeholder collaboration as requested or needed.

Question 34: 
Skipped
As a Scrum Master, what would you strive for if five new Scrum Teams were to work on
one product?

There should be five Product Owners, one for each Scrum Team.

There should be five Product Backlogs and one Product Owner to manage
them.

The product has one Product Backlog and one Product Owner.

(Correct)
 

There should be five Product Backlogs and five Product Owners.

Explanation
For a single product there is one Product Backlog. For a single Product Backlog there is
one Product Owner.
Question 35: 
Skipped
A first Sprint can start before the Product Owner has a complete and exhaustive Product
Backlog in place.

True

(Correct)

False
Explanation
A first Sprint requires no more than a Product Owner, a team, and enough ideas to
potentially complete a full Sprint.
Question 36: 
Skipped
Which of the following describe the Definition of Done? (choose 2 answers)

Ensures everything is documented

Helps ensure the Increment is releasable

(Correct)


 Increases transparency

(Correct)

Helps increase velocity

Explanation
Definition of Done increases transparency because everyone knows what it means by
"Done". It includes everything required for creating something usable by the end users
(potentially releasable).
Question 37: 
Skipped
Management need to monitor progress on a daily basis and decide to do so by
attending the Daily Scrum. What are the likely results?

Management will be able to better direct the work of the Developers

The Scrum Master may need to enforce the rule that only Developers
participate in the Daily Scrum

(Correct)

The Developers may end up with less time in the Daily Scrum to re-plan
their work

(Correct)

Additional facilitation may be required to keep to the time box

(Correct)
 

The Developers may be less open and transparent during the Daily Scrum

(Correct)

Question 38: 
Skipped
When multiple teams are working on the same product, a Developer can be a member
of more than one Scrum Team.

False

True

(Correct)

Explanation
The Scrum Guide doesn’t prohibit it even though it is not considered best practice.

None of the Scrum roles are necessarily full-time, and a single person can occupy more
than one role or the same role in more than one team; e.g., there may be a special
expertise that is needed in multiple teams, but it's not needed in a full-time basis. So,
one person can provide that special type of expertise to multiple teams.
Question 39: 
Skipped
Which of the following is mandatory in Scrum?

Sprint Backlog

(Correct)


 Value Points

Burn-down charts

Planning Poker
Explanation
a. This is what you can use to estimate the size of items better. It's not mandatory
though.

c. You can use any form of progress measurement, tracking, and visualization.

d. This is what some people use to vote on the value of items and use them to order the
items in the Product Backlog.

Only the roles, events, and artifacts (+ Definition of Done and progress measurement)
are mandatory.

Question 40: 
Skipped
What type of test should be done during the Sprint?

Unit tests

All tests, except for integration tests

Every type of test

(Correct)


 All tests, except for user acceptance tests
Explanation
Remember that the Increment has to be "Done", and potentially releasable. It means
that all tests should be done
Question 41: 
Skipped
What does it mean for a Scrum Team to be cross-functional?

The Scrum Team includes cross-skilled individuals who are able to

contribute to do what is necessary to deliver an increment of product

(Correct)

The Scrum Team is a virtual team drawing from separate teams of business
analysts, architects, developers and testers

Developers in the Scrum Team work closely with business analysts,

architects, developers and testers who are not on the team

The Scrum Team includes not only developers but also business analysts,
architects, developers and testers
Explanation
Scrum Teams are cross-functional, meaning the members have all the skills necessary to
create value each Sprint. They are also self-managing, meaning they internally decide
who does what, when, and how.
Question 42: 
Skipped
Who participates in the Sprint Planning? (choose the best three answers)

The Technical Architect

 

The Key Stakeholders

The Scrum Master

(Correct)

The Developers

(Correct)

The Product Owner

(Correct)

Explanation
The work to be performed in the Sprint is planned at the Sprint Planning. This plan is
created by the collaborative work of the entire Scrum Team.
Question 43: 
Skipped
Which of the following is required by Scrum?

Sprint Burndown Chart

Release Planning


 Members must stand up at the Daily Scrum

All of the above

Sprint Retrospective

(Correct)

Explanation
Scrum prescribes four formal events for inspection and adaptation:

- Sprint Planning

- Daily Scrum

- Sprint Review

- Sprint Retrospective

Question 44: 
Skipped
If the costs exceed the benefits of releasing an increment, the Scrum Team may decide
to delay the release of that increment.

True

(Correct)

False
Explanation
The Scrum Team's job is the maximize the value of the product.
Question 45: 
Skipped
Which of the following does NOT apply to/suit Scrum?

Static requirements

(Correct)

Process framework used to address complex products

Based on empirical process control

Difficult to master
Explanation
Agile is all about depending on adaptation, instead of predictive (static, upfront) plan
and design.
Only the market / users validate our assumptions and we learn from our own
experience.
Question 46: 
Skipped
Which statements are correct about Product Backlog refinement? (Choose 2 answers)

The Scrum Master should facilitate it

It should be done right before the Sprint Planning

Multiple teams may participate

(Correct)
 

It is the act of breaking down and further defining Product Backlog items
into smaller more precise items

(Correct)

Explanation
Product Backlog refinement is the act of breaking down and further defining Product
Backlog items into smaller more precise items. This is an ongoing activity to add details,
such as a description, order, and size. Attributes often vary with the domain of work.

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.

Question 47: 
Skipped
When is it time to integrate the code?

At the end of the project

At the end of each Sprint

Frequently, during the Sprint

(Correct)

Before each release

Explanation
You can't know if the code will work properly, unless you integrate it with the rest of the
code. That's why we have continuous integration in Agile, which can happen multiple
times a day.
Question 48: 
Skipped
Which best describes the Product Backlog?

It provides just enough information to enable Scrum Team to start the

design phase of a product

It is allowed to grow and change anytime as more is learned about the

product and its customers

(Correct)

It contains all foreseeable tasks and requirements from which the Scrum
Team can develop and maintain a complete project plan

It is baselined to follow change management process

Explanation
Requirements never stop changing, so a Product Backlog is a living artifact. Changes in
business requirements, market conditions, or technology may cause changes in the
Product Backlog.
Question 49: 
Skipped
Which statements are correct about Sprint Retrospective meeting? (Choose 2 answers)

The Product Owner doesn't have to be at the meeting

It's three hours maximum

(Correct)
 

It's an opportunity for inspection and adaptation

(Correct)

It happens before the Sprint Review

It's the only time improvement are planned for the project
Explanation
The Sprint Retrospective happens after the Sprint Review; it's the last event in the Sprint.
It's three hours in a one-month Sprint and all Scrum Team members attend it. Its
purpose is planning for improvements in the process (the way we're working), but it's
not the only time we try to improve. Similar to Sprint Planning, Sprint Review and Daily
Scrum, it's an opportunity for inspection and adaptation.
Question 50: 
Skipped
What type of process control is Scrum?

Modern

Empirical

(Correct)

Traditional


 Adaptive
Explanation
Scrum is empirical; based on the real-world experiences. It asserts that knowledge
comes from experience and making decisions based on what is known. In order to do
so, Scrum employs an iterative, incremental approach to optimize predictability and
control risk.
Question 51: 
Skipped
Which three of the following are true about Scrum?

Choose 3 answers.

Each component of Scrum serves a specific purpose, and is essential to

Scrum's success and your usage of Scrum to develop complex products

(Correct)

Scrum is like traditional processes but with self-organization to replace

Project managers

Scrum is a framework for developing and sustaining complex products

(Correct)

Scrum is a methodology, where you can pick and choose which parts of
Scrum you think will work for your environment

Scrum is based on empirical process control theory

 (Correct)

Explanation
Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts
that knowledge comes from experience and  making decisions based on what is known.
Scrum employs an iterative, incremental approach to optimize predictability and control
risk.

Three pillars uphold every implementation of empirical process control: transparency,

inspection, and adaptation.

Question 52: 
Skipped
For the purpose of transparency, when does Scrum say a new increment must be
available?

Before the release Sprint

At the end of every Sprint

(Correct)

Every 3 Sprints

When the Product Owner asks to create one

After the acceptance testing phase

Explanation
Scrum Teams deliver products iteratively and incrementally, maximizing opportunities
for feedback. Incremental deliveries of “Done” product ensure a potentially useful
version of working product is always available.
Question 53: 
Skipped
What activities would a Product Owner typically undertake in the phase between the
end of the current Sprint and the start of the next Sprint?

Update the project plan with stakeholders

Refine the Product Backlog

There are no such activities. The next Sprint starts immediately after the
current Sprint

(Correct)

Work with the QA departments on the increment of the current Sprint

Question 54: 
Skipped
During the Sprint, the Scrum Master's role is to help the Scrum Team with which two of
the following:

Choose 2 answers

Ensure the Product Owner attends all Scrum events

Monitor the progress of the Developers


 Causing the removal of impediments

(Correct)

Assign tasks with the Scrum team

Facilitate inspection and adaptation opportunities as requested or needed

(Correct)

Escalate team conflicts to functional line managers

Explanation
The Scrum Master serves the Scrum Team in several ways, including:

● Coaching the team members in self-management and cross-functionality;

● Helping the Scrum Team focus on creating high-value Increments that meet the
Definition of Done;

● Causing the removal of impediments to the Scrum Team’s progress; and,

● Ensuring that all Scrum events take place and are positive, productive, and kept within
the timebox.

Question 55: 
Skipped
When does the second Sprint start?

Immediately after the first Sprint

(Correct)
 

After the Product Backlog for the second Sprint has been selected

Once the architectural changes for the second Sprint have been approved by
the senior architect

After the customer completes acceptance testing of the first Sprint

Explanation
A new Sprint starts immediately after the conclusion of the previous Sprint.
Question 56: 
Skipped
When a product grows, it is quite possible that the Product Owner will get help from
other Product Managers and others in the organization who interact regarding the
customer facing activities and knowledge of the product marketplace. Is it a good idea
for the Product Owner to proxy or outsource some of their duties to these people (for
example, Scrum Team facing duties)?

Yes

No

(Correct)

Explanation
When a product grows, it is quite possible that the Product Owner will get help from
other Product Managers and others in the organization who interact regarding the
customer facing activities and knowledge of the product marketplace. While it is fine for
the Product Owner to be aided by the aforementioned people, it is NOT acceptable for
him/her to attempt to proxy or outsource their Product Ownership duties, especially the
Scrum Team facing duties.
Question 57: 
Skipped
Which does a self-managing Scrum Team choose?

Sprint length

Stakeholders for the Sprint Review

When to release, based on its progress

How to best accomplish its work

(Correct)

Product Backlog ordering

Question 58: 
Skipped
The Product Backlog is ordered by:

Items are randomly arranged

Size, where small items are at the top and large items are at the bottom

Risk, where safer items are at the top, and riskier items are at the bottom


 Importance and priority according to the Product Owner, where the most
important items are at the top at all times

(Correct)

Explanation
The Product Backlog is dynamic; it constantly changes to identify what the product
needs to be appropriate, competitive, and useful.
Question 59: 
Skipped
What should the Developers be able to explain by the end of sprint planning?

How they intend to complete the items selected for the sprint

(Correct)

Who will demonstrate the increment at the sprint review

What items are currently in the product backlog

What they can do to improve in the upcoming sprint

Explanation
Developers are the people in the Scrum Team that are committed to creating any aspect
of a usable Increment each Sprint.

The specific skills needed by the Developers are often broad and will vary with the
domain of work. However, the Developers are always accountable for:

● Creating a plan for the Sprint, the Sprint Backlog;

● Instilling quality by adhering to a Definition of Done;

● Adapting their plan each day toward the Sprint Goal; and,
● Holding each other accountable as professionals.

Question 60: 
Skipped
Who assigns tasks to the Developers?

The project manager

The Scrum Master

The Product Owner

Developers themselves

(Correct)

Explanation
The Developers take responsibility for doing the tasks themselves and the Developers
ensure that all tasks are done properly. Remember that they are self-managed. When
items are "Done", the Product Owner checked them but this is focused on the item
rather than individuals; all Developers are accountable for the team's outputs.
Question 61: 
Skipped
Which of the following refers to the average amount of work done per Sprint?

Burn-down rate

Capacity


 Performance

Velocity

(Correct)

Explanation
Velocity is the amount of work (usually in "story points") done per Sprint.
Question 62: 
Skipped
How should the Developers deal with non-functional requirements?

Assign them to the lead Developers on the team

Ensure every Increment meets them

(Correct)

Make sure the release department understands these requirements, but it is

not the Developers' responsibility

Handle them during the Integration sprint preceding the release sprint
Question 63: 
Skipped
The Developers are required to deliver a done increment by the end of a Sprint. Select
two statements that explain what "done" means.

Choose 2 answers


 No work left from the Definition of Done

(Correct)

Ready for integration

All work the Developers are willing to do

All work to create an increment that is ready to be released to end users

(Correct)

Whatever the Product Owner defines as quality

Explanation
- The purpose of each Sprint is to deliver Increments of potentially releasable
functionality that adhere to the Scrum Team’s current Definition of Done.

- Developers deliver an Increment of product functionality every Sprint. This Increment is

useable, so a Scrum Team may choose to immediately release it. If the Definition of
Done for an increment is part of the conventions, standards or guidelines of the
development organization, all Scrum Teams must follow it as a minimum.
Question 64: 
Skipped
If burndown charts are used to visualize progress, what does a trend through a release
burndown chart indicates

The evolution of the cost spent on the project


 When the project will be over if the Product owner removes work that is
equal in effort to any new work that is added

When the work remaining will likely be completed if nothing changes on

the Product Backlog or the Scrum Team

(Correct)

When all work will be completed so the Scrum Team can be released for
other work
Question 65: 
Skipped
What are three benefits of self-organization?

Choose 3 answers.

Increased commitment

(Correct)

Increase rule compliance

Increased accuracy of estimates

Increased creativity

(Correct)
 

Increased self-accountability

(Correct)

Explanation
Scrum Teams are self-managing and cross-functional. Self-managing teams choose how
best to accomplish their work, rather than being directed by others outside the team.
Question 66: 
Skipped
Who is responsible for tracking the remaining work of the Sprint?

The Scrum Master

The Developers

(Correct)

The Product Owner

The Developers in consultation with the Product Owner

The Project Manager

Explanation
Developers are structured and empowered by the organization to organize and manage
their own work. The resulting synergy optimizes the Developers' overall efficiency and
effectiveness.

The Product Owner is responsible for measuring the progress of the project, and
tracking the remaining work in the Product Backlog.
The Developers are responsible for measuring the progress of the Sprint, and tracking
the remaining work in the Sprint Backlog.
Question 67: 
Skipped
If an item in the Sprint Backlog cannot be finished by the end of the Sprint (it turned out
there is a lot more work to do than was estimated), the Sprint is cancelled and a new
Sprint is created with a more realistic scope.

True

False

(Correct)

Explanation
The Sprint is cancelled only in the case if the Sprint Goal became obsolete. If some work
could not be done, the Sprint Backlog should be renegotiated between the Product
Owner and the Developers.
Question 68: 
Skipped
Technical debt… (choose the best three answers)

belongs entirely to the Developers. No one else needs to know about it.

is a real risk which can genuinely be incurred

(Correct)

compromises long-term quality of the Product

 (Correct)

reflects some extra development work

(Correct)

is a lack of technical supplies

Explanation
Technical debt is a concept in programming that reflects the extra development work
that arises when code that is easy to implement in the short run is used instead of
applying the best overall solution. In other words it can be defined as the longer term
consequences of poor design decisions. Technical debt is a real risk which can genuinely
be incurred. It compromises long-term quality of the Product. One of the ways of
handling technical debt is recording it on the Product Backlog. So, it becomes visible to
the Scrum Team.
Question 69: 
Skipped
Which of these may a Scrum Team deliver at the end of a Sprint?

Failing unit tests, to identify acceptance tests for the next Sprint

A single document, if that is what the Scrum Master asked for

An increment of working product that is "done"

(Correct)


 An increment of with minor known defects / bugs in it
Explanation
Scrum Teams deliver products iteratively and incrementally, maximizing opportunities
for feedback. Incremental deliveries of “Done” product ensure a potentially useful
version of working product is always available.
Question 70: 
Skipped
Which of the following is a prerequisite for starting the Sprint Planning meeting?

Having the Product Backlog items cleared and assigned to developers

None

(Correct)

Having the items at the top of the Product Backlog small enough to fit in
one Sprint

Having the requirements specified and completely reflected in the Product

Backlog
Explanation
We prefer to have "ready" items at the top of the Product Backlog before Sprint
Planning, which is done through Product Backlog refinement. However, nothing stops
our flow of Sprints. For example, we do not delay the Sprint because the items are not
ready. In such cases, the "unready" items would be selected for the Sprint and refined
during the Sprint. "Ready" items are those that are clear and small enough to fit into
one Sprint.
Question 71: 
Skipped
When multiple Scrum Teams are working on the same product, their Sprints should start
and end at the same time.
 

False

(Correct)

True
Explanation
It's not mandatory in Scrum.org to start and end the Sprints at the same time. That
makes it much more difficult to manage the whole project. It's not mandatory, because
you may need it in certain cases: maybe some teams are working on parts of the project
that need longer Sprints (four-week), while others need shorter ones (two-week) for
shorter feedback loops.
Question 72: 
Skipped
The Sprint Backlog is crafted via the answers of these 3 questions : Why, What and How

True

(Correct)

False
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.
Question 73: 
Skipped
If several Scrum Teams are working on the same product, each Scrum Team should
operate with their own separate Product Backlog?

False

(Correct)

True
Explanation
The different Scrum Teams working on the same product must use the same Product
Backlog for which the same Product Owner is accountable.

Remember : 1 product = 1 Product Owner = 1 Product Backlog

Question 74: 
Skipped
A product increment must be released to production at the end of each Sprint

True

False

(Correct)

Explanation
An increment is a body of inspectable, done work that supports empiricism at the end of
the Sprint. The increment is a step toward a vision or goal. The increment must be in
useable condition regardless of whether the Product Owner decides to release it.
Question 75: 
Skipped
The Scrum Team is empowered by the organization to manage their own work.
 

False

True

(Correct)

Explanation
Scrum Teams are cross-functional, meaning the members have all the skills necessary to
create value each Sprint. They are also self-managing, meaning they internally decide
who does what, when, and how.
Question 76: 
Skipped
Which are properties of the Daily Scrum?

Choose 2 answers.

It is fifteen minutes in duration

(Correct)

It is held first thing in the morning

Its location and time should remain constant

(Correct)


 It is facilitated by the team lead
Explanation
The Daily Scrum is a 15-minute event for the Developers. The Daily Scrum is held every
day of the Sprint. At it, the Developers plan work for the next 24 hours. This optimizes
team collaboration and performance by inspecting the work since the last Daily Scrum
and forecasting upcoming Sprint work. The Daily Scrum is held at the same time and
place each day to reduce complexity.
Question 77: 
Skipped
At the Sprint Planning, who is responsible for ensuring that attendees are prepared to
discuss the most important Product Backlog items and how they map to the Product
Goal?

The Product Owner

(Correct)

The Scrum Master

The Developers

The Scrum Master and The Developers

The Product Owner and The Developers

The Scrum Team

Explanation
At the Sprint Panning, Product Owner ensures that attendees are prepared to discuss
the most important Product Backlog items and how they map to the Product Goal.
Question 78: 
Skipped
Which three questions may be answered by all Developers at the Daily Scrum?

Choose 3 answers

What work am I going to do today to help the team achieve its goal?

(Correct)

What work did I do yesterday to help the team achieve its goal?

(Correct)

How is the Sprint proceeding?

How many hours did I spend on the project yesterday?

Why were you late?

What impediments are in my way or in the way of the team?

(Correct)

Explanation
The Developers can select whatever structure and techniques they want, as long as their
Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable
plan for the next day of work. This creates focus and improves self-management.
Question 79: 
Skipped
Which commitment from the Sprint Planning provides the Developers with a target and
overarching direction for the Sprint?

The release plan

The Sprint Goal

(Correct)

The Sprint Backlog

Sprint Review minutes

Explanation
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 is created during the Sprint Planning meeting. The Sprint Goal
gives the Developers some flexibility regarding the functionality implemented within the
Sprint. The selected Product Backlog items deliver one coherent function, which can be
the Sprint Goal. The Sprint Goal can be any other coherence that causes the Developers
to work together rather than on separate initiatives.
Question 80: 
Skipped
Which are considered Scrum Values. (choose all that apply)

Self-organization
 

Commitment

(Correct)

Focus

(Correct)

Openness

(Correct)

Respect

(Correct)

Courage

(Correct)

Explanation
Successful use of Scrum depends on people becoming more proficient in living five
values:

Commitment, Focus, Openness, Respect, and Courage

Question 81: 
Skipped
What are three ways Scrum promotes self-management?

Choose 3 answers

By preventing stakeholders from entering the development room

By being a lightweight framework

(Correct)

By removing titles for Developers

(Correct)

By not allowing documentation

By the Developers deciding what work to do in a Sprint

(Correct)

Question 82: 
Skipped
When multiple Scrum Teams are working on the same product, should they integrate all
their work into a single functional increment every Sprint?

Yes, so that the whole Scrum Team and the Stakeholders can inspect a full
piece of functionality at the Sprint Review.
 (Correct)

Yes, but only for the Scrum Teams whose work have dependencies between
each others.

No, because it's not mandatory that the increment is fully integrated at each
Sprint. The integration can be done during "Integration Sprints".

No, because every Scrum Team is self-managed and independent and works
on their own.
Explanation
The Scrum Teams in a Nexus (Scaled Scrum) produce a single Integrated Increment
every Sprint.

The Nexus Sprint Review is held at the end of the Sprint to provide feedback on
the done Integrated Increment that the Nexus has built over the Sprint and determine
future adaptations.

See the The Nexus TM Guide of 2021.

Question 83: 
Skipped
A Scrum Team is only allowed to meet the stakeholders during the Sprint Review

True

False

(Correct)

Explanation
A Scrum Team can meet the stakeholders whenever they want, whenever it makes
sense.
Question 84: 
Skipped
The Product Owner manages… (select 1)

The Developers

The Product Backlog

(Correct)

The Project

The Scrum Team

Explanation
The Product Owner is accountable for effective Product Backlog management, which
includes:

● Developing and explicitly communicating the Product Goal;

● Creating and clearly communicating Product Backlog items;

● Ordering Product Backlog items; and,

● Ensuring that the Product Backlog is transparent, visible and understood.

Question 85: 
Skipped
In order to start the first Sprint, Scrum only requires a Product Owner with enough ideas,
Developers to execute on those ideas, and a Scrum Master to guide the process.


 False

True

(Correct)

Explanation
In complex domains, you are only able to know the outcomes in hindsight. Empiricism,
from which Scrum was founded on, asserts that knowledge comes from experience and
making decisions based on what is known. New knowledge will emerge as work is being
done.
Question 86: 
Skipped
How does the Definition of Done help to the Scrum Team?  (Choose the BEST three
answers)

Definition of Done is used to assess when work is complete on the product

Increment.

(Correct)

Definition of Done helps in inspection and adaptation.

Definition of Done helps to calculate velocity of the Scrum Team.

Definition of Done ensures artifact transparency.

(Correct)


 Definition of Done guides the Developers in knowing how many Product
Backlog items it can select during a Sprint Planning.

(Correct)

Explanation
Definition of Done is used to assess when work is complete on the product Increment.
Guides the Developers in knowing how many Product Backlog items it can select during
a Sprint Planning. Definition of Done ensures artifact transparency.
Question 87: 
Skipped
Which two metrics will help a Product Owner establish that value is being delivered?

Productivity

Velocity

Customer satisfaction

(Correct)

Time to market

(Correct)

Budget
Explanation
EBM guide: Customer Satisfaction KVM and Time to Market KVA.
Budget, velocity and productivity do not contribute directly to capturing Product value.
Question 88: 
Skipped
How does the Scrum Master help the Product Owner? (choose the best three answers)

Helping find techniques for effective Product Goal definition and Product
Backlog management

(Correct)

Introducing cutting edge development practices

Helping the Scrum Team understand the need for clear and concise Product
Backlog items

(Correct)

Helping establish empirical product planning for a complex environment

(Correct)

Leading and coaching the organization in its Scrum adoption

Explanation
The Scrum Master serves the Product Owner in several ways, including:

● Helping find techniques for effective Product Goal definition and Product Backlog
management;

● Helping the Scrum Team understand the need for clear and concise Product Backlog
items;
● Helping establish empirical product planning for a complex environment; and,

● Facilitating stakeholder collaboration as requested or needed.

Question 89: 
Skipped
Which topics should be discussed at the Sprint Review?

Coding and engineering practices

The Scrum process, and how it was used during the Sprint

All of the above

Sprint results

(Correct)

Explanation
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine
future adaptations. The Scrum Team presents the results of their work to key
stakeholders and progress toward the Product Goal is discussed.

During the event, the Scrum Team and stakeholders review what was accomplished in
the Sprint and what has changed in their environment. Based on this information,
attendees collaborate on what to do next. The Product Backlog may also be adjusted to
meet new opportunities. The Sprint Review is a working session and the Scrum Team
should avoid limiting it to a presentation.

The Sprint Review is the second to last event of the Sprint and is timeboxed to a
maximum of four hours for a one-month Sprint. For shorter Sprints, the event is usually
shorter.

Question 90: 
Skipped
What are two responsibilities of testers among the Developers?

Choose 2 answers

Scrum has no "tester" role

(Correct)

Finding bugs

Tracking quality metrics

Verifying the work of programmers

Every Developer is responsible for quality

(Correct)

Question 91: 
Skipped
When is the Sprint Backlog created?

At the beginning of the project

Prior to the Sprint Planning meeting

 

During the Sprint

During the Sprint Planning meeting

(Correct)

Explanation
The work to be performed in the Sprint is planned at the Sprint Planning. This plan is
created by the collaborative work of the entire Scrum Team.

Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For
shorter Sprints, the event is usually shorter. The Scrum Master ensures that the event
takes place and that attendants understand its purpose. The Scrum Master teaches the
Scrum Team to keep it within the time-box.

Sprint Planning answers the following:

- What can be delivered in the Increment resulting from the upcoming Sprint?

- How will the work needed to deliver the Increment be achieved?

Question 92: 
Skipped
The Product Owner’s authority to change and update the Product Backlog is unlimited,
except for:

High impact changes that have not been approved by the change request
board.

Technical and architectural work that needs to be done first, as indicated by

the chief enterprisearchitect.


 Work for which impediments exist that the Scrum Master still needs to
resolve

Decisions by the CFO, the CEO or the board of directors.

Nothing. The entire organization must respect a Product Owner's decisions.

(Correct)

Decisions by the chief program manager.

Question 93: 
Skipped
What enhances the transparency of an increment?

Doing all work needed to meet the Definition of Done

(Correct)

Reporting Sprint progress to the stakeholders daily

Keeping track of and estimating all undone work to be completed in a

separate Sprint

Updating sprint tasks property in the electronic tracking tool

Explanation
When a Product Backlog item or an Increment is described as “Done”, everyone must
understand what “Done”  means. Although this may vary significantly per Scrum Team,
members must have a shared understanding of what it means for work to be complete,
to ensure transparency.
Question 94: 
Skipped
When does the next Sprint begin?

Next Monday

Immediately after the conclusion of the previous Sprint

(Correct)

Immediately following the next Sprint Planning

When the Product Owner is ready

Question 95: 
Skipped
Scrum is an iterative and incremental Agile framework.

False

True

(Correct)

Explanation
Scrum is iterative because processes are repeated in each Sprint. It's incremental
because it delivers the product in multiple incremental steps instead of in a big bang.
And of course it's Agile (adaptive instead of predictive).
Question 96: 
Skipped
The purpose of the Sprint Review is…

To check what was done and not done during the Sprint

To inspect the Increment and adapt the Product Backlog

(Correct)

To show Stakeholders work that is done and work that is near to completion

To review the status of the Project

Explanation
The Scrum Review is also an opportunity to collect customer / user feedback from the
Stakeholders.
Question 97: 
Skipped
At the Sprint Retrospective meeting the Scrum Team identified some improvements that
can be done. What could the Scrum Team do? (choose the best answer)

Assign responsible team members for every improvement. Check the

progress at the next Retrospective.

Put the improvements to the Product Backlog and might choose some to
the Sprint Backlog.
 (Correct)

Assign a responsible team member for at least one improvement. Check the
progress at the next Retrospective.

Make sure the Sprint Backlog for the next Sprint includes all the
improvements.
Explanation
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.
Question 98: 
Skipped
Which statement best describes Scrum?

A framework to address complex products in complex environments.

(Correct)

A clearly defined methodology that defines the product development

process.

A manual for defining best practices for product development.

A clearly defined and predictable process that follows the principles of

Computer Science.
Explanation
Scrum is a framework for developing, delivering, and sustaining complex products. This
Guide contains the definition of Scrum. This definition consists of Scrum’s roles, events,
artifacts, and the rules that bind them together. Ken Schwaber and Jeff Sutherland
developed Scrum; the Scrum Guide is written and provided by them. Together, they
stand behind the Scrum Guide.
Question 99: 
Skipped
Which of the following may change during the Sprint?

Product Backlog

(Correct)

Sprint Goal

Composition of the team

Minimum level of quality

Explanation
a. The team stays the same during the Sprint. If you need to change it, wait until the
beginning of the next Sprint.

b. The level of expected quality shouldn't decrease during the Sprint.

c. The Sprint Goal doesn't change after the Sprint Planning meeting

d. Product Backlog may change at any time.

Those that stay fixed during the Sprint are needed to avoid distractions, and create a
more productive environment. After all, Sprints are not so long that they create
problems.

Question 100: 
Skipped
For a 1 month sprint, select the best time-box for each Scrum event

Sprint Planning : 8 hours or less, Daily Scrum : 15 minutes or less, Sprint

Review : 4 hours or less, Sprint Retrospective : 3 hours or less.

(Correct)

Sprint Planning : 8 hours or less, Daily Scrum : 30 minutes or less, Sprint

Review : 4 hours or less, Sprint Retrospective : 3 hours or less.

Sprint Planning : 4 hours or less, Daily Scrum : 15 minutes or less, Sprint

Review : 4 hours or less, Sprint Retrospective : 4 hours or less.

Sprint Planning : 4 hours or less, Daily Scrum : 15 minutes or less, Sprint

Review : 8 hours or less, Sprint Retrospective : 4 hours or less.
Question 101: 
Skipped
Which Scrum Value is impacted by trust?

Respect

Openness

Commitment


 Courage

Focus

All of the above

(Correct)

Explanation
Successful use of Scrum depends on people becoming more proficient in living five
values:

Commitment, Focus, Openness, Respect, and Courage

Without trust, team members will have difficulties acting and behaving in the ways that
reflect the Scrum values and how effective they apply empiricism.

Question 102: 
Skipped
Who can do the legwork of gathering the marketplace data for the Product Owner?
(choose the best answer)

Only the Product Owner

The Scrum Team

Anyone can do the legwork

(Correct)


 Subject matter experts
Explanation
The Product Owner may or may not be the one doing the legwork of gathering the
marketplace data, but he/she should definitely be aware of said data/research.
Question 103: 
Skipped
It is good practice to have at least two Product Owners on larger projects.

False

(Correct)

True
Explanation
When you have 1 project for creating 1 product, there would be only 1 Product Backlog
and 1 Product Owner. Having more than one Product Backlog makes it hard to prioritize
the items and having more than one Product Owner might create inconsistency in the
system.
Question 104: 
Skipped
Which of the following is required by Scrum?

Story Points

Test-Driven Development

Release planning

Having timeboxed events

 (Correct)

Question 105: 
Skipped
Who determines how work is performed during the Sprint?

Subject matter experts

The Scrum Master

The Developers

(Correct)

Scrum Team Managers

Architects
Explanation
Developers are the people in the Scrum Team that are committed to creating any aspect
of a usable Increment each Sprint.

The specific skills needed by the Developers are often broad and will vary with the
domain of work. However, the Developers are always accountable for:

● Creating a plan for the Sprint, the Sprint Backlog;

● Instilling quality by adhering to a Definition of Done;

● Adapting their plan each day toward the Sprint Goal; and,

● Holding each other accountable as professionals.

Question 106: 
Skipped
What would likely happen if management only changed the organization's current
terminology to fit Scrum without the proper understanding and support of Scrum as
defined in the Scrum Guide?

All answers apply.

(Correct)

Very little change will happen as the vocabulary in Scrum is specifically

defined for implementing Scrum.

Organizations may feel less stressed as the behaviors would remain familiar
to management.

The organization may not realize the real benefits of Scrum as there would
be no real change on the way the teams work.
Explanation
The the defined terminology in Scrum was selected, designed, and defined specifically
for supporting the Scrum Framework. Understanding the differences between traditional
methods and the Scrum Framework will help move teams in the right direction in Scrum
adoption.
Question 107: 
Skipped
How often should the Developers change within the Scrum Team?

As needed while taking into account a short-term reduction in productivity

(Correct)
 

Never, because it reduces productivity

As needed, with no special allowance for changes in productivity

Every Sprint to promote shared learning

Question 108: 
Skipped
What is the maximum duration of a Sprint Planning?

4 hours

6 hours

3 hours

8 hours

(Correct)

Explanation
Sprint Planning is 8 hours for a one-month Sprint and usually shorter proportionally for
shorter Sprints (best practice but not mandatory).
Question 109: 
Skipped
Which of the following is not a pillar of Scrum?


 Empiricism

(Correct)

Transparency

Inspection

Adaptation
Explanation
The three pillars of Scrum are adaptation, inspection and transparency. Scrum is based
on empiricism but it's not one of the pillars.
Question 110: 
Skipped
Every Scrum Team should have:

At least one representative from each major software engineering discipline

(like QA, Dev, UX)

The competencies and skills needed to deliver a Done Increment in a Sprint

(Correct)

One lead Developer and no more than 8 other members

Explanation
The fundamental unit of Scrum is a small team of people, a Scrum Team. The Scrum
Team consists of one Scrum Master, one Product Owner, and Developers. Within a
Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals
focused on one objective at a time, the Product Goal.

Scrum Teams are cross-functional, meaning the members have all the skills necessary to
create value each Sprint. They are also self-managing, meaning they internally decide
who does what, when, and how.

Question 111: 
Skipped
Which two of the following are correct about the Product Owner role?

Explains the Product Backlog items

(Correct)

Is the only person who can add items to the Product Backlog

Participates in the Daily Scrum meeting

Is accountable for all changes to the Product Backlog

(Correct)

Can make changes to the Sprint Backlog

Question 112: 
Skipped
A Scrum Team uses 2-week Sprints and time box their Sprint Planning to 6 hours. Does
this break the rules of Scrum?


 Yes

No

(Correct)

Explanation
The concept of "event duration proportional to the sprint duration" used to be
mandatory but it has been abandoned in the last updates of the Scrum Guide. It's now
only best practice but not mandatory so no rule is broken here.
Question 113: 
Skipped
When the Developers of the Scrum Team determine that it has over-committed itself for
a Sprint, who has to be present when reviewing and adjusting the Sprint work selected?

The Developers

The Scrum Master, project manager and the Developers

The Product Owner and all stakeholders

The Product Owner and the Developers

(Correct)

Explanation
If the Developers determine it has too much or too little work, it may renegotiate the
selected Product Backlog items with the Product Owner.
Question 114: 
Skipped
Who can change the Sprint Backlog in the middle of the Sprint?
 

Only the Scrum Master

Only the Developers

(Correct)

The Scrum Team

Only the Product Owner

Explanation
Only the Developers can change its Sprint Backlog during a Sprint. As new work is
required, the Developers add it to the Sprint Backlog. As work is performed or
completed, the estimated remaining work is updated. When elements of the plan are
deemed unnecessary, they are removed.
Question 115: 
Skipped
Who identifies the Key Stakeholders for the Product?

The Upper Management

The Developers

The Scrum Master


 The Product Owner

(Correct)

The Scrum Team

Question 116: 
Skipped
What's the optimal length of a Sprint?

One week

Short enough to minimize risk

(Correct)

Two weeks

One month
Explanation
We prefer shorter Sprints as long as we can produce enough output. Shorter Sprints
reduce the risk to the business.
Question 117: 
Skipped
What are the two primary ways a Scrum Master keeps the Scrum Team working at its
highest level of productivity?

Choose 2 answers.


 By keeping high value features high in the Product backlog

Helping the Scrum Team focus on creating high-value Increments that meet
the Definition of Done

(Correct)

Creating a plan for the Sprint, the Sprint Backlog

Causing the removal of impediments to the Scrum Team’s progress

(Correct)

Explanation
The Scrum Master serves the Scrum Team in several ways, including:

● Coaching the team members in self-management and cross-functionality;

● Helping the Scrum Team focus on creating high-value Increments that meet the
Definition of Done;

● Causing the removal of impediments to the Scrum Team’s progress; and,

● Ensuring that all Scrum events take place and are positive, productive, and kept within
the timebox.

Question 118: 
Skipped
The Product Goal is a short-term objective for the Scrum Team.

True


 False

(Correct)

Explanation
The Product Goal describes a future state of the product which can serve as a target for
the Scrum Team to plan against. The Product Goal is in the Product Backlog. The rest of
the Product Backlog emerges to define “what” will fulfill the Product Goal.

A product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-
defined users or customers. A product could be a service, a physical product, or something
more abstract.

The Product Goal is the long-term objective for the Scrum Team. They must fulfill
(or abandon) one objective before taking on the next.

Question 119: 
Skipped
The result of the Sprint Review is…

A revised Product Backlog that defines the probable Product Backlog items
for the next Sprint

(Correct)

Acceptance (or rejection) of all Product Backlog Items

Incomplete Product Backlog Items have been reviewed and returned to the
top of the Product Backlog

The Increment has been demonstrated to Stakeholders

Explanation
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine
future adaptations. The Scrum Team presents the results of their work to key
stakeholders and progress toward the Product Goal is discussed.

The Scrum Review is also an opportunity to collect customer / user feedback from the
Stakeholders.

During the event, the Scrum Team and stakeholders review what was accomplished in
the Sprint and what has changed in their environment. Based on this information,
attendees collaborate on what to do next. The Product Backlog may also be adjusted to
meet new opportunities. The Sprint Review is a working session and the Scrum Team
should avoid limiting it to a presentation.

The Sprint Review is the second to last event of the Sprint and is timeboxed to a
maximum of four hours for a one-month Sprint. For shorter Sprints, the event is usually
shorter.

Question 120: 
Skipped
The practice of Product Backlog refinement focuses on items for upcoming Sprints, not
the current Sprint in progress.

False

True

(Correct)

Explanation
Product Backlog refinement is the act of adding detail, estimates, and order to items in
the Product Backlog. The Items in the current Sprint are no longer on the Product
Backlog, because they are now on the Sprint Backlog. However, it is certainly fine for the
Product Owner to add detail and clarification to the current Sprint’s work as well.