Psm-I 9
Psm-I 9
Get the Full PSM-I dumps in VCE and PDF From SurePassExam
https://www.surepassexam.com/PSM-I-exam-dumps.html (197 New Questions)
Scrum
Exam Questions PSM-I
Professional Scrum Master I
NEW QUESTION 1
What may be included in the Sprint Backlog? (choose the best answer)
A. User Stones
B. Tasks
C. Use Cases
D. Tests
E. Any of the above (or others) which ate a decomposition of the selected Product Backlog items
Answer: E
Explanation:
According to the Scrum Guide, the Sprint Backlog may include any items that are a decomposition of the selected Product Backlog items, such as user stories,
tasks, use cases, tests, or others. The Sprint Backlog is the Developers’ plan for the Sprint, and it contains all the work that they forecast they can do to achieve
the Sprint Goal and create a “Done” Increment. The other options are not valid, as they are either too specific (such as user stories or tasks) or too vague (such as
tests).
NEW QUESTION 2
What is the function or purpose of management in Scrum? (choose the best answer)
A. To identify and remove people that are not working hard enough.
B. To monitor the productivity of the Developers.
C. To present the Scrum Teams with insights and resources that help them improve.
D. To continually monitor staffing levels of the Scrum Team.
Answer: C
Explanation:
The best answer is C. The function or purpose of management in Scrum is to present the Scrum Teams with insights and resources that help them improve.
According to the article What is the Function or Purpose of Management in Scrum?, management is still critical to providing vision, securing resources, hiring
talent, training teams, removing roadblocks, and continuously improving. Management also encourages collaboration and establishes Scrum Team autonomy,
which are essential for Scrum’s values and principles.
A, B and D are not good answers because they imply a command-and-control approach that contradicts Scrum’s values of respect, openness, and self-
organization. Management in Scrum is not supposed to micromanage, judge, or interfere with the work of the Developers, but rather support them and enable
them to deliver value.
NEW QUESTION 3
When should a Sprint Goal be created?
A. It should have been created in the previous Sprint during Product Backlog refinement.
B. It must be established before Sprint Planning in order to begin planning.
C. A Sprint Goal is not mandatory in Scrum.
D. At any time during the Sprint.
E. During Sprint Planning.
Answer: E
Explanation:
According to the Scrum Guide1, one aspect of Scrum Teams inspecting how they work toward their Product Goal is that they create a Sprint Goal every Sprint.
The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Developers on why it
is building the Increment. It also provides a basis for inspecting and adapting during the Sprint Review and Sprint Retrospective. The Sprint Goal is created during
the Sprint Planning event.
References: Scrum Guide
NEW QUESTION 4
You have just been hired by a company new to Scrum. Your management has assigned you to be the Scrum Master of six new Scrum Teams. These teams will
build one product. Select two conditions you should strive for in this scenario. (Choose two.)
A. There should be six Product Owners, one for each Scrum Team.
B. There should be six Product Owners, reporting to a chief Product Owner.
C. The product has one Product Backlog.
D. Each Scrum Team should have a separate Product Backlog.
E. There should be only one Product Owner.
Answer: CE
Explanation:
The product has one Product Backlog, as it is a single source of requirements for any changes to be made to the product. There should be only one Product
Owner, who is accountable for maximizing the value of the product and the work of the Development Team. Having multiple Product Owners or Product Backlogs
would create confusion, inconsistency, and waste.
NEW QUESTION 5
A Scrum Master is keeping a list of open impediments, but it is growing and they have been able to resolve only a small portion of the impediments. Which two
techniques would be most helpful in this situation? (Choose two.)
Answer: AB
Explanation:
Two techniques that would be most helpful in this situation are to discuss the impediments with the Development Team, and to prioritize the list and work on them
in order, as stated in [3]: “The Scrum Master should facilitate a discussion with the Development Team to identify and prioritize the impediments that are blocking
their progress. The Scrum Master should then work with the Development Team and other stakeholders to remove or mitigate these impediments as soon as
possible.”
NEW QUESTION 6
Which of the following is required by Scrum? (Choose all that apply.)
A. Sprint Retrospective.
B. Members must be stand up at the Daily Scrum.
C. Sprint Burndown Chart.
D. Release planning.
E. All of the above.
Answer: AD
Explanation:
explanation of Correct Answer: According to the Scrum Guide1, the only required events in Scrum are Sprint Planning, Daily Scrum, Sprint Review, and Sprint
Retrospective. These events enable transparency, inspection, and adaptation. The other options are not mandatory in Scrum, although they may be useful in some
contexts.
References: Scrum Guide
NEW QUESTION 7
The Product Owner must release each Increment to production.
Answer: A
Explanation:
According to the Scrum Guide1, 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. Multiple Increments may be created within
a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders prior
to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value.
References: Scrum Guide
NEW QUESTION 8
Which three behaviors demonstrate that a team is self-organizing? (Choose three.)
A. Stakeholders walking in at the Daily Scrum to check progress and work with the Scrum Master to optimize the functional scope for the Sprint.
B. The Development Team members are working within the boundaries of their functional description and nicely handing off work from analyst to developer to
tester to integration.
C. The Product Owner doesn’t need to be at Sprint Retrospectives.
D. The Development Team creating their own sprint backlog, reflecting all work that is part of the definition of “Done”.
E. The Development Team has all the skills needed to create a releasable Increment.
F. Development Team members collaboratively selecting their own work during the Sprint.
G. The Development Team inviting external people to the Sprint Planning to ask them how to turn aProduct Backlog item into an Increment via a complete and
detailed Sprint Backlog.
H. The Scrum Master is no longer needed.
Answer: DEF
Explanation:
According to the Scrum Guide, three behaviors that demonstrate that a team is self-organizing are creating their own sprint backlog, having all the skills needed to
create a releasable Increment, and collaboratively selecting their own work during the Sprint. The other options are not behaviors that demonstrate
self-organization, as they are either contrary to Scrum values and principles (such as stakeholders walking in at the Daily Scrum or working within functional
boundaries) or unnecessary for self-organization (such as the Product Owner not being at Sprint Retrospectives or the Development Team inviting external people
to the Sprint Planning).
NEW QUESTION 9
Which approach is best for Scrum Teams in order to produce valuable Increments? (Choose the best answer.)
A. Each Developer works on the component where they feel that they can contribute.
B. Each Scrum Team is accountable for developing functionality from beginning to end.
C. Each Scrum Team works on an independent set of components.
D. Each Scrum Member works only as an independent layer of the system.
Answer: A
Explanation:
According to the Scrum Guide, the best approach for Scrum Teams in order to produce valuable Increments is to have each Developer work on the component
where they feel that they can contribute. This means that the Developers can self-organize and collaborate effectively to deliver a valuable Increment that meets
the Definition of Done and the Sprint Goal. The other options are not valid approaches, as they either imply that the Developers work in silos or rely on external
people (such as developing functionality from beginning to end, working on an independent set of components, or working only as an independent layer of the
system).
NEW QUESTION 10
Which technique is the best way the Scrum Master can ensure that the Development Team communicates effectively with the Product Owner?
Answer: A
Explanation:
The correct answer is A, because the best way the Scrum Master can ensure that the Development Team communicates effectively with the Product Owner is to
monitor communications between them and facilitate direct collaboration. The Scrum Guide states that “the Scrum Master serves the Product Owner in several
ways, including … facilitating Scrum events as requested or needed.” Therefore, the Scrum Master should help the Development Team and the Product Owner
interact regularly and productively during the Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective events.
NEW QUESTION 10
Several Sprints into a project, the Product Owner tells the Scrum Master that a key stakeholder just started using the product. The stakeholder is unhappy with the
quality of the product. What are two good options for the Scrum Master? (Choose the best two answers.)
Answer: BE
NEW QUESTION 12
When does a Sprint conclude? (choose the best answer)
A. When the Product Owner decides enough has been delivered to meet the Sprint Goal.
B. When the Sprint Retrospective is complete.
C. When all the tasks are completed by the Developers.
D. When all Product Backlog items meet their Definition of Done.
Answer: B
Explanation:
According to the Scrum Guide, a Sprint concludes when the Sprint Retrospective is complete. This is the last event of the Sprint cycle, where the Scrum Team
inspects itself and creates a plan for improvements. The other options are not valid indicators of the conclusion of a Sprint, as they are either irrelevant (such as
the Product Owner deciding enough has been delivered) or incomplete (such as all tasks or Product Backlog items being done).
NEW QUESTION 15
Every Scrum Team must have a Product Owner and Scrum Master. (Choose the best answer.)
A. Tru
B. Outcomes affected by their participation and availability.
C. Fals
D. A Product Owner can be replaced by a subject matter expert in the Scrum Team.
E. Fals
F. A Scrum Master is only required when asked for by the Scrum Team.
G. Tru
H. Each must be 100% dedicated to the Scrum Team.
Answer: A
Explanation:
According to the Scrum Guide, every Scrum Team must have a Product Owner and a Scrum Master, as they are essential roles for Scrum. The outcomes of the
Scrum Team are affected by their participation and availability, as they provide guidance, support, and facilitation to the Development Team and the stakeholders.
The other options are false, as they imply that a Product Owner or a Scrum Master can be replaced or optional, which is not consistent with Scrum.
NEW QUESTION 20
What are two good ways for the Development Team to make non-functional requirements visible? (Choose two.)
A. Put them on a separate list on the Scrum board, available for all to see.
B. Add them to the Product Backlog and keep the Product Owner posted on the expected effort.
C. Run the integration and regression tests before the end of the Sprint, and capture the open work for the Sprint Backlog of the next Sprint.
D. Add them to the definition of “Done” so the work is taken care of every Sprint.
Answer: BD
Explanation:
The correct answers are B and D, because adding non-functional requirements to the Product Backlog and keeping the Product Owner posted on the expected
effort helps prioritize and plan them in alignment with the product vision and goals. Additionally, adding non-functional requirements to the definition of ‘Done’
ensures that they are met every Sprint and do not accumulate technical debt.
References: Suggested Reading for Professional Scrum Master™ I
NEW QUESTION 22
Every Development Team should have:
A. At least one representative from each major software engineering discipline (like QA, Dev, UX).
B. The competencies and skills needed to deliver a Done Increment in a Sprint.
C. One Lead Developer and no more than 8 other members.
Answer: B
Explanation:
According to the Scrum Guide1, the Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done”
product at the end of each Sprint. Development Teams are structured and empowered by the organization to organize and manage their own work. The resulting
synergy optimizes the Development Team’s overall efficiency and effectiveness. Cross-functional teams have all competencies needed to accomplish the work
without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.
References: Scrum Guide
NEW QUESTION 25
What techniques could the Scrum Master use when the Scrum Team gets caught in an internal disagreement about which agile practices to apply? (Choose the
best two answers.)
Answer: AB
Explanation:
Two techniques that the Scrum Master could use when the Scrum Team gets caught in an internal disagreement about which agile practices to apply are to
involve the complete Scrum Team in making a decision, and to use coaching techniques such as open questions and active listening, as stated in [3]: “The Scrum
Master should facilitate a constructive dialogue among the team members and help them reach a consensus on which agile practices to use. The Scrum Master
should also use coaching techniques such as open questions and active listening to understand the underlying needs and motivations of each team member and
to help them find common ground.”
NEW QUESTION 30
In accordance with Scrum theory, how should a group of 100 people be divided into multiple Development Teams?
A. Understanding the product, the product vision and the rules of the Scrum framework, the group divides itself into teams.
B. It doesn’t really matter because you can rotate the teams every Sprint to spread knowledge.
C. Check with the allocation department to see who has worked together before and make these the first teams.
D. Create a matrix of skills, seniority, and level of experience to assign people to teams.
Answer: A
Explanation:
The correct answer is A, because in accordance with Scrum theory, a group of 100 people should be divided into multiple Development Teams by understanding
the product, the product vision and the rules of the Scrum framework, and then dividing itself into teams. This approach respects the self-organization and
empowerment of the people who will do the work, and allows them to form cross-functional and collaborative teams that can deliver value.
NEW QUESTION 32
How much work Is required of the Developers to complete a Product Backlog Item selected during the Sprint Planning?
(choose the best answer)
Answer: B
Explanation:
According to the Scrum Guide, the amount of work required of the Developers to complete a Product Backlog item selected during the Sprint Planning is as much
as is required to meet the Scrum Team’s Definition of Done. This means that the Developers must ensure that every item they work on is in a usable condition
and meets all quality standards agreed upon by the team. The other options are not valid descriptions of the amount of work required, as they are either too vague
(such as all development work and some testing or a proportional amount of time) or incorrect (such as fitting as much as possible or deferring work to the next
Sprint).
NEW QUESTION 37
When a Development Team is having trouble delivering a working Increment because they don’t understand a functional requirement, what should they do?
B. Partially complete the functionality, and discuss the remaining work at the Sprint Review.
C. Collaborate with the Product Owner to determine what is possible and acceptable.
D. Defer the work to a more appropriate Sprint.
Answer: C
Explanation:
The correct answer is C, because when a Development Team is having trouble delivering a working Increment because they don’t understand a functional
requirement, they should collaborate with the Product Owner to determine what is possible and acceptable. The Scrum Guide states that “the Product Owner is
responsible for maximizing the value of the product resulting from work of the Development Team. How this is done may vary widely across organizations, Scrum
Teams, and individuals.” Therefore, the Product Owner should clarify the functional requirement and negotiate the scope of work with the Development Team.
NEW QUESTION 39
A product Increment must be released to production at the end of each Sprint.
A. True
B. False
Answer: B
Explanation:
The correct answer is B, because a product Increment does not have to be released to production at the end of each Sprint. The Scrum Guide states that “at the
end of a Sprint, the new Increment must be ‘Done,’ which means it must be in useable condition and meet the Scrum Team’s definition of ‘Done’. 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.” Therefore, a product
Increment must be potentially releasable, but the decision to release it is up to the Product Owner.
NEW QUESTION 42
A Scrum Master is essentially the same thing as a traditional PM (Project Manager).
A. True
B. False
Answer: B
Explanation:
The correct answer is B, because a Scrum Master is not the same thing as a traditional PM (Project Manager). The Scrum Guide states that “the Scrum Master is
responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices,
rules, and values.” Therefore, a Scrum Master is not a manager, but a servant-leader and a coach for the Scrum Team and the organization.
NEW QUESTION 44
What are three benefits of self-organization? (Choose three.)
A. Increased creativity.
B. Increased rule compliance.
C. Increased accuracy of estimates.
D. Increased self-accountability
E. Increased commitment.
Answer: ADE
Explanation:
According to the Scrum Guide1, self-organization is one of the essential characteristics of Scrum Teams.
Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Self-organization enables teams to deliver
faster and better results by harnessing their creativity and skills. Some benefits of self-organization are:
Increased creativity, as team members have more freedom and autonomy to explore new ideas and solutions.
Increased self-accountability, as team members take ownership and responsibility for their work and outcomes.
Increased commitment, as team members are more engaged and motivated by having a say in how they work.
The other options are not benefits of self-organization, as they may imply external control or pressure. References: Scrum Guide
NEW QUESTION 45
Which of the following are topics for the Developers to discuss at the Daily scrum as they inspect their progress toward the Sprint Goal?
(choose the best three answers)
A. what have we learned since yesterday, and now should we modify our plan to increase our ability to meet the Sprint Goal?
B. Are mere any impediments Clocking progress toward the sprint Goal?
C. What will I be working on tomorrow?
D. Are mere any decisions that need to be made to maintain progress toward the sprint Goal?
E. Why were you late?
F. How many hours Old I spend on the project yesterday
G. win todays work negatively impact our ability to meet the sprint Goal for the Split following this one?
Answer: ABD
Explanation:
Three topics for the Developers to discuss at the Daily Scrum as they inspect their progress toward the Sprint Goal are:
What have we learned since yesterday, and how should we modify our plan to increase our ability to meet the Sprint Goal?
Are there any impediments blocking progress toward the Sprint Goal?
Are there any decisions that need to be made to maintain progress toward the Sprint Goal?
These topics are suggested by [6]: “The structure of the meeting is set by the Developers and can be conducted in different ways if it focuses on progress toward
the Sprint Goal. Some Development Teams will use questions, some will be more discussion based.”
NEW QUESTION 50
user documentation is part ot your Definition ot Done. However, there are not enough technical writers for all teams. Your Scrum Team does not have a technical
writer. What should the Scrum Team do?
(choose the best answer)
A. The Developers on the Scrum Team should write the user documentatiom
B. Wait until you have a technical writer on your Scrum Team to take care of this.
C. Form a separate team of technical writers that will work on an on-demand basis torthe various Product Owner
D. Work order will be first in, first out.
E. Let the user documentation remain undone and accumulate until after the last development Sprin
F. It will then be done by any available technical writers.
Answer: A
Explanation:
According to the Scrum Guide, the Developers on the Scrum Team should write the user documentation, as they are responsible for creating a “Done” Increment
that meets the Definition of Done and the Sprint Goal. The other options are not valid, as they imply that the user documentation can be deferred, ignored, or
outsourced, which is not consistent with Scrum values and principles.
NEW QUESTION 51
Who creates the definition of “Done”?
A. The Scrum Master as he/she is responsible for the Development Team’s productivity.
B. The Scrum Team, in a collaborative effort where the result is the common denominator of all members’ definition.
C. The Product Owner as he/she is responsible for the product’s success.
D. The development organization (or Development Team if none is available from the development organization).
Answer: D
Explanation:
According to the Scrum Guide1, the definition of “Done” is a formal description of the state of the Increment when it meets the quality measures required for the
product. The definition of “Done” is created by the development organization (or Development Team if none is available from the development organization). The
definition guides the Development Team in creating a “Done” Increment.
References: Scrum Guide
NEW QUESTION 54
The IT manager asks a Development Team for a status report describing the progress throughout the Sprint. The Development Team asks the Scrum Master for
advice. The Scrum Master should:
(Choose the best answer.)
A. Talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review.
B. Tell the Development Team to figure it out themselves.
C. Tell the Development Team to fit the report into the Sprint Backlog.
D. Create and deliver the report to the manager herself.
E. Ask the Product Owner to send the manager the report.
Answer: A
Explanation:
The Scrum Master should talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review, as stated in [5]:
“The Scrum Master should educate the IT manager about how Scrum works and how progress is measured. The Scrum Master should invite the IT manager to
attend the Sprint Review where the Development Team demonstrates what was accomplished during the Sprint. The Scrum Master should also explain that status
reports are not necessary in Scrum, as transparency is ensured by using artifacts such as Product Backlog, Sprint Backlog, and Increment.”
NEW QUESTION 58
The Sprint Goal is a result of Sprint Planning, as is the Sprint Backlog.
A. True
B. False
Answer: A
Explanation:
According to the Scrum Guide1, the Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides
guidance to the Developers on why it is building the Increment. It also provides a basis for inspecting and adapting during the Sprint Review and Sprint
Retrospective. The Sprint Goal is a result of Sprint Planning, as is the Sprint Backlog.
References: Scrum Guide
NEW QUESTION 63
When is a Sprint over?
Answer: D
Explanation:
The correct answer is D, because the Scrum Guide states that “a Sprint is a container for all other events. Each event in Scrum is a formal opportunity to inspect
and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in
reduced transparency and is a lost opportunity to inspect and adapt.” Therefore, a Sprint is over when its time-box expires, regardless of whether all Product
Backlog items or tasks are completed or not.
NEW QUESTION 68
Multiple Scrum Teams working on the same project must have the same Sprint start date.
A. True
B. False
Answer: B
Explanation:
The correct answer is B, because multiple Scrum Teams working on the same project do not have to have the same Sprint start date. The Scrum Guide states that
“multiple Scrum Teams often work together on the same product. One product goal unites them. Therefore, they must mutually define and comply with a definition
of ‘Done’ that applies to their combined work product.” Therefore, the synchronization of multiple Scrum Teams is based on their shared product goal and
definition of ‘Done’, not on their Sprint start date.
NEW QUESTION 73
Which are characteristics of the Daily Scrum? (choose the best two answers)
Answer: AB
Explanation:
According to the Scrum Guide, two characteristics of the Daily Scrum are its location and time remain constant and its purpose is to inspect progress toward the
Sprint Goal and adapt the Sprint Backlog. These characteristics promote consistency, transparency, and adaptation within the Development Team. The other
options are not valid characteristics of the Daily Scrum, as they are either irrelevant (such as being held first thing in the morning) or inappropriate (such as being
free form, facilitated by the team lead, or consisting of the Scrum Master asking for status).
NEW QUESTION 76
Who creates the Definition of Done? (choose the best answer)
Answer: C
Explanation:
The correct answer is C. The Scrum Team creates the Definition of Done. According to the Scrum Guide1, “The Developers are required to conform to the
Definition of Done, which is defined and evolves with the Scrum Team.” The Definition of Done is a commitment by the Developers for the Increment, but it is also
a shared understanding within the whole Scrum Team, including the Product Owner and the Scrum Master2.
The Scrum Team collaborates to create and update the Definition of Done as needed, based on the product and organizational standards3. The Definition of Done
is not imposed by any external authority or individual.
NEW QUESTION 80
Which of these may a Development Team deliver at the end of a Sprint?
A. Failing unit tests, to identify acceptance tests for the next Sprint.
B. An increment of software with minor known bugs in it.
C. An increment of working software that is “done”.
D. A single document, if that is what the Scrum Master asked for.
Answer: C
Explanation:
The correct answer is C, because a Development Team should deliver an increment of working software that is “done” by the end of a Sprint. The Scrum Guide
states that “the Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end
of a Sprint, the new Increment must be ‘Done,’ which means it must be in useable condition and meet the Scrum Team’s definition of ‘Done’.”
NEW QUESTION 84
A Development Team is required to deliver a done Increment by the end of a Sprint. Select two statements that explain what “Done” means. (Choose two.)
Answer: CE
Explanation:
The correct answers are C and E, because these statements explain what “Done” means. No work left from the definition of “Done” means that all Product
Backlog items selected for a Sprint meet the quality criteria agreed upon by the Scrum Team. All work to create software that is ready to be released to end users
means that the Increment is potentially releasable at any time during the Sprint.
NEW QUESTION 89
When does the next Sprint begin?
Answer: B
Explanation:
The next Sprint begins immediately after the conclusion of the previous Sprint, as stated in the Scrum Guide: “Sprints have consistent durations throughout a
development effort. A new Sprint starts immediately after the conclusion of the previous Sprint.”
NEW QUESTION 94
The Product Owner determines how many Product Backlog items the Development Team selects for a Sprint.
A. False.
B. True, accordingly to what was committed to the stakeholders.
C. True, but only after confirmation by the resource manager that the Team has enough capacity.
D. True.
E. False, the Scrum Master does that.
F. False, capacity and commitment are the Project manager’s responsibility.
Answer: A
Explanation:
The correct answer is A, because the Product Owner does not determine how many Product Backlog items the Development Team selects for a Sprint. The Scrum
Guide states that “the number of items selected from the Product Backlog for the Sprint is solely up to the Development Team. Only the Development Team can
assess what it can accomplish over the upcoming Sprint.” Therefore, the Development Team is responsible for choosing the scope of work for a Sprint.
NEW QUESTION 97
What is the recommended size for a Scrum Team? (Choose the best answer.)
A. At least 7.
B. 9
C. 10 or fewer.
D. 7 plus or minus 3.
Answer: C
Explanation:
The recommended size for a Scrum Team is 10 or fewer people, as stated in the Scrum Guide: “The recommended size of a Scrum Team is small enough to
remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people.”
NEW QUESTION 99
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? (Choose
the best answer.)
Answer: B
Explanation:
According to the Scrum Guide, estimates are made by the people doing the work, which is the Development Team. The Development Team is responsible for all
estimates in the Product Backlog and the Sprint Backlog. The other options are not valid guidelines for estimating work in Scrum, as they are either too prescriptive
(such as requiring story points or relative units), incorrect (such as forbidding estimating or having the Product Owner make estimates), or unnecessary (such as
checking estimates with the Development Team).
A. The Scrum process, and how it was used during the Sprint.
B. Coding and engineering practices.
C. Sprint results.
D. All of the above.
Answer: D
Explanation:
All of the above topics should be discussed in the Sprint Review, as stated in [4]: "The purpose of this meeting is to inspect what was delivered during this sprint
and adapt what we want to deliver next. This means we will discuss three things:
What did we do this sprint?
How did we do it?
What do we want to do next?"
Answer: CE
Explanation:
According to the Scrum Guide1, each Sprint is a project with no more than a one-month horizon. The Sprint Goal gives guidance to why the Scrum Team is
building an Increment. The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the
end of each Sprint. Therefore, in the first Sprint, as in any other Sprint, the Development Team should develop at least one piece of functionality and create an
increment of potentially releasable software. The other options are not consistent with Scrum values and principles.
References: Scrum Guide
Answer: C
Explanation:
According to the Scrum Guide, Developers are self-managing, which means that they manage their own Sprint Backlog. They decide how to organize their work
and collaborate effectively to deliver a valuable Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid, as they imply that
Developers manage things that are either determined by the Scrum framework (such as Sprint length), by collaboration with other roles (such as when to release
or stakeholders for the Sprint Review), or by the Product Owner (such as Product Backlog ordering).
Answer: B
Explanation:
According to the Scrum Guide, management external to the Scrum Team is not involved in the Daily Scrum at all. The Daily Scrum is an internal event for the
Development Team to inspect their progress toward the Sprint Goal and plan their work for the next 24 hours. The other options are not valid ways for
management to be involved in the Daily Scrum, as they are either intrusive (such as giving an update or speaking on behalf of others) or unnecessary (such as
being represented by the Product Owner or the Scrum Master).
Answer: CEF
Explanation:
The correct answers are C, E, and F, because these phrases best describe the purpose of a definition of “Done”. It creates transparency over the work inspected
at the Sprint Review, as it defines what it means for an Increment to be potentially releasable. It guides the Development Team in creating a forecast at the Sprint
Planning, as it helps them estimate how much work they can accomplish in a Sprint. It defines what it takes for an Increment to be ready for release, as it ensures
that the product meets the quality expectations of the stakeholders.
A. The Scrum Team may add items to the Sprint Backlog for the next Sprint.
B. The Scrum Team should choose at least one high priority process improvement to place in the Product Backlog.
C. The Scrum Team should decline to add a process improvement to the Sprint Backlog when things are running smoothly.
D. The Scrum Master selects the most important process improvement and places it in the Sprint Backlog
Answer: A
Explanation:
During the Sprint Retrospective, the Scrum Team may add items to the Sprint Backlog for the next Sprint, as stated in [5]: “The purpose of each Sprint
Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team plans ways to implement improvements identified during this meeting into its
way of working. By doing this it reinforces empiricism throughout its work. Improvements may be implemented at any time during a Sprint or they may be planned
for subsequent Sprints.”
Answer: D
Explanation:
According to the Scrum Guide, the Scrum Team should make sure that everyone on the team does their tasks for the Sprint, as they are collectively accountable
for creating valuable Increments that meet stakeholder needs and expectations. The other options are not valid, as they imply that someone else outside the
Scrum Team (such as a project manager) or another role on the Scrum Team (such as the Product Owner or the Scrum Master) is responsible for making sure
that everyone does their tasks for the Sprint.
Answer: BC
Explanation:
According to the Scrum Guide1, there are five values that guide decisions within Scrum teams:
Commitment
Focus
Openness
Respect
Courage
In order to achieve the benefits of Scrum, it is important to enact these values. Two actions that demonstrate the commitment of Scrum Team members are:
Help the other Scrum Team members, as they work together as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment by
the end of the Sprint.
Do your best, as they strive to deliver a potentially releasable Increment that meets the definition of “Done” and provides value to the stakeholders.
A. True
B. False
Answer: A
Explanation:
According to the Scrum Guide1, the heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product
Increment is created. The 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.
References: Scrum Guide
A. The Scrum Team includes skilled individuals who together have all the skins necessary to create value each sprint
B. Developers on the Scrum Team work closely with business analysis architects developers, and testers who are not on the team
C. The Scrum Team includes not only developers but also business analysts, architects, and testers
D. The Scrum Team is a virtual team drawing from separate teams of business analysts, architects, developers, and testers
Answer: A
Explanation:
According to the Scrum Guide, a Scrum Team is cross-functional if it includes skilled individuals who together have all the skills necessary to create value each
Sprint. This means that the Developers can work on any aspect of the product without depending on others outside the team. The other options are not valid
descriptions of cross-functionality, as they either imply that the Developers work in silos or rely on external people (such as business analysts, architects, testers,
or separate teams).
Answer: D
Explanation:
A Product Backlog item is considered complete when it meets the Definition of Done, as stated in [5]: “When a Product Backlog item or an Increment is described
as “Done”, everyone must understand what “Done” means. Although this varies significantly per Scrum Team, members must have a shared understanding of
what it means for work to be complete, to ensure transparency. This is the definition of “Done” for the Scrum Team and is used to assess when work is complete
on the product Increment.”
A. Sprint Review.
B. Release Planning.
C. Sprint Retrospective.
D. Refinement Meeting.
E. Daily Scrum.
Answer: ACE
Explanation:
The correct answers are A, C, and E, because these are feedback loops in Scrum. The Sprint Review is a feedback loop that allows the Scrum Team and the
stakeholders to inspect the Increment and adapt the Product Backlog. The Sprint Retrospective is a feedback loop that allows the Scrum Team to inspect itself and
create a plan for improvements. The Daily Scrum is a feedback loop that allows the Development Team to inspect its progress and plan its work for the next 24
hours.
Answer: BD
Explanation:
According to the Scrum Guide1, the Sprint Planning meeting has a time-box of eight hours or less for a one-month Sprint. The Scrum Master ensures that the
meeting is time-boxed and keeps the Scrum Team
focused on the objective. If the Development Team cannot forecast how many Product Backlog items it can complete, it should still start the Sprint and work on the
most likely items to meet the Sprint Goal. The Sprint Backlog can be updated throughout the Sprint as more is learned. The Scrum Master should also support the
team to discuss the reasons for the lack of clarity in the Product Backlog items and how to prevent it from happening again in the next Sprint Retrospective.
References: Scrum Guide
A. Sprint length.
B. How to best accomplish its work.
C. Stakeholders for the Sprint Review.
D. When to release, based on its progress.
E. Product Backlog ordering.
Answer: B
Explanation:
According to the Scrum Guide, a self-organizing Development Team chooses how to best accomplish its work, rather than being directed by others outside the
team. The other options are not choices that a self-organizing Development Team makes, as they are either determined by the Scrum framework (such as Sprint
length and Product Backlog ordering) or by collaboration with other roles (such as stakeholders for the Sprint Review and when to release).
A. True
B. False
Answer: B
Explanation:
According to the Scrum Guide, a Scrum Team is not only allowed to meet with stakeholders during Sprint Review, but also during Sprint Planning and throughout
the Sprint as needed. The Sprint Review is an opportunity for the Scrum Team and the stakeholders to collaborate on what was done in the Sprint and what to do
next. However, it is not the only time that stakeholder feedback is welcomed and valued.
Answer: C
Explanation:
According to the Scrum Guide, a Development Team needs a Sprint Goal because it provides guidance and focus for building an Increment that delivers value.
The other options are not valid reasons for having a Sprint Goal, as they are either incorrect (such as giving purpose only to Sprint 0 or ensuring implementation of
all Product Backlog items) or irrelevant (such as knowing everything from the Product Backlog).
A. 1 day
B. 4 hours for a one-month Sprint.
C. As long as needed
D. 2 hours for a one-month Sprint.
Answer: B
Explanation:
The timebox for the Sprint Review is four hours for a one-month Sprint, as stated in [4]: “The Sprint Review is held at the end of the Sprint to inspect the Increment
and adapt the Product Backlog if needed. 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 Owner explains what Product Backlog items have been
“Done” and what has not been “Done”; additionally, they discuss any changes to scope or budget or potential value. The entire group then collaborates on what
to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning. The Sprint Review is a working session and attendees should inspect
based on facts. A Sprint Review is held at the end of every Sprint for a maximum duration of four hours for a one-month Sprint.”
A. The Scrum Master, or the Scrum Master may have the Development Team do it.
B. The Scrum Master.
C. The Product Owner.
D. The business analyst who represents the Product Owner in the Development Team.
Answer: C
Explanation:
According to the Scrum Guide1, the Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of
requirements for any changes to be made to the product. The Product Owner is accountable for maximizing value resulting from work by Developers. The Product
Owner is also accountable for effective Product Backlog management, which includes:
A. True
B. False
Answer: B
Explanation:
According to the Scrum Guide, the Product Owner does not make sure that the Developers select enough from the Product Backlog for a Sprint to satisfy the
stakeholders. The Developers are responsible for selecting how much work they can do in a Sprint, based on their capacity and past performance. The Product
Owner may influence them by ordering and clarifying the Product Backlog items, but does not control their selection.
Answer: B
Explanation:
The correct answer is B, because the time-box for a Daily Scrum is 15 minutes. The Scrum Guide states that “the Daily Scrum is a 15-minute time-boxed event for
the Development Team to synchronize activities and create a plan for the next 24 hours.”
Answer: CDE
Explanation:
According to the Scrum Guide, the Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted
during the next Sprint. The topics that are appropriate for discussion are those that relate to how the team does its work, such as team relations, Definition of
Done, and processes, tools, communication, collaboration, quality, etc. The other options are not appropriate topics for discussion in a Sprint Retrospective, as
they belong to other Scrum events (such as arranging the Sprint Backlog for the next Sprint in the Sprint Planning or evaluating the value of work in the Product
Backlog in the Sprint Review).
Answer: A
Explanation:
According to the Scrum Guide1, ordering Product Backlog items is solely up to the Product Owner’s discretion. The Product Owner orders items in the Product
Backlog to best achieve goals and missions. To do this, they optimize value by considering various factors such as cost and benefit, risk, dependencies, date
needed, etc. The Product Owner is responsible for maximizing the value of the work the Development Team does.
References: Scrum Guide
A. True
B. False
Answer: B
Explanation:
According to the Scrum Guide, an Increment does not have to be released to customers or users at the end of each Sprint. However, it must be in a usable
condition and meet the Definition of Done. The decision to release an Increment is made by the Product Owner, based on the value and feedback obtained from
stakeholders. The other option is not valid, as it implies that releasing an Increment is mandatory at the end of each Sprint.
Answer: A
Explanation:
The correct answer is A, because the Product Owner does not need to be present at the Daily Scrum. The Scrum Guide states that “the Daily Scrum is a
15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. … The structure of the meeting is set by
the Development Team and can be conducted in different ways if it focuses on progress toward the Sprint Goal.” Therefore, the Daily Scrum is an internal event
for the Development Team, and the Product Owner can attend only if invited by the Development Team.
A. How will we make sure all teams have the right amount or expertise?
B. What is the right mixture of senior and junior people on each team?
C. Who are going to be the team leads?
D. Who are the subject matter experts on each team?
Answer: A
Explanation:
The correct answer is A, because a good first question for you to suggest the group thinks about when forming into teams is how will we make sure all teams have
the right amount of expertise. This question helps the group consider the cross-functionality and self-organization of the Development Teams, which are essential
for delivering a potentially releasable Increment every Sprint.
References: [Suggested Reading for Professional Scrum Master™ I]
Answer: CD
Explanation:
A Developer is accountable for creating a plan for the Sprint, the Sprint Backlog, and organizing the work required to meet the Sprint Goal, as stated in the Scrum
Guide: "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."
A. True
B. False
Answer: B
Explanation:
According to the Scrum Guide1, there is no such thing as a Release Sprint in Scrum. A Release Sprint implies that there are other Sprints that don’t produce a
potentially releasable Increment, which violates the core principle of Scrum. Every Sprint should result in a “Done”, useable, and potentially releasable product
Increment.
Answer: C
A. 7 plus or minus 3.
B. At least 7.
C. 9
D. 10 or fewer.
Answer: D
Explanation:
The correct answer is D. 10 or fewer. According to the Scrum Guide 20201, “The Scrum Team is small enough to remain nimble and large enough to complete
significant work within a Sprint, typically 10 or fewer people.” The other options are outdated or incorrect. Option A was based on the previous version of the
Scrum Guide, which suggested a range of 3 to 9 developers2. Option B is too vague and does not account for the upper limit of team size. Option C is too specific
and does not allow for flexibility.
A. A decomposition of all Product Backlog items into tasks for future Sprint Backlog lists.
B. Additional features in a usable state that complement those delivered in previous iterations.
C. A new user interface design for functionality delivered in previous iterations.
D. An automated test suite to verify functionality delivered in previous iterations.
E. UML diagrams that describe how to deliver functionality in future iterations.
Answer: B
Explanation:
According to the Scrum Guide1, 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, an Increment must be usable. Multiple Increments may be created within
a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders prior
to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value. Therefore, the best description of an increment of working
software is additional features in a usable state that complement those delivered in previous iterations.
References: Scrum Guide
A. When calculated and estimated, the total amount of technical debt shows exactly how long until the Product Owner can release the Increment.
B. It leads to false assumptions about the current state of the system, specifically of an Increment being releasable at the end of a Sprint.
C. As development progresses and code is added, the system becomes more difficult to stabilize, which results in future work being slowed down in unpredictable
ways.
D. It enhances transparency for the Product Owner as a Development Team is not allowed to do additional feature development in a Sprint as long as there is
technical debt.
Answer: BC
Explanation:
The correct answers are B and C, because technical debt impacts transparency in these ways. It leads to false assumptions about the current state of the system,
specifically of an Increment being releasable at the end of a Sprint, as it may contain hidden defects or incomplete functionality. It also results in future work being
slowed down in unpredictable ways, as development progresses and code is added, the system becomes more difficult to stabilize and maintain.
A. Accumulated cost.
B. Individual worker productivity.
C. Work remaining across time.
D. Accumulated business value delivered to the customer.
Answer: C
Explanation:
The correct answer is C, because if burndown charts are used to visualize progress, they track work remaining across time. A burndown chart is a graphical
representation of the amount of work left to do versus the time available. It helps the Scrum Team monitor and forecast the progress toward the Sprint Goal.
A. The Developers.
B. The Scrum Master.
C. The Product Owner.
D. The Project Manager.
Answer: A
Explanation:
According to the Scrum Guide, the Developers are accountable for tracking the remaining work toward the Sprint Goal, as they are responsible for creating a
valuable Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid, as they imply that someone else outside the
Development Team (such as the Scrum Master, the Product Owner, or the Project Manager) is accountable for tracking the remaining work, which is not
consistent with Scrum values and principles.
A. The Development Team includes not only developers but also business analysts, architects, and testers.
B. The Development Team includes cross-skilled individuals who are able to contribute to do what is necessary to deliver an increment of software.
C. Developers on the Development Team work closely with business analysts, architects, developers and testers who are not on the team.
D. The Development Team is a virtual team drawing from separate teams of business analysts, architects, developers and testers.
Answer: B
Explanation:
A cross-functional Development Team is one that includes cross-skilled individuals who are able to contribute to do what is necessary to deliver an increment of
software, as stated in the Scrum Guide1: “Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of
the team.”
A. Yes, but only for Scrum Teams whose work has dependencies.
B. No, that is tar too nard and must be done in a hardening Sprint
C. No, each Scrum Team stands alone.
D. Yes, in order to accurately inspect what is done.
Answer: D
Explanation:
According to the Scrum Guide, when multiple Scrum Teams are working on the same product, they should integrate their Increments every Sprint, in order to
accurately inspect what is done and ensure that there is no technical debt or unfinished work at the end of each Sprint. The other options are not valid, as they
imply that integration can be skipped, delayed, or done only for some teams, which is not consistent with Scrum values and principles.
A. Users
B. Scrum Master
C. Product Owner
D. Development Team
E. Customers
Answer: BCD
Explanation:
According to the Scrum Guide, the Scrum Team consists of three roles: the Scrum Master, who coaches and facilitates the team; the Product Owner, who
manages and prioritizes the Product Backlog; and the Development Team, who delivers a potentially releasable Increment at the end of each Sprint. Users and
customers are not roles on the Scrum Team, but they are stakeholders who may provide feedback and input to the product.
Answer: A
Explanation:
The correct answer is A, because a Sprint Retrospective should be held at the end of each Sprint. The Scrum Guide states that “the Sprint Retrospective is an
opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. … The Sprint Retrospective occurs after
the Sprint Review and prior to the next Sprint Planning.”
A. When the Development Team feels that the work is too hard.
B. When the Sprint Goal becomes obsolete.
C. When the sales department has an important new opportunity.
D. When it becomes clear that not everything will be finished by the end of the Sprint.
Answer: B
Explanation:
According to the Scrum Guide1, a Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint,
although he or she may do so under influence from the stakeholders, the Developers, or the Scrum Master. A Sprint would be cancelled if the Sprint Goal becomes
obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be cancelled if it no longer
makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense.
References: Scrum Guide
A. 7 plus or minus 3.
B. At least 7.
C. 9.
D. 3 to 9.
Answer: D
Explanation:
The correct answer is D, because the recommended size for a Development Team is 3 to 9 members. The Scrum Guide states that “fewer than three
Development Team members decrease interaction and results in smaller productivity gains. Smaller Development Teams may encounter skill constraints during
the Sprint, causing the Development Team to be unable to deliver a potentially releasable Increment. Having more than nine members requires too much
coordination. Large Development Teams generate too much complexity for an empirical process to be useful.”
A. The break between Sprints is time-boxed to 1 week for 30 day Sprints, and usually less for shorter sprints.
B. Enough time for the requirements for the next Sprint to be determined and documented.
C. Enough time for the Development team to finish the testing from the last Sprint.
D. Non
E. A new Sprint starts immediately following the end of the previous Sprint.
F. All of the above are allowed depending on the situation.
Answer: D
Explanation:
The correct answer is D, because there is no gap between Sprints in Scrum. The Scrum Guide states that “a new Sprint starts immediately after the conclusion of
the previous Sprint.” Therefore, there is no time required after a Sprint to prepare for the next Sprint.
Answer: D
Explanation:
The Sprint Backlog is the Development Team’s plan for the Sprint, as stated in the Scrum Guide1: “The Sprint Backlog is a plan with enough detail that changes
in progress can be understood in the Daily Scrum. The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges
during the Sprint.”
Answer: A
Explanation:
There is no such thing as Sprint 0 in Scrum, as stated in [7]: “Sprint 0 is a term used by some people who use Scrum to describe an initial period before starting
Sprints where they do some upfront planning or analysis. However, this is not part of Scrum and contradicts its principles of empirical process control, iterative
delivery, and responding to change.”
A. Postpone the work until a specialist can perform a security audit and create a list of security-related Product Backlog items.
Answer: BE
Explanation:
According to the Scrum Guide1, the definition of “Done” is a formal description of the state of the Increment when it meets the quality measures required for the
product. The definition guides the Development Team in creating a “Done” Increment. The definition of “Done” is created by the development organization (or
Development Team if none is available from the development organization). The definition of “Done” may vary significantly per Scrum Team, depending on the
context. One aspect of Scrum Teams inspecting how they work toward their Product Goal is that they improve their definition of “Done” over time. Therefore, one
good way for a Scrum Team to ensure security concerns are satisfied is to add security concerns to the definition of “Done”. Another good way is to have the
Scrum Team create Product Backlog items for each concern, as they are responsible for managing and refining the Product Backlog.
References: Scrum Guide
A. Short enough to keep the business risk acceptable to the Product Owner.
B. Short enough to be able to synchronize the development work with other business events.
C. No more than one calendar month.
D. All of these answers are correct.
Answer: D
Explanation:
According to the Scrum Guide1, the heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product
Increment is created. Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous
Sprint. The length of a Sprint should be short enough to keep the business risk acceptable to the Product Owner, short enough to be able to synchronize the
development work with other business events, and no more than one calendar month.
References: Scrum Guide
Answer: BC
Explanation:
The correct answers are B and C, because these are two responsibilities of a self-organizing Development Team. The Scrum Guide states that “the Development
Team consists of professionals who do the work of delivering a potentially releasable Increment of ‘Done’ product at the end of each Sprint. Development Teams
are structured and empowered by the organization to organize and manage their own work.” Therefore, the Development Team should pull Product Backlog items
for the Sprint and do the work planned in the Sprint Backlog.
A. The Development Team after clarifying requirements with the Product Owner.
B. The Product Owner with input from the Development Team.
C. The most senior people in the organization, including architects and subject matter experts.
D. The Scrum Master.
E. The Development Team, alone.
Answer: A
Explanation:
According to the Scrum Guide1, Product Backlog refinement is an ongoing activity in which Product Backlog items are reviewed and revised. The Developers who
will be doing the work are responsible for sizing or estimating it. The Product Owner may influence them by helping them understand and select trade-offs.
Answer: D
Explanation:
According to the Scrum Guide, the Product Owner can cancel a Sprint, as he or she is responsible for maximizing the value of the product and the work of the
Development Team. The other roles do not have this authority, although they may provide input and suggestions to the Product Owner.
Answer: AD
Explanation:
The correct answers are A and D, because a Development Team is responsible for resolving internal team conflicts and organizing the work required to meet the
Sprint Goal. The Scrum Guide states that “development Teams are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn
Product Backlog into Increments of potentially releasable functionality.” Therefore, a Development Team should manage its own work and resolve its own issues.
A. The Sprint is extended and future Sprints use this new duration.
B. The Sprint length holds and the Development Team continuously learns what is actually possible to do within a Sprint of this length.
C. The Sprint is extended temporaril
D. Lessons are taken to ensure it doesn’t happen again.
Answer: B
Explanation:
If the Development Team cannot complete its work by the end of the Sprint, then the Sprint length holds and the Development Team continuously learns what is
actually possible to do within a Sprint of this length, as stated in [7]: “If a Development Team determines it has overcommitted itself for a Sprint, one option is to
collaborate with the Product Owner to negotiate removing or reducing scope. Another option is to simply work hard and do its best, without cutting quality or
pressuring individuals. In either case, the Development Team learns from its experience and uses this learning when planning future Sprints.”
A. Architects.
B. The Development Team.
C. The Scrum Master.
D. Subject matter experts.
E. Development Team managers.
Answer: B
Explanation:
The correct answer is B, because the Development Team determines how work is performed during the Sprint. The Scrum Guide states that “development Teams
are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable
functionality.” Therefore, the Development Team has the autonomy and responsibility to organize and manage its own work.
Answer: B
Explanation:
According to the Scrum Guide1, 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, an Increment must be usable. Multiple Increments may be created within
a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders prior
to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value. Therefore, implementation of a Product Backlog item is
considered complete when the item has no work remaining in order to be potentially released.
Answer: B
Answer: B
Explanation:
According to the Scrum Guide, every Scrum Team should have the competencies and skills needed to deliver an Increment in a Sprint. This means that the
Developers can work on any aspect of the product without depending on others outside the team. The other options are not valid descriptions of what every Scrum
Team should have, as they either imply that the Developers work in silos or rely on external people (such as a lead developer or representatives from different
departments).
A. Manage them during the Integration Sprint prior to the Release Sprint.
B. Assign them to the lead developers on the team.
C. Ensure every Increment meets them.
D. Make sure the release department understands these requirements, but it is not the Scrum Team's responsibility.
Answer: C
Explanation:
The best answer is C. Ensure every Increment meets them. Non-functional requirements (NFRs) are system qualities that guide the design of the solution and
often serve as constraints across the relevant
backlogs1. NFRs are persistent qualities and constraints typically revisited as part of the definition of done (DoD) for each Iteration, PI, or release1. The Scrum
Team should ensure that every Increment meets the NFRs, as they are part of the product requirements and affect the value delivery and customer satisfaction.
Answer: D
Explanation:
The Development Team must do as much work as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the
definition of “Done”, as stated in the Scrum Guide1: “The Development Team works to forecast the functionality that will be developed during the Sprint. The
Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint
Goal. The entire Scrum Team collaborates on understanding the work of the Sprint.”
Answer: A
Explanation:
The correct answer is A, because keeping component teams while starting Scrum may cause less initial disruption than organizing into new teams. As they start
using Scrum, they will discover what works best for them and how to potentially re-organize towards feature teams. However, component teams may face some
challenges in delivering a working Increment of software that provides business value every Sprint, as they may depend on other teams or layers.
Answer: CF
Explanation:
According to the Scrum Guide1, each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable
critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt. All events
are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The
remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process.
The time-box for the Daily Scrum is 15 minutes or less for a one-month Sprint. Its location and time remain constant.
References: Scrum Guide
Answer: A
Explanation:
The correct answer is A, because the Scrum Guide states that “the definition of ‘Done’ is a formal description of the state of the Increment when it meets the
quality measures required for the product.” Therefore, non-functional requirements should be part of the definition of ‘Done’ and ensure every Increment meets
them.
A. Suggest the Product Owner extend the Sprint, so he can have more time to order the Product Backlog.
B. Suggest that the Development Team does the ordering to be sure that it is a feasible ordering of work.
C. Offer the Product Owner help in understanding that the goal of ordering the Product Backlog is to maximize value.
D. Present the Product Owner with an ordered Product Backlog to use.
E. Encourage the Product Owner to work with the Development Team to see which items technically are fastest to implement.
Answer: C
Explanation:
According to the Scrum Guide1, ordering Product Backlog items is solely up to the Product Owner’s discretion. The Product Owner orders items in the Product
Backlog to best achieve goals and missions. To do this, they optimize value by considering various factors such as cost and benefit, risk, dependencies, date
needed, etc. The Product Owner is responsible for maximizing the value of the work the Development Team does. 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. Therefore, an appropriate action for the Scrum Master to take if the Product Owner is struggling with ordering the Product Backlog is to offer the
Product Owner help in understanding that the goal of ordering the Product Backlog is to maximize value.
References: Scrum Guide
A. Create teams based on their skills across multiple layers (such as database, UI, etc.)
B. Ask the Product Owner to assign the people to teams.
C. Ask the developers to divide themselves into teams.
Answer: C
Explanation:
According to the Nexus Guide2, which is a framework for scaling Scrum, one way to form multiple Development Teams from a large group of people is to ask them
to self-organize into teams based on dependencies, skills, domain knowledge, and personal preferences. This approach respects the autonomy and empowerment
of the Developers and allows them to choose how they want to work together.
References: Nexus Guide
A. Monthly.
B. 8 hours for a one-month Sprint
C. Whenever ills done
D. 4 hours for a one-month Sprint
Answer: B
Explanation:
According to the Scrum Guide, the timebox for a Sprint Planning event is 8 hours for a one-month Sprint, proportionally shorter for shorter Sprints. The other
options are not valid, as they are either too long (such as monthly), too vague (such as whenever it’s done), or too short (such as 4 hours for a one-month Sprint).
Answer: C
Explanation:
According to the Scrum Guide1, the Sprint Review is an informal meeting at the end of the Sprint, where the Scrum Team and stakeholders collaborate about what
was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on what to do next. The Product Owner
explains what Product Backlog items have been “Done” and what has not been “Done”; the Development Team discusses what went well during the Sprint, what
problems it ran into, and how those problems were solved; and the Development Team demonstrates the work that it has “Done” and answers questions about
the Increment. The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning. The Sprint
Review is mainly an inspect and adapt opportunity for the Scrum Team and stakeholders.
References: Scrum Guide
A. Teach the Product Owner to work with the lead developers on ordering Product Backlog in a way to avoid too much technical and development overlap during a
Sprint.
B. Teach them that it is their responsibility to work with the other teams to create an integrated Increment.
C. Collect the Sprint tasks from the teams at the end of their Sprint Planning and merge that into a consolidated plan for the entire Sprint.
D. Visit the five teams each day to inspect that their Sprint Backlogs are aligned.
Answer: B
Explanation:
According to the Scrum Guide1, when multiple Scrum Teams are working together on the same product, they must mutually define and comply with the same
definition of “Done”, which includes creating an integrated Increment at least by the end of each Sprint. The Scrum Master should teach and coach the Developers
that it is their responsibility to work with other Scrum Teams to create an integrated Increment that meets the definition of “Done”. The other options are not
aligned with Scrum values and principles.
References: Scrum Guide
A. Existing teams propose how they would like to go about organizing into the new structure.
B. Managers personally re-assign current subordinates to new teams.
C. Managers collaborate to assign individuals to specific teams.
D. Bring all the developers together and let them self-organize into Development Teams.
E. The Chief Product Owner determines the new team structures and assignments.
Answer: AD
Explanation:
The correct answers are A and D, because these ways of creating Development Teams are consistent with Scrum’s values. Allowing existing teams to propose
how they would like to organize into the new structure respects their self-organization and empowerment. Bringing all the developers together and letting them self-
organize into Development Teams also respects their autonomy and collaboration.
References: [Suggested Reading for Professional Scrum Master™ I]
* PSM-I Most Realistic Questions that Guarantee you a Pass on Your FirstTry
* PSM-I Practice Test Questions in Multiple Choice Formats and Updatesfor 1 Year