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 part2 don’t forget to checkout the other parts.
1-The Product Owner should use user stories to compose Product
Backlog items.
1. True
2. False.
The Product Owner should use user stories to compose Product
Backlog items.
1. True
2. False.

Explanation :User stories are a popular way of communicating requirements but are not
mandatory in Scrum.
2-The Product Owner wants to refine the Product Backlog. When
should Product Backlog items be refined?
1. In Sprint O
2. During the Sprint, if they have not been refined in the previous
Sprints.
3. ✔In preceding Sprints.
4. In the time between the Sprints
The Product Owner wants to refine the Product Backlog. When
should Product Backlog items be refined?
1. In Sprint O
2. During the Sprint, if they have not been refined in the previous
Sprints.
3. ✔In preceding Sprints.
4. In the time between the Sprints
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
Refinement occurs within Sprints
Refinement may occur in Sprint Planning
3-The purpose of the Daily Scrum is for the Developers is to inform
the Product Owner of their progress.
1. False.
2. True
The purpose of the Daily Scrum is for the Developers is to inform
the Product Owner of their progress.
1. False.
2. True
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.
4-The responsibility of the project manager in Scrum is to
1. Prepare the project plan
2. Authorizing the Sprints
3. There is no project manager role in Scrum.
4. Making high-level decisions
5. Planning releases
The responsibility of the project manager in Scrum is to
1. Prepare the project plan
2. Authorizing the Sprints
3. There is no project manager role in Scrum.
4. Making high-level decisions
5. Planning releases

Explanation : There is no project manager role in Scrum

5-The purpose of Scrum Master in the Sprint Retrospective is
1. Auditor
2. Silent Observer
3. Scrum Team member.
4. Manager
5. None of the above
The purpose of Scrum Master in the Sprint Retrospective is
1. Auditor
2. Silent Observer
3. Scrum Team member.
4. Manager
5. None of the above
Explanation
The Scrum Master participates as a Scrum Team member. They may also facilitate the event.
6-The Scrum Master has decided to assign each Product Backlog
Item to individuals Developers. When do Developers become the
exclusive owner of a Product Backlog item?
1. At Sprint planning
2. Never. All Product Backlog Items in a Sprint are "owned" by all
the Developers, even though each one may be worked by an
individual Developer.
3. During the Daily Scrum.
4. During the Sprint
The Scrum Master has decided to assign each Product Backlog Item
to individuals Developers. When do Developers become the
exclusive owner of a Product Backlog item?
1. At Sprint planning
2. Never. All Product Backlog Items in a Sprint are "owned" by all
the Developers, even though each one may be worked by an
individual Developer.
3. During the Daily Scrum.
4. During the Sprint
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.
7-The Scrum Master is a leader and servant in service to which of
the following?
1. The Developers
2. The Product Owner
3. The organization and Scrum Team.
The Scrum Master is a leader and servant in service to which of the
following?
1. The Developers
2. The Product Owner
3. The organization and Scrum Team.
Explanation
Scrum Masters are true leaders who serve the Scrum Team and the larger organisation.
8-The Scrum Master is a management role.
1. True.
2. False
The Scrum Master is a management role.
1. True.
2. False
Explanation
The Scrum Master is a manager, but for the Scrum framework,
rather than for the people in
the Scrum Team.
9-The Scrum Master is a participant in the Sprint Retrospective.
1. True.
2. False
The Scrum Master is a participant in the Sprint Retrospective.
1. True.
2. False
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.
10-The Scrum Master is accountable for
1. Establishing Scrum as defined in the Scrum Guide.
2. ✔Causing the removal of impediments.
3. Helping everyone understand Scrum theory and practice, both
within the Scrum Team and the organization.
4. Assigning tasks to the Scrum Team
5. Ensuring the Scrum Team always consists of 10 or fewer
members
The Scrum Master is accountable for
1. Establishing Scrum as defined in the Scrum Guide.
2. ✔Causing the removal of impediments.
3. Helping everyone understand Scrum theory and practice, both
within the Scrum Team and the organization.
4. Assigning tasks to the Scrum Team
5. Ensuring the Scrum Team always consists of 10 or fewer members
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.
The Scrum Master serves the Scrum Team in several ways, including causing the removal of impediments
11-The Scrum Master tracks the work remaining in the Product
Backlog.
1. True
2. False.
The Scrum Master tracks the work remaining in the Product Backlog.
1. True
2. False.
Explanation
A Product Owner may choose to do this.
12-The Scrum Team decides to include some specific types of
testing in the Definition of Done. What is the potential benefit of
this decision? Select all that apply.
1. Increments could be closer to being releasable
2. Increased transparency of the state of the Increment
3. Reporting would be easier for the project manager. Ch not
4. Increments would be more likely to be useable
The Scrum Team decides to include some specific types of testing in
the Definition of Done. What is the potential benefit of this
decision? Select all that apply.
1. Increments could be closer to being releasable
2. Increased transparency of the state of the Increment
3. Reporting would be easier for the project manager. Ch not
4. Increments would be more likely to be useable
Explanation
The Definition of Done creates transparency by providing everyone a shared understanding
of what work was completed as part of the Increment.
13-The Scrum Team has just begun Sprint Planning. There are a lot
of questions and in general, the Product Backlog is not clear. Due to
this, what is the maximum duration of Sprint Planning?
1. 12 hours
2. 2 hours
3. 8 hours.
4. 6 hours
The Scrum Team has just begun Sprint Planning. There are a lot of
questions and in general, the Product Backlog is not clear. Due to
this, what is the maximum duration of Sprint Planning?
1. 12 hours
2. 2 hours
3. 8 hours.
4. 6 hours
Explanation
In this case, the duration can be even more than one day
Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint.
14-The Scrum Team has just begun the first Sprint. Which of the
following must be Done in this case?
1. Planning the project
2. Creating a valuable and useful Increment.
3. Developing the product vision
4. Completing the reference architecture
5. Choosing the team leader
The Scrum Team has just begun the first Sprint. Which of the
following must be Done in this case?
1. Planning the project
2. Creating a valuable and useful Increment.
3. Developing the product vision
4. Completing the reference architecture
5. Choosing the team leader
Explanation
There is no difference between the first Sprint and subsequent ones. All Sprint are about
creating Increments to fulfil a Sprint Goal.
15-The Scrum Team has just begun Sprint Planning. How much of
the Sprint Backlog should be created during this event?
1. As a minimum, just enough, so the Developers can forecast
what it can do and provide enough of a plan for the start of the
Sprint. More planning can follow in the Sprint.
2. Just enough to understand the architecture
3. All of the potential work must be planned in full
4. Just enough for the Scrum Master to be able to assign tasks to
Developers
The Scrum Team has just begun Sprint Planning. How much of the
Sprint Backlog should be created during this event?
1. As a minimum, just enough, so the Developers can forecast
what it can do and provide enough of a plan for the start of the
Sprint. More planning can follow in the Sprint.
2. Just enough to understand the architecture
3. All of the potential work must be planned in full
4. Just enough for the Scrum Master to be able to assign tasks to
Developers
Explanation
The Sprint Backlog includes the items selected from the Product Backlog and the plan to deliver them. A
Sprint Goal and enough of a plan to start the Sprint is needed. More planning may follow during the
Sprint.
16-The Scrum Team have finished the Sprint Planning event. The
Product Owner identifies one more Product Backlog item they want
to add to the Sprint Backlog. What may happen?
1. The Developers must add that item to the Sprint Backlog
2. The Developers must defer that item to the next Sprint
3. The Developers can decide to add the item to the Sprint Backlog
if it will not endanger the Sprint Goal.
The Scrum Team have finished the Sprint Planning event. The
Product Owner identifies one more Product Backlog item they want
to add to the Sprint Backlog. What may happen?
1. The Developers must add that item to the Sprint Backlog
2. The Developers must defer that item to the next Sprint
3. The Developers can decide to add the item to the Sprint Backlog
if it will not endanger the Sprint Goal.
Explanation
The Sprint Backlog is a plan by and for the Developers. The Sprint Backlog is updated throughout the
Sprint as more is learned. The Developers manage the Sprint Backlog.
16-The Scrum Team is self-managing and therefore can decide to
drop the Daily Scrum.
1. True
2. False.
The Scrum Team is self-managing and therefore can decide to drop
the Daily Scrum.
1. True
2. False.
Explanation
The Daily Scrum event is mandatory in Scrum
18-The Scrum Team is self-managing and therefore can decide to
remove the Sprint Retrospective as and when needed.
1. True
2. False.
The Scrum Team is self-managing and therefore can decide to
remove the Sprint Retrospective as and when needed.
1. True
2. False.
Explanation
The Sprint Retrospective event is mandatory.
19-The Scrum Team realize they will not be able to complete all the
forecast Product Backlog items in the Sprint. Who needs to talk
about this.
1. The Developers and the Product Owner.
2. The Developers
3. The Product Owner
4. The Scrum Master
The Scrum Team realize they will not be able to complete all the
forecast Product Backlog items in the Sprint. Who needs to talk
about this.
1. The Developers and the Product Owner.
2. The Developers
3. The Product Owner
4. The Scrum Master
Explanation
The Developers and the Product Owner should discuss this and adjust scope as needed.
20-The Sprint Backlog makes visible all of the work the... identify as
necessary to meet the Sprint Goal
1. Scrum Team
2. Product Owner
3. Developers.
4. Scrum Master
The Sprint Backlog makes visible all of the work the... identify as
necessary to meet the Sprint Goal
1. Scrum Team
2. Product Owner
3. Developers.
4. Scrum Master
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.
21-The Sprint Backlog may change during the Sprint.
1. True.
2. False
The Sprint Backlog may change during the Sprint.
1. True.
2. False
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. It should have enough detail that they can inspect their progress in the Daily Scrum.
22-The Sprint Backlog must be baselined at the end of each Sprint
Planning event.
1. True
2. False.
The Sprint Backlog must be baselined at the end of each Sprint
Planning event.
1. True
2. False.
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.
23-The Sprint Goal is the single objective for the Sprint. The Sprint
Goal provides the following
1. Guidance to the Scrum Team on why it is building the Increment
2. Flexibility in terms of the exact work needed to achieve it
3. Coherence and focus, encouraging the Scrum Team to work
together rather than on separate initiatives
4. All the answers apply.
The Sprint Goal is the single objective for the Sprint. The Sprint
Goal provides the following
1. Guidance to the Scrum Team on why it is building the Increment
2. Flexibility in terms of the exact work needed to achieve it
3. Coherence and focus, encouraging the Scrum Team to work
together rather than on separate initiatives
4. All the answers apply.
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.
24-The Sprint Retrospective is one of the events in Scrum. Which of
the following items is not a topic of discussion within a Sprint
Retrospective?
1. Sprint Backlog for the next Sprint.
2. Team interactions
3. Process improvements
4. Definition of Done
The Sprint Retrospective is one of the events in Scrum. Which of
the following items is not a topic of discussion within a Sprint
Retrospective?
1. Sprint Backlog for the next Sprint.
2. Team interactions
3. Process improvements
4. Definition of Done
Explanation
Sprint Backlog for the next Sprint are better discussed at the Sprint Review and Sprint
Planning. The focus of the Sprint Retrospective is to plan ways to increase quality and effectiveness.
25-The Sprint Review is the only time when stakeholder feedback is
captured.
1. False.
2. True
The Sprint Review is the only time when stakeholder feedback is
captured.
1. False.
2. True
26-The Sprint Review must include a presentation of the Increment.
1. True
2. False.
The Sprint Review must include a presentation of the Increment.
1. True
2. False.
Explanation
The Sprint Review is a working session and the Scrum Team should avoid limiting it to a
presentation.
27-The time to integrate the work being carried out is ....
1. During the Sprint.
2. At the end of the Sprint
3. Before the release
4. At the end of the project
The time to integrate the work being carried out is ....
1. During the Sprint.
2. At the end of the Sprint
3. Before the release
4. At the end of the project
Explanation
Integration is part of developing the product and should be Done during each Sprint to
ensure we have an Increment no later than the end of the Sprint.
28-There are 3 Scrum Teams and they develop a single product.
Each team should have its own Definition of Done.
1. True
2. False.
There are 3 Scrum Teams and they develop a single product. Each
team should have its own Definition of Done.
1. True
2. False.
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.
29-There are 3 Scrum Teams and they develop a single product.
Who is responsible for the Definition of Done that will be used?
1. The Product Owner
2. The Scrum Master
3. The Scrum Team's.
There are 3 Scrum Teams and they develop a single product. Who is
responsible for the Definition of Done that will be used?
1. The Product Owner
2. The Scrum Master
3. The Scrum Team's.
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.
30-There are 4 Scrum Teams working on the same product. Who
should make sure that their outputs can be integrated into one
Increment?
1. The Developers in the Scrum Teams.
2. The Scrum Master(s)
3. The Product Owner
4. No one
Explanation
Integration is the responsibility of the Developers across the Scrum Teams
There are 4 Scrum Teams working on the same product. Who
should make sure that their outputs can be integrated into one
Increment?
1. The Developers in the Scrum Teams.
2. The Scrum Master(s)
3. The Product Owner
4. No one
Explanation
Integration is the responsibility of the Developers across the Scrum Teams
31-There are 5 Scrum Teams and they develop the same product.
They should ...
1. Collocate together and integrate their changes every day under
the supervision of the Scrum Master
2. Mutually define their Definition of Done.
3. Should ask the common quality guidance from the Product
Owner
4. Each Scrum Team should create its own Definition of Done of
their own and make their standards transparent to each other
There are 5 Scrum Teams and they develop the same product. They
should ...
1. Collocate together and integrate their changes every day under
the supervision of the Scrum Master
2. Mutually define their Definition of Done.
3. Should ask the common quality guidance from the Product
Owner
4. Each Scrum Team should create its own Definition of Done of
their own and make their standards transparent to each other
Explanation
If there are multiple Scrum Teams working together on a product, they must mutually define
and comply with the same Definition of Done.
32-These are accountabilities in Scrum for the Product Owner.
Select 3 answers.
1. Developing and explicitly communicating the Product Goal.
2. Creating and clearly communicating Product Backlog items.
3. Ordering Product Backlog items.
4. Product design
5. Facilitate events
6. Provide sizing
These are accountabilities in Scrum for the Product Owner. Select 3 answers.
1. Developing and explicitly communicating the Product Goal.
2. Creating and clearly communicating Product Backlog items.
3. Ordering Product Backlog items.
4. Product design
5. Facilitate events
6. Provide sizing
Explanation
The Product Owner is also 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.
33-This accountability in Scrum 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 Senior Developer
This accountability in Scrum 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 Senior Developer
Explanation
The Sprint Backlog is a plan by and for the Developers. The Sprint Backlog is updated
throughout the Sprint as more is learned.
34-This role is responsible for Gantt Charts in Scrum
1. It is not required in Scrum.
2. The project manager
3. The Developers
4. The Product Owner
5. The Scrum Master
This role is responsible for Gantt Charts in Scrum
1. It is not required in Scrum.
2. The project manager
3. The Developers
4. The Product Owner
5. The Scrum Master
Explanation
The Gannt chart is not a tool required by Scrum
35-This Scrum event supports daily inspection and adaptation
1. Sprint Retrospective
2. Daily Scrum.
3. Sprint Planning
4. Product Backlog Refinement
This Scrum event supports daily inspection and adaptation
1. Sprint Retrospective
2. Daily Scrum.
3. Sprint Planning
4. Product Backlog Refinement
Explanation
The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the
Sprint Backlog as necessary.
36-Throughout the Sprint, Developers review and potentially adapt
their plan toward the Sprint Goal at least......
1. Every day.
2. Every Sprint Retrospective
3. Whenever the Scrum Master directs them to do it
4. At a minimum every month
Throughout the Sprint, Developers review and potentially adapt
their plan toward the Sprint Goal at least......
1. Every day.
2. Every Sprint Retrospective
3. Whenever the Scrum Master directs them to do it
4. At a minimum every month
Explanation
Developers are always accountable for adapting their plan each day toward the Sprint Goal;
37-Throughout the Sprint, the Developers replan the remaining
work. At a minimum, this should happen
1. Every week
2. Every day.
3. Whenever the Scrum Master gets the time
4. Every month
Throughout the Sprint, the Developers replan the remaining work.
At a minimum, this should happen
1. Every week
2. Every day.
3. Whenever the Scrum Master gets the time
4. Every month
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 focuses on progress toward the Sprint Goal and produces an actionable plan
for the next day of work
38-Time can be allocated between Sprints for integration.
1. True
2. False.
Time can be allocated between Sprints for integration.
1. True
2. False.
Explanation
Integration is part of the Definition of Done and should happen as part of the development
during the Sprint. Each new Sprint starts immediately after the previous one. There is no time
between Sprints to do this.
39-Transitioning from Waterfall to Scrum is a significant step for
many organizations. How may the organization judge the success of
Scrum? Select 2 answers.
1. By reducing costs
2. By increasing customer satisfaction.
3. Through frequent releases that deliver value.
4. By releasing new features after each Sprint
Transitioning from Waterfall to Scrum is a significant step for many
organizations. How may the organization judge the success of
Scrum? Select 2 answers.
1. By reducing costs
2. By increasing customer satisfaction.
3. Through frequent releases that deliver value.
4. By releasing new features after each Sprint
Explanation
Producing Increments and delivering value is a good way to measure the success of Scrum
40-We are ready to start the first Sprint, but work on the Product
Backlog is not completed yet. What should the Scrum Team do?
1. Refine the Product Backlog instead of starting the first Sprint
2. Let the Sprint begin, but only with the goal of completing the
Product Backlog. No Increment will be produced in this Sprint.
3. Start the first Sprint, and continue refining the Product Backlog.
We are ready to start the first Sprint, but work on the Product
Backlog is not completed yet. What should the Scrum Team do?
1. Refine the Product Backlog instead of starting the first Sprint
2. Let the Sprint begin, but only with the goal of completing the
Product Backlog. No Increment will be produced in this Sprint.
3. Start the first Sprint, and continue refining the Product Backlog.
Explanation
The Scrum Team should start Sprint and continue refining the Product Backlog. Beware of analysis
paralysis and waiting for perfect and complete information. It may never arrive.
41-What are the three accountabilities in a Scrum Team?
1. Project Owner, Developers, Scrum Master
2. Product Owner, Scrum Master, Developers.
3. Scrum Manager, project manager, Tester
4. Tester, Scrum Master, Product Owner
5. Architect, Designer, Developers
What are the three accountabilities in a Scrum Team?
1. Project Owner, Developers, Scrum Master
2. Product Owner, Scrum Master, Developers.
3. Scrum Manager, project manager, Tester
4. Tester, Scrum Master, Product Owner
5. Architect, Designer, Developers
Explanation
The Scrum Team consists of a Product Owner, Scrum Master and Developers
42-What artifact lists all the known features, functions,
requirements, enhancements, and fixes that constitute the changes
to be made to the product
1. The Sprint Backlog
2. The Sprint Goal
3. The Product Backlog.
4. Increment
What artifact lists all the known features, functions, requirements,
enhancements, and fixes that constitute the changes to be made to
the product
1. The Sprint Backlog
2. The Sprint Goal
3. The Product Backlog.
4. Increment
Explanation
The Product Backlog is an emergent, ordered list of what is needed to improve the product. It
is the single source of work undertaken by the Scrum Team.
43-What does a Scrum Team consist of? Select all that apply.
1. A Scrum Manager
2. A Scrum Master
3. A Product Owner
4. Developers
5. A project manager
What does a Scrum Team consist of? Select all that apply.
1. A Scrum Manager
2. A Scrum Master
3. A Product Owner
4. Developers
5. A project manager
Explanation
The Scrum Team consists of a Product Owner, Developers, and a Scrum Master.
44-What does letter S mean in MOSCOW technique?
1. Should not have
2. Should Have
3. Should be improved
4. O Sprint
What does letter S mean in MOSCOW technique?
1. Should not have
2. Should Have
3. Should be improved
4. O Sprint
Explanation
In MOSCOW, S stands for should have.
MOSCOW method:
Must have
Should have
Could have
Won't have (this time)
45-What does the "cone of uncertainty" describe?
1. Uncertainty is always equally high
2. Uncertainty is always lowered after the requirements are signed
off at the beginning of the project
3. How much is known about the product over time.
4. Dependencies, start times and stop times for project tasks
What does the "cone of uncertainty" describe?
1. Uncertainty is always equally high
2. Uncertainty is always lowered after the requirements are signed
off at the beginning of the project
3. How much is known about the product over time.
4. Dependencies, start times and stop times for project tasks
Explanation
The "cone of uncertainty" shows that uncertainty is highest at the beginning of developing a product,
and reduces as we progress and more work is Done. This uncertainty can take many dimensions including
duration, work, risks, etc.
46-What does the Sprint burn-down chart show?
1. The evolution of the amount of uncertainty during a project
2. How much work remains until the end of the Sprint.
3. Dependencies, start times and stop times for project tasks
4. An overview of the release progress by plotting the remaining
workload
What does the Sprint burn-down chart show?
1. The evolution of the amount of uncertainty during a project
2. How much work remains until the end of the Sprint.
3. Dependencies, start times and stop times for project tasks
4. An overview of the release progress by plotting the remaining
workload
Explanation
A chart which shows the amount of work which is thought to remain in a backlog. Time is
shown on the horizontal axis and work remaining on the vertical axis. As time progresses and
items are drawn from the backlog and completed, a plot line showing work remaining may be
expected to fall. The amount of work may be assessed in any of several ways such as user story
points or task hours. Work remaining in Sprint Backlogs and Product Backlogs may be
communicated by means of a burn-down chart.
47-What happens to Product Backlog items in the Sprint Backlog
that are not Done by the end of the Sprint?
1. They will not be inspected as part of the Increment at the Sprint
Review.
2. They will be completed in the next Sprint
3. They will be moved back to the Product Backlog. ch
4. They will be demonstrated to the stakeholders in the Sprint
Review but pointed out that it's not complete
5. The Sprint will be extended until the item is Done
What happens to Product Backlog items in the Sprint Backlog that are
not Done by the end of the Sprint?
1. They will not be inspected as part of the Increment at the Sprint
Review.
2. They will be completed in the next Sprint
3. They will be moved back to the Product Backlog. ch
4. They will be demonstrated to the stakeholders in the Sprint
Review but pointed out that it's not complete
5. The Sprint will be extended 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.
48-What is the benefit of using value points in the Product Backlog?
1. There is no additional benefit as value points are required by
Scrum
2. Using value points makes the ordering clear items
3. Assigning value points may increase transparency around the
value of Product Backlog.
What is the benefit of using value points in the Product Backlog?
1. There is no additional benefit as value points are required by
Scrum
2. Using value points makes the ordering clear items
3. Assigning value points may increase transparency around the
value of Product Backlog.
Explanation
Assigning value points is a complimentary practice to Scrum. Value points are relative units for the value
assigned to the Product Backlog items. They may increase transparency around the value of Product
Backlog items.
49-What is the best description of a Sprint Backlog?
1. The Sprint Backlog is the sum of all the Product Backlog items
completed during the Sprint
2. The Sprint Backlog is an ordered list of everything that must be
built in the current Sprint
3. The Sprint Backlog is the Product Backlog items that the
Developers are committed to delivering in the current Sprint
4. 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).
What is the best description of a Sprint Backlog?
1. The Sprint Backlog is the sum of all the Product Backlog items
completed during the Sprint
2. The Sprint Backlog is an ordered list of everything that must be
built in the current Sprint
3. The Sprint Backlog is the Product Backlog items that the
Developers are committed to delivering in the current Sprint
4. 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).
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).
50-What is the desirable common outcome of Daily Scrum?
1. The Scrum Master identifies new impediments (if he/she
presents at the event)
2. The Developers are clear on the next steps towards the Sprint
Goal.
3. Stakeholders are kept informed of the progress made
4. The Product Owner is informed of the progress
What is the desirable common outcome of Daily Scrum?
1. The Scrum Master identifies new impediments (if he/she
presents at the event)
2. The Developers are clear on the next steps towards the Sprint
Goal.
3. Stakeholders are kept informed of the progress made
4. The Product Owner is informed of the progress
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.
51-What is the fundamental organizational unit of Scrum?
1. The Scrum Master and the Product Owner
2. The Scrum Guide
3. The Scrum Team.
4. The Developers
What is the fundamental organizational unit of Scrum?
1. The Scrum Master and the Product Owner
2. The Scrum Guide
3. The Scrum Team.
4. The Developers
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.
52-What is the main reason that a Daily Scrum is held at the same
time and same place?
1. It makes it easier to book the rooms
2. Because the Scrum Master requires it
3. Because the Product Owner requires it
4. To reduce complexity.
What is the main reason that a Daily Scrum is held at the same time
and same place?
1. It makes it easier to book the rooms
2. Because the Scrum Master requires it
3. Because the Product Owner requires it
4. To reduce complexity.
Explanation
The Daily Scrum is held at the same time and place each day to reduce complexity.
53-What is the main responsibility of the tester role in Scrum?
1. Maintain user acceptance tests
2. Verify the programmers' output
3. Help the Scrum Team incorporate the test-driven development
practice
4. There is no tester role in Scrum.
5. Find and remove bugs
What is the main responsibility of the tester role in Scrum?
1. Maintain user acceptance tests
2. Verify the programmers' output
3. Help the Scrum Team incorporate the test-driven development
practice
4. There is no tester role in Scrum.
5. Find and remove bugs
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.
54-What is the maximum duration of the Sprint Review?
1. 8 hours
2. 4 hours
3. 6 hours
4. 3 hours
What is the maximum duration of the Sprint Review?
1. 8 hours
2. 4 hours
3. 6 hours
4. 3 hours
Explanation
A Sprint Review is at most a four-hour meeting for one-month Sprints. For shorter Sprints,
the event is usually shorter.
55-What is the most optimal length of a Sprint?
1. Two weeks
2. One week
3. One month
4. Short enough to minimize risk.
What is the most optimal length of a Sprint?
1. Two weeks
2. One week
3. One month
4. Short enough to minimize risk.
Explanation
Sprints enable predictability by ensuring inspection and adaptation of progress toward a
Product Goal at least every calendar month. When a Sprint's horizon is too long the Sprint
Goal may become invalid, complexity may rise, and risk may increase. Shorter Sprints can be
employed to generate more learning cycles and limit risk of cost and effort to a smaller time
frame. Each Sprint may be considered a short project.
56-What is the number of Product Owners where there is one
product being built by 4 Scrum Teams?
1. The Scrum Teams should decide
2. It depends on the size and complexity of the product
3. One.
4. Six
What is the number of Product Owners where there is one product
being built by 4 Scrum Teams?
1. The Scrum Teams should decide
2. It depends on the size and complexity of the product
3. One.
4. Six
Explanation
One product has only one Product Backlog and one Product Owner.
57-What is the reason why there should be only one Product
Owner per product?
1. There should be one Product Owner for each Scrum Team. If more than
one teams are working on the same product, multiple Product Owners will
be needed.
2. So we have one clear, named person accountable for maximizing the value
of the product resulting from the work of the Scrum Team and for effective
Product Backlog management.
3. One person is always enough to complete all the work regardless of the
size of the product
4. It becomes confusing when more than one Product Owners are managing
the Scrum Team.
What is the reason why there should be only one Product Owner per product?
1. There should be one Product Owner for each Scrum Team. If more than one teams are
working on the same product, multiple Product Owners will be needed.
2. So we have one clear, named person accountable for maximizing the value of the product
resulting from the work of the Scrum Team and for effective Product Backlog
management.
3. One person is always enough to complete all the work regardless of the size of the
product
4. It becomes confusing when more than one Product Owners are managing the Scrum
Team.
Explanation
The Product Owner is one person, not a committee. They are accountable for maximizing the value of
the product resulting from the work of the Scrum Team and for effective Product Backlog management. If
Scrum Teams become too large, they should consider reorganizing into multiple cohesive Scrum Teams,
each focused on the same product. Therefore, they should share the same Product Goal, Product
Backlog, and Product Owner.
58-What is the responsibility of the team leader in Scrum?
1. There's no team leader in Scrum.
2. Preparing the project plan and Gantt Charts
3. Managing the Sprints
4. Making high-level decisions
5. Planning releases
What is the responsibility of the team leader in Scrum?
1. There's no team leader in Scrum.
2. Preparing the project plan and Gantt Charts
3. Managing the Sprints
4. Making high-level decisions
5. Planning releases
Explanation
There is no team leader role in Scrum
59-What is the purpose of the Scrum Master at the Daily Scrum?
1. The Scrum Master must provide daily reports to the Product
Owner
2. The Scrum Master must ensure the Developers answer the
three required questions
3. The Scrum Master has to ensure the Daily Scrum occurs.
What is the purpose of the Scrum Master at the Daily Scrum?
1. The Scrum Master must provide daily reports to the Product
Owner
2. The Scrum Master must ensure the Developers answer the
three required questions
3. The Scrum Master has to ensure the Daily Scrum occurs.
Explanation
Scrum Master does not necessarily have to be there; but they have to ensure a Daily Scrum occurs and is
effective
60-What is velocity?
1. Average man-hours spent per Sprint
2. Amount of work taken into the Sprint
3. Average lines of code created per Sprint
4. The amount of Product Backlog turned into an Increment
during a Sprint.
What is velocity?
1. Average man-hours spent per Sprint
2. Amount of work taken into the Sprint
3. Average lines of code created per Sprint
4. The amount of Product Backlog turned into an Increment
during a Sprint.
Explanation
Velocity is an optional, but often used, indication of the amount of Product Backlog turned
into an Increment of product during a Sprint by a Scrum Team
61-What measures may help the Product Owner to determine the
product's value? Select all that apply.
1. The productivity of the Scrum Team
2. Total cost of the product throughout its life.
3. On-time completion of the design
4. Customer satisfaction.
5. The productivity of the Developers
6. The ease of absorption of new releases for the customer.
What measures may help the Product Owner to determine the
product's value? Select all that apply.
1. The productivity of the Scrum Team
2. Total cost of the product throughout its life.
3. On-time completion of the design
4. Customer satisfaction.
5. The productivity of the Developers
6. The ease of absorption of new releases for the customer.
Explanation
Productivity and predictability, although often desirable are not an indicator of value. Total cost, happy
customers and easy adoption of new features may indicate value.
62-What must be Done in the first Sprint?
1. Planning the project
2. Creating an Increment.
3. Developing the product vision
4. Completing the reference architecture
5. Complete the Product Backlog
What must be Done in the first Sprint?
1. Planning the project
2. Creating an Increment.
3. Developing the product vision
4. Completing the reference architecture
5. Complete the Product Backlog
Explanation
There's no difference between the first Sprint and subsequent Sprints. Creating an
Increment
is always necessary.
63-Which of the following is not an accountability in
Scrum?
1. Scrum Master
2. Product Owner
3. Developers
4. Product Manager.
Which of the following is not an accountability in
Scrum?
1. Scrum Master
2. Product Owner
3. Developers
4. Product Manager.
Explanation
There is no Product Manager accountability in Scrum
64-What Scrum event supports daily inspection
and adaptation?
1. Sprint Planning
2. Daily Scrum.
3. Sprint Review
4. Sprint Retrospective
What Scrum event supports daily inspection and
adaptation?
1. Sprint Planning
2. Daily Scrum.
3. Sprint Review
4. Sprint Retrospective
Explanation
There is only one daily activity event in Scrum: The Daily Scrum
65-What should the Product Owner do during Sprint zero?
1. There is no Sprint zero in Scrum.
2. Prepare the Product Backlog for the whole project
3. Communicate with the customer and understand the
requirements
4. Prepare the Product Backlog for the next few Sprints
What should the Product Owner do during Sprint zero?
1. There is no Sprint zero in Scrum.
2. Prepare the Product Backlog for the whole project
3. Communicate with the customer and understand the
requirements
4. Prepare the Product Backlog for the next few Sprints
Explanation
There's no Sprint Zero in Scrum. All Sprints are the same as other Sprint with the aim of
creating an Increment and meeting a Sprint Goal.
66-What should the Product Owner use to identify unfinished work
at the end of the Sprint?
1. Coding Standards
2. Definition of ready
3. Testing standard
4. Definition of Done.
What should the Product Owner use to identify unfinished
work at the end of the Sprint?
1. Coding Standards
2. Definition of ready
3. Testing standard
4. Definition of Done.
Explanation
Definition of Done is used by entire Scrum Team to identify unfinished work
67-What work is typical for a Product Owner between the end of
Sprint Planning and before the Sprint Review
1. Prepare statistical reports
2. Measure the Sprint performance
3. Assign tasks to testers
4. Refine the Product Backlog with the Developers.
What work is typical for a Product Owner between the end
of Sprint Planning and before the Sprint Review
1. Prepare statistical reports
2. Measure the Sprint performance
3. Assign tasks to testers
4. Refine the Product Backlog with the Developers.
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.
68-When do the Developers prepare the tools and
infrastructure for development?
1. Someone else must do this
2. In Sprint Zero
3. Before the first Sprint and/or in Sprints.
When do the Developers prepare the tools and infrastructure
for development?
1. Someone else must do this
2. In Sprint Zero
3. Before the first Sprint and/or in Sprints.
Explanation
This is work that needs to be Done. Some may happen before we start with Scrum. It may also
happen as part of developing the Product with Scrum in Sprints.
69-When is the Scrum Team allowed to interact with the
stakeholders?
1. The Sprint Retrospective
2. The Sprint Review
3. Anytime where it will help the Scrum Team deliver value.
4. The Daily Scrum

.
When is the Scrum Team allowed to interact with the
stakeholders?
1. The Sprint Retrospective
2. The Sprint Review
3. Anytime where it will help the Scrum Team deliver value.
4. The Daily Scrum
Explanation
The Scrum Team may interact with the stakeholders anytime when it is appropriate and
helpful.
70-When is work in the Sprint Backlog considered to be Done?
1. When all of its tasks are complete
2. When it meets the Definition of Done.
3. When the user acceptance tests have passed
4. When the Sprint is over
When is work in the Sprint Backlog considered to be Done?
1. When all of its tasks are complete
2. When it meets the Definition of Done.
3. When the user acceptance tests have passed
4. When the Sprint is over
Explanation
Work cannot be considered part of an Increment unless it meets the Definition of Done.
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.
71-When may adaptation occur in Scrum?
1. During Sprint Planning, the Daily Scrum, the Sprint Review and
the Sprint Retrospectives.
2. Only at the Sprint Review
3. Only during the Daily Scrum
4. During Sprint Planning
When may adaptation occur in Scrum?
1. During Sprint Planning, the Daily Scrum, the Sprint Review and
the Sprint Retrospectives.
2. Only at the Sprint Review
3. Only during the Daily Scrum
4. During Sprint Planning
Explanation
Adaptation may occur during any event and at any point in a Sprint.
72-When should the Product Backlog be refined?
1. In Sprint zero
2. During each Sprint.
3. Only in the time between Sprints
When should the Product Backlog be refined?
1. In Sprint zero
2. During each Sprint.
3. Only in the time between Sprints
Explanation
During the Sprint the Product Backlog is refined as needed
73-Which are good ways for a Scrum Team to ensure security
concerns are managed? Select 2 answers.
1. Postpone the work until a specialist can perform a security audit
and create a list of security-related Product Backlog items
2. Add security concerns to the Definition of Done.
3. Add a Sprint to specifically resolve all security concerns
4. Have the Scrum Team create Product Backlog items to capture
each concern.
Which are good ways for a Scrum Team to ensure security concerns
are managed? Select 2 answers.
1. Postpone the work until a specialist can perform a security audit
and create a list of security-related Product Backlog items
2. Add security concerns to the Definition of Done.
3. Add a Sprint to specifically resolve all security concerns
4. Have the Scrum Team create Product Backlog items to capture
each concern.
Explanation
If security is important then it needs to be managed by the Scrum Team and the work and risks made
transparent.
74-Which are the outcomes of the Daily Scrum?
1. Stakeholders get a report
2. Developers are clear on next steps towards the Sprint
Goal.
3. The impediments are discussed and possible solutions
planned
4. The Product Owner is informed of progress
Which are the outcomes of the Daily Scrum?
1. Stakeholders get a report
2. Developers are clear on next steps towards the Sprint
Goal.
3. The impediments are discussed and possible solutions
planned
4. The Product Owner is informed of progress
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.
75-Which event is the most appropriate to adapt the
Definition of Done?
1. Sprint Retrospective.
2. Sprint Review
3. Daily Scrum
4. O Sprint Planning
Which event is the most appropriate to adapt the Definition
of Done?
1. Sprint Retrospective.
2. Sprint Review
3. Daily Scrum
4. O Sprint Planning
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
76-Which event results a plan for improvements which must be
enacted during the next Sprint?
1. Sprint Planning
2. Sprint Retrospective
3. Daily Scrum
4. Sprint Review
5. None of these events.
Which event results a plan for improvements which must be
enacted during the next Sprint?
1. Sprint Planning
2. Sprint Retrospective
3. Daily Scrum
4. Sprint Review
5. None of these events.
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. Scrum stops short of insisting the improvements are implemented in the NEXT
Sprint.
77-Which of the following answers may be considered as a valid
Increment?
1. A diagram that describes the features that will be built in future
Sprints
2. A decomposition of Product Backlog items into tasks that will
be used in future Sprints
3. A user interface design
4. The sum of all the Product Backlog items Done during the
Sprint and the value of the Increments of all previous Sprints.
Which of the following answers may be considered as a valid Increment?
1. A diagram that describes the features that will be built in future Sprints
2. A decomposition of Product Backlog items into tasks that will be used in
future Sprints
3. A user interface design
4. The sum of all the Product Backlog items Done during the Sprint and the
value of the Increments of all previous Sprints.
Explanation
An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all
prior Increments and thoroughly verified, ensuring that all Increments work together. In order to
provide value, the Increment must be usable.
78-Which of the following are a mandatory input for Sprint
Planning?
1. Having the items at the top of the Product Backlog refined to
be small enough to be Done in one Sprint
2. A completed Product Backlog
3. Having the Product Backlog items pre-assigned to Developers
4. None of these are mandated inputs to Sprint Planning.
Which of the following are a mandatory input for Sprint Planning?
1. Having the items at the top of the Product Backlog refined to be small
enough to be Done in one Sprint
2. A completed Product Backlog
3. Having the Product Backlog items pre-assigned to Developers
4. None of these are mandated inputs to Sprint Planning.
Explanation
Having the items at the top of the Product Backlog refined to be small enough to be Done in
one Sprint is desirable and a good practice but this can potentially be completed as late as the Sprint
Planning event itself.
79-Which of the following are artifacts in Scrum? Select all that
apply.
1. Sprint Backlog
2. Increment
3. Product Backlog
4. Impediments
5. The Scrum Goal
Which of the following are artifacts in Scrum? Select all
that apply.
1. Sprint Backlog
2. Increment
3. Product Backlog
4. Impediments
5. The Scrum Goal
Explanation
Scrum artifacts are the Product Backlog, Sprint Backlog and Increment.
80-Which of the following are correct about Scrum? Select all that
apply.
1. Scrum is a methodology for managing complex projects
2. Scrum is a traditional process but with Sprints and related
artifacts
3. Scrum is a lightweight framework that helps people, teams and
organizations generate value through adaptive solutions for
complex problems.
4. Scrum is based on empirical process control theory.
Which of the following are correct about Scrum? Select all that apply.
1. Scrum is a methodology for managing complex projects
2. Scrum is a traditional process but with Sprints and related artifacts
3. Scrum is a lightweight framework that helps people, teams and
organizations generate value through adaptive solutions for
complex problems.
4. Scrum is based on empirical process control theory.
Explanation
Scrum is a lightweight framework that helps people, teams and organizations generate value through
adaptive solutions for complex problems. Scrum is founded on empiricism and lean thinking. Empiricism
asserts that knowledge comes from experience and making decisions based on what is observed. Lean
thinking reduces waste and focuses on the essentials.
81-Which of the following are not mandatory in Scrum?
Select 2 answers.
1. Increments
2. Velocity.
3. Release plan.
4. Product Backlog
Which of the following are not mandatory in Scrum?
Select 2 answers.
1. Increments
2. Velocity.
3. Release plan.
4. Product Backlog
Explanation
The Increment and Product Backlog are mandatory Scrum artifacts. Velocity and Release
plans are optional complimentary practices.
82-Which of the following are not permitted in Scrum?
1. Refactoring
2. Velocity tracking
3. Hardening Sprints.
4. Release planning
Which of the following are not permitted in Scrum?
1. Refactoring
2. Velocity tracking
3. Hardening Sprints.
4. Release planning
Explanation
All Sprints result in a Done Increment. There are no special Sprints where this occurs (and
therefore does not occur in other Sprints). Scrum requires the addition of many other practices in
order to enable a Scrum Team to deliver value.
83-Which of the following are optional in Scrum? Select 2 answers.
1. Burn-down charts
2. Definition of Done
3. Velocity
4. Increment
5. Sprint Backlog
6. Product Backlog
Which of the following are optional in Scrum? Select 2 answers.
1. Burn-down charts
2. Definition of Done
3. Velocity
4. Increment
5. Sprint Backlog
6. Product Backlog
Explanation
Burn-down charts and measuring Velocity are not mandatory in Scrum
84-Which of the following are true about the Sprint
Retrospective
1. The Sprint Retrospective occurs before the Sprint Review
2. Only Developers participate in the Sprint Retrospective
3. The Sprint Retrospective is to plan ways to increase quality
and effectiveness.
4. By the end of the Sprint Retrospective, the Scrum Team
should have identified improvements that it must implement
from the next Sprint.
Which of the following are true about the Sprint Retrospective
1. The Sprint Retrospective occurs before the Sprint Review
2. Only Developers participate in the Sprint Retrospective
3. The Sprint Retrospective is to plan ways to increase quality
and effectiveness.
4. By the end of the Sprint Retrospective, the Scrum Team
should have identified improvements that it must implement
from the next Sprint.
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.
85-Which of the following does not have to happen in the first
Sprint?
Select 2 answers.
1. Creating a Done Increment.
2. Designing the full solution
3. Creating a complete Product Backlog
Which of the following does not have to happen in the first Sprint?
Select 2 answers.
1. Creating a Done Increment.
2. Designing the full solution
3. Creating a complete Product Backlog
Explanation
Every Sprint is intended to produce an Increment. There may never be a time where we have
a complete Product Backlog or a fully designed solution.
86-Which of the following events has the shortest timebox?
1. Sprint Review
2. O Sprint Planning
3. Sprint Retrospective.
Which of the following events has the shortest timebox?
1. Sprint Review
2. O Sprint Planning
3. Sprint Retrospective.
Explanation
The Sprint Retrospective is timeboxed to a maximum of three hours for a one-month Sprint.
For shorter Sprints, the event is usually shorter.
87-Which of the following factors will help the Scrum Team to
balance creativity, efficiency, flexibility and productivity? Select 2
answers.
1. Strong team management and guidance by a Scrum Team leader
2. Having all the skills required to perform their work without
external help.
3. Empowering the Scrum Team so that it can self-manage its work
against towards a Product Goal. ch
4. A performance management system that rewards the high
achievers in the team
Which of the following factors will help the Scrum Team to balance
creativity, efficiency, flexibility and productivity? Select 2 answers.
1. Strong team management and guidance by a Scrum Team leader
2. Having all the skills required to perform their work without
external help.
3. Empowering the Scrum Team so that it can self-manage its work
against towards a Product Goal.
4. A performance management system that rewards the high
achievers in the team
Explanation
Scrum Teams are self-managing
88-Which of the following are the attributes of a good user
story?
1. Renewable, Supportable, Valuable
2. Independent, Negotiable, Valuable, Estimable, Small and
Testable.
3. Large, Dependant, Simple
Which of the following are the attributes of a good user
story?
1. Renewable, Supportable, Valuable
2. Independent, Negotiable, Valuable, Estimable, Small and
Testable.
3. Large, Dependant, Simple
Explanation
The INVEST acronym details the characteristics of a good user story. It should be: -
Independent, Negotiable, Valuable, Estimable, Small and Testable.
89-Which of the following is a responsibility of team leaders when
multiple teams are working on the same product?
1. Help the Product Owner with release planning
2. There are no team leaders in Scrum.
3. Acting as an intermediary between the Product Owner and the
Developers
4. Making work assignments
Which of the following is a responsibility of team leaders when multiple
teams are working on the same product?
1. Help the Product Owner with release planning
2. There are no team leaders in Scrum.
3. Acting as an intermediary between the Product Owner and the
Developers
4. Making work assignments
Explanation
There are three accountabilities in Scrum - the Product Owner, the Scrum Master, the Developers
90-Which of the following is a valid service from the Scrum
Master to the Product Owner? Select 2 answers.
1. Helping the Product Owner find techniques for managing the
Product Backlog value
2. Ensuring the Product Owner knows how to arrange the
Product Backlog to maximize.
3. Act as the middleman between the Product Owner and the
Developers, as requested or required
4. Act as a proxy when the Product Owner is not available to
the team.
Which of the following is a valid service from the Scrum Master
to the Product Owner? Select 2 answers.
1. Helping the Product Owner find techniques for managing
the Product Backlog value
2. Ensuring the Product Owner knows how to arrange the
Product Backlog to maximize
3. Act as the middleman between the Product Owner and the
Developers, as requested or required
4. Act as a proxy when the Product Owner is not available to
the team.
Explanation
The Scrum Master serves the Product Owner and may help them find effective ways to fulfil their
accountability
91-Which of the following is a way of limiting the
accumulation of technical debt?
1. Hiring an external auditor
2. Improving the Definition of Done.
3. Having hardening Sprints
4. Increasing velocity
Which of the following is a way of limiting the accumulation
of technical debt?
1. Hiring an external auditor
2. Improving the Definition of Done.
3. Having hardening Sprints
4. Increasing velocity
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.
Developers are always accountable for instilling quality by adhering to a Definition of Done.
92-Which of the following is commonly discussed in a Sprint
Retrospective?
1. The Product Backlog items to select for the next Sprint
2. Sizing of Product Backlog items
3. The Definition of Done.
Which of the following is commonly discussed in a Sprint
Retrospective?
1. The Product Backlog items to select for the next Sprint
2. Sizing of Product Backlog items
3. The Definition of Done.
Explanation
Sprint Retrospective is used for planning for improvements. One of them is improving the
Definition of Done.
93-Which of the following is correct about the Sprint Backlog?
1. The Product Owner creates it
2. It is the Developers plan for the Sprint.
3. Each of its items must be estimated in hours
Which of the following is correct about the Sprint Backlog?
1. The Product Owner creates it
2. It is the Developers plan for the Sprint.
3. Each of its items must be estimated in hours
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. It should
have enough detail that they can inspect their progress in the Daily Scrum.
94-Which of the following is NOT a common attribute of a
Product Backlog item?
1. Owner,
2. Order
3. Description
4. Size
Which of the following is NOT a common attribute of a
Product Backlog item?
1. Owner,
2. Order
3. Description
4. Size
Explanation
Product Backlog refinement is an ongoing activity to add details, such as a description,
order,
and size. Attributes often vary with the domain of work.
95-Which of the following is not a pillar of Empiricism?
1. Adaptation
2. Inspection
3. Transparency
4. O Complexity.
Which of the following is not a pillar of Empiricism?
1. Adaptation
2. Inspection
3. Transparency
4. O Complexity.
Explanation
Three pillars of empirical process control are transparency, inspection, and adaptation.
96-Which of the following is not a Scrum event?
1. Daily Scrum
2. Sprint Retrospective
3. Sprint Review
4. Weekly Status Review
Which of the following is not a Scrum event?
1. Daily Scrum
2. Sprint Retrospective
3. Sprint Review
4. Weekly Status Review
Explanation
Weekly Status Review is not Scrum event
97-Which of the following is not an accountability in Scrum?
Select 2 answers.
1. Product manager
2. Scrum Master
3. Product Owner
4. Developers
5. Team Leader
.
Which of the following is not an accountability in Scrum?
Select 2 answers.
1. Product manager
2. Scrum Master
3. Product Owner
4. Developers
5. Team Leader
Explanation
There are 3 accountabilities inside a Scrum Team: Scrum Master, Product Owner, and
Developers.
98-Which of the following is not an input to the Sprint
Planning event?
1. The Product Backlog
2. Sprint Goal.
3. Previous Increment
Which of the following is not an input to the Sprint Planning
event?
1. The Product Backlog
2. Sprint Goal.
3. Previous Increment
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 they are building the
Increment. It is created during Sprint Planning
99-Which of the following is the single objective for the
Sprint?
1. The Sprint Backlog
2. The Increment
3. The Product Backlog
4. The Sprint Goal.
Which of the following is the single objective for the Sprint?
1. The Sprint Backlog
2. The Increment
3. The Product Backlog
4. The Sprint Goal.
Explanation
The Sprint Goal is the single objective for the Sprint.
100-Which of the following is the single source of work
undertaken by the Scrum Team?
1. The Increment
2. The Sprint Retrospective
3. The Product Backlog.
4. The Sprint Backlog.
5. The product vision
Which of the following is the single source of work undertaken by
the Scrum Team?
1. The Increment
2. The Sprint Retrospective
3. The Product Backlog.
4. The Sprint Backlog.
5. The product vision
Explanation
The Product Backlog is an emergent, ordered list of what is needed to improve the product. It
is the single source of work undertaken by the Scrum Team.
 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/