SCrum Test 2
SCrum Test 2
Scrum Open
Duration: 00:04:26
Fe e dback
Congratulations! Your score on the Open assessment demonstrates you know your
Scrum basics.
Scrum on,
Ken Schwaber
Continue here
Return to Scrum.org
Question 1 of 30
A. When it becomes clear that not everything will be finished by the end of the
Sprint.
Fe e dback
A Sprint could be cancelled if the Sprint Goal becomes obsolete. Only the Product
Owner has the authority to cancel the Sprint.
Question 2 of 30
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.
True
False
Fe e dback
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.
Question 3 of 30
B. The Developers.
Fe e dback
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.
Question 4 of 30
A. 7 plus or minus 2.
B. Minimum of 7.
C. 10 or fewer.
D. 9.
Fe e dback
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
Question 5 of 30
A. Complete the project as estimated when the date and cost are committed to
the Product Owner.
B. Do all of the development work, except for specialized testing that requires
additional tools and environments.
C. Turn the Product Backlog items they select into an Increment of a useful
and valuable product.
Fe e dback
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.
Question 6 of 30
A. Monthly.
C. Whenever it is done.
D. 4 hours.
Fe e dback
Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For
shorter Sprints, the event is usually shorter.
Question 7 of 30
Fe e dback
Timeboxed events are events that have a maximum duration.
Question 8 of 30
A. Short enough to keep the business risk acceptable to the Product Owner.
Fe e dback
All of these choices are appropriate considerations in determining the length of a
Sprint.
Question 9 of 30
True or False : The purpose of a Sprint is to produce a valuable and useful Increment of a
usable product.
True
False
Fe e dback
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.
Question 10 of 30
What are two ways a Scrum Master serves to enable effective Scrum Teams?
Fe e dback
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.
Question 11 of 30
Fe e dback
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.
Question 12 of 30
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?
B. The Developers.
Fe e dback
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.
Question 13 of 30
What is the main reason for the Scrum Master to be at the Daily Scrum?
A. To write down any changes to the Sprint Backlog, including adding new
items, and tracking progress on the burn-down.
D. They do not have to be there; they only need to ensure the Developers
have a Daily Scrum.
Fe e dback
The Scrum Master only ensures that all Scrum events take place and are positive,
productive, and kept within the timebox.
Question 14 of 30
A. 15 minutes.
C. 4 hours.
Fe e dback
The Daily Scrum is always a 15-minute event. Because it is a short event, the timebox is
not influenced by the Sprint length.
Question 15 of 30
Fe e dback
Scrum is a lightweight framework that helps people, teams and organizations generate
value through adaptive solutions for complex problems.
Question 16 of 30
B. 1 day.
C. As long as needed.
D. 2 hours.
Fe e dback
Sprint Review is a maximum four-hour timeboxed event for one-month Sprints. For
shorter Sprints, the event is usually shorter.
Question 17 of 30
Who should know the most about the progress toward a business objective or a release, and
be able to explain the alternatives most clearly?
C. The Developers
Fe e dback
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.
Question 18 of 30
When many Scrum Teams are working on a single product, what best describes the Definition
of Done?
A. It depends.
B. Each Scrum Team uses its own, but must make their definition clear to all
other teams so the differences are known.
C. All Scrum Teams must have a Definition of Done that makes their combined
Increment valuable and useful.
Fe e dback
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.
Question 19 of 30
True or False : It is mandatory that the product Increment be released to production at the
end of each Sprint.
True
False
Fe e dback
The product Increment should be usable at the end of every Sprint, but it does not
have to be released.
Question 20 of 30
C. 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.
D. Identify and remove people that are not working hard enough.
Fe e dback
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.
Question 21 of 30
A. Developers
B. Product Owner
C. Users
D. Customers
E. Scrum Master
Fe e dback
The Scrum Team consists of one Scrum Master, one Product Owner, and Developers.
Question 22 of 30
When does a Developer become the sole owner of an item on the Sprint Backlog?
D. Never. All Sprint Backlog items are "owned" by the Developers on the Scrum
Team.
Fe e dback
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.
Question 23 of 30
D. Managing the project and ensuring that the work meets the commitments to
the stakeholders.
Fe e dback
The Product Owner is accountable for maximizing the value of the product and the work
of the Scrum Team.
Question 24 of 30
Fe e dback
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.
Question 25 of 30
A. Refinement.
B. Release Retrospective.
C. Sprint Review.
D. Release Testing.
E. Sprint Planning.
F. Sprint Retrospective.
G. Sprint Testing.
Fe e dback
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.
Question 26 of 30
When does a Developer become accountable for the value of a Product Backlog item selected
for the Sprint?
A. Never. The entire Scrum Team is accountable for creating value every
Sprint.
Fe e dback
All members of the Scrum Team share in the accountability for creating value every
Sprint.
Question 27 of 30
How much work must the Developers complete for each Sprint?
Fe e dback
The purpose of each Sprint is to deliver useful and valuable Increments that adhere to
the Scrum Team's current Definition of Done.
Question 28 of 30
A. Project Manager.
C. Developers.
Fe e dback
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.
Question 29 of 30
An organization has decided to adopt Scrum, but management wants to change the
terminology to fit with terminology already used. What will likely happen if this is done?
B. The organization may not understand what has changed with Scrum and
the benefits of Scrum may be lost.
Question 30 of 30
B. The Scrum Master since they are responsible for the productivity of the
Developers.
C. The Scrum Team, in a collaborative effort where the result is the common
denominator of all members' definitions.
D. The Product Owner since they are responsible for the product's success.
Fe e dback
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.