Exam Scrum Guide PSM
Exam Scrum Guide PSM
Exam Scrum Guide PSM
Sprint Goal should remain intact. These are conditions that foster
creativity, quality and productivity. (Which one the following answers
is FALSE?)
The Sprint Backlog is fully formulated in the Sprint Planning event and does not change
during the Sprint.
Feedback
The Sprint Backlog makes visible all of the work that the Developers identify as necessary to
meet the Sprint Goal. The Developers modify the Sprint Backlog throughout the Sprint, and the
Sprint Backlog emerges during the Sprint.
Inform the other members of the Scrum Team so the team can decide what to do
Feedback
The items selected for a Sprint have been selected as most valuable with the Product Owner. The
items serve the Sprint's goal. No changes should be made that endanger the Sprint Goal. No one
external to the Scrum Team can force changes on the Developers.
True
Feedback
The heart of Scrum is a Sprint, a timebox of one month or less during which a done, useful, and
valuable working product Increment is created.
4) What are three incorrect, untrue, or misleading statements about
Scrum?(choose the best three answers)
Feedback
Feedback
A Sprint could be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the
authority to cancel the Sprint.
6) During a Sprint, a Developer determines that the Scrum Team will
not be able to complete the items in their forecast. Who should be
present to review and adjust the Product Backlog items selected?
(choose the best answer)
Feedback
During the Sprint, scope may be clarified and re-negotiated between the Product Owner and the
Developers as more is learned. It is important to be transparent when challenges arise since
ultimately the entire Scrum Team is accountable for creating a valuable, useful Increment.
Product Owner
Scrum Master
Developers
Feedback
The Scrum Team consists of one Scrum Master, one Product Owner, and Developers.
The Developers.
Feedback
The Developers use the Daily Scrum to inspect progress toward the Sprint Goal and to inspect
how progress is trending toward completing the work in the Sprint Backlog.
9) The timebox for the Sprint Planning event is?
Feedback
Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter
Sprints, the event is usually shorter.
10 or fewer.
Feedback
A Scrum Team is small enough to remain nimble and large enough to complete significant work
within a Sprint, typically 10 or fewer people. Generally smaller teams communicate better and
are more productive
Empirical
Feedback
Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that
knowledge comes from experience and making decisions based on what is observed.
Feedback
Sprint Review is a maximum four-hour timeboxed event for one-month Sprints. For shorter
Sprints, the event is usually shorter.
13) True or False: It is mandatory that the product Increment be
released to production at the end of each Sprint.
False
Feedback
The product Increment should be usable and releasable at the end of every Sprint, but it does not
have to be released.
14) Why is the Daily Scrum held at the same time and same place?
Feedback
The Daily Scrum is held at the same time and place each day to reduce complexity.
15) True or False: When multiple Scrum Teams work together on the
same product, each team should maintain a separate Product Backlog.
False
Feedback
Products have one Product Backlog, regardless of how many Scrum Teams are used. Any other
setup makes it difficult for the Developers to determine what they should work on.
Feedback
A new Sprint starts immediately after the conclusion of the previous Sprint.
17) Who is required to attend the Daily Scrum?
The Developers.
Feedback
Only the people doing the work described on the Sprint Backlog need to inspect and adapt at the
Daily Scrum. If the Product Owner or Scrum Master are actively working on items in the Sprint
Backlog, they participate as Developers, they will need to be at the Daily Scrum.
18) Which two things should the Scrum Team do during the first Sprint?
Feedback
The heart of Scrum is a Sprint, which is one month or less during which a done, usable, valuable
product Increment is created. This applies to every Sprint.
Developers.
The Scrum Master.
The Product Owner.
Feedback
The Scrum Team consists of the Scrum Master, the Product Owner and Developers. The Scrum
Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal.
20) True or False: The Scrum Team must choose at least one high
priority process improvement item, identified during the Sprint
Retrospective, and place it in the Sprint Backlog.
False
Feedback
An earlier version of the Scrum Guide prescribed the practice of placing one improvement in the
Sprint Backlog. This was removed in the 2020 update to the Scrum Guide because it was felt to
be too prescriptive. However, if this practice provides value to you then you should adopt it. It is
simply not prescribed anymore, but can still be valuable.
21) When many Scrum Teams are working on a single product, what
best describes the Definition of Done?
All Scrum Teams must have a Definition of Done that makes their combined Increment
valuable and useful.
Feedback
The Increment must be valuable and useful. This means that when many Scrum Teams are
working on a single product, they are expected to adhere to a single Definition of Done for the
Increment.
Teach the Developers to keep the Daily Scrum within the 15 minute timebox.
Feedback
The Scrum Master ensures that the Developers have the event, but the Developers are
responsible for conducting the Daily Scrum. The Scrum Master teaches the Developers to keep
the Daily Scrum within the 15-minute timebox. The Scrum Master enforces the rule that only
Developers participate in the Daily Scrum.
23) Who creates the Definition of Done?
If it is not an organizational standard, the Scrum Team must create a Definition of Done
appropriate for the product.
Feedback
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.
24) How much work must the Developers complete for each Product
Backlog item they select for a Sprint?
Enough so that each Product Backlog item they select meets the Definition of Done.
Feedback
The purpose of each Sprint is to deliver useful and valuable Increments that adhere to the Scrum
Team's current Definition of Done.
25) Who has the final say on the order of the Product Backlog?
Feedback
The Product Owner is the sole person responsible for ordering the Product Backlog.
15 minutes.
Feedback
The Daily Scrum is a 15-minute event for the Developers of the Scrum Team. The Scrum Master
serves the Scrum Team by ensuring that all Scrum events take place and are positive, productive,
and kept within the timebox.
27) When does a Developer become accountable for the value of a
Product Backlog item selected for the Sprint?
Never. The entire Scrum Team is accountable for creating value every Sprint.
Feedback
All members of the Scrum Team share in the accountability for creating value every Sprint.
Feedback
Scrum Teams typically go through some steps before achieving a state of increased performance.
Changing membership typically reduces cohesion, affecting performance and productivity in the
short term.
Feedback
The Sprint is a container for the following timeboxed events: Sprint Planning, Daily Scrum, Sprint
Review, and Sprint Retrospective. Sprints are fixed length events of one month or less to create
consistency, and a new Sprint starts immediately after the conclusion of the previous Sprint.
The Sprint Retrospective concludes the Sprint, and is timeboxed to a maximum of three hours for
a one-month Sprint. For shorter Sprints, the event is usually shorter
Though not typical, a Sprint can end if the Sprint Goal becomes obsolete. Only the Product Owner
has the authority to end the Sprint prematurely.
30) The Developers should have all the skills needed to:
Turn the Product Backlog items they select into an Increment of useful and valuable
product functionality.
Feedback
The Developers are a group of professionals who do the work of delivering an Increment of done
product at the end of each Sprint. As a team, Developers have all of the skills necessary to create
a product Increment.
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.
One month or less.
All of the above.
Feedback
All of these choices are appropriate considerations in determining the length of a Sprint.
32) What is the main reason for the Scrum Master to be at the Daily
Scrum?
They do not have to be there; they only need to ensure the Developers have a Daily
Scrum.
Feedback
The Scrum Master only ensures that all Scrum events take place and are positive, productive, and
kept within the timebox.
False
Feedback
A Scrum Team has a Scrum Master, a Product Owner and Developers. As a whole they have all
controls needed.
34) What are two ways a Scrum Master serves to enable effective
Scrum Teams?
Feedback
The Scrum Master serves the Scrum Team in several ways. Facilitation and removing
impediments are examples of ways a Scrum Master helps a team become more effective.
Feedback
The Product Owner is accountable for maximizing the value of the product and the work of the
Scrum Team.
Feedback
Scrum is a lightweight framework that helps people, teams and organizations generate value
through adaptive solutions for complex problems.
37) What is the function or purpose of Management in Scrum?
Support the Product Owner with insights and information into high value product and
system capabilities. Support the Scrum Master to encourage organizational change that
fosters empiricism, self-management, bottom-up intelligence, and intelligent product
delivery.
Feedback
Management has no official role or accountability on a Scrum Team. However, management
external to the Scrum Team is relevant in setting the vision and strategy to guide the overall
direction of the organization.
Feedback
Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that
knowledge comes from experience and making decisions based on what is known.
Three pillars uphold every implementation of empirical process control: transparency, inspection,
and adaptation.
39) When does a Developer become the sole owner of an item on the
Sprint Backlog?
Never. All Sprint Backlog items are "owned" by the Developers on the Scrum Team.
Feedback
The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint, and
the set of Product Backlog items selected for the Sprint are collectively owned by the Developers.
No individual Developer can claim ownership over an item as this would block communication
and collaboration. The Sprint Backlog is updated by the Developers throughout the Sprint as
more is learned.
40) What does it mean to say that an event has a timebox?
Feedback
Timeboxed events are events that have a maximum duration.
Feedback
The Product Owner is accountable for effective Product Backlog management. 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.
Sprint Retrospective.
Sprint Planning.
Sprint Review.
Feedback
The Scrum Guide states that the Sprint Planning, Sprint Retrospectives, and Sprint Reviews are
timeboxed events. Sprints are fixed length events of one month or less to create consistency, and
the Daily Scrum is a 15-minute event.
43) Who should know the most about the progress toward a business
objective or a release, and be able to explain the alternatives most
clearly?
Feedback
The Product Owner is the sole person responsible for ordering the Product Backlog. Their
responsibilities include making the Product Backlog visible, transparent, and clear to all.
It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure
out what to do next.
Feedback
Every event in Scrum, besides the Sprint, which is a container for the other events, is an
opportunity to Inspect and Adapt.