Scrum Basics Practice Test

The Daily Scrum is a 15-minute event for the Developers of the Scrum Team.

Further reading: The Daily Scrum

The Scrum Guide does not define strict limits. Previously 3-9 was recommended for the Developers, even before 7+/-2. However, the current Scrum Guide only states that a Scrum Team (including the Scrum Master, the Product Owner and the Developers) has typically 10 members or less.

Further reading: The Scrum Team

A Sprint could be cancelled if the Sprint Goal becomes obsolete.

Further reading: The Sprint

The answer which claims that the Product Backlog is optional contradicts the Scrum Guide in multiple ways:

• The Product Backlog is not optional in Scrum.
• User Stories can be used in Scrum (as an optional technique) for describing Product Backlog Items but these two are not the same.

Further reading: Product Backlog

As per the rules of Scrum, it is the Scrum Master.

One of the services of the Scrum Master to the Scrum Team is "Causing the removal of impediments to the Scrum Team’s progress".

Further reading: The Scrum Master

The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint.

Further reading: The Scrum Team

An Increment is a concrete stepping stone toward the Product Goal.

Further reading: The Increment

The Scrum Guide canonized the names of the events (it even canonized that these are events and not ceremonies and not even meetings). No more stand-up and demo. Grooming is called Refinement and is not an event but a process.

Further reading: Scrum Events

The false statement makes a direct connection between the Sprint Goal and the Definition of Done, which is wrong:

• The Sprint Goal has a business purpose and is peculiar to a Sprint;
• The Definition of Done is a generic statement. All Product Backlog Items must meet the Definition of Done when claimed to be done.

Further reading: The Definition of Done, Sprint Planning

The Product Owner is also accountable for effective Product Backlog management. - The Scrum Guide

Since the Scrum Team is self-managing, nobody assigns tasks to the team members.

The Sprint Backlog is under the authority of the Developers of the Scrum Team.

Further reading: The Product Owner

Changing the core design or ideas of Scrum, leaving out elements, or not following the rules of Scrum, covers up problems and limits the benefits of Scrum, potentially even rendering it useless.

Further reading: Purpose of the Scrum Guide

The Product Owner is also accountable for effective Product Backlog management

The Product Owner

The correct answer is: "Scrum Teams and their associated roles, events, artifacts, and rules", so much that this statement was part of the Scrum guide until the 2020 overhaul. The other answers are wrong for various reasons, e.g. Scrum has no ceremonies and detailed processes, elaborate methods and instructions. The "values, principles, pillars and rules" list is vaguely related to Scrum, however, it clearly misses the point.

Defined by the Scrum Guide:

Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.

Further reading: Sprint Planning

The Sprint Backlog is a plan by and for the Developers.

Sprint Backlog

The Daily Scrum is a 15-minute event for the Developers of the Scrum Team.

Daily Scrum

The 3 pillars are transparency, inspection and adaptation.

Further reading: Scrum Theory

The 2020 Scrum Guide has different wording for the same statement:

Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.

Further reading: The Definition of Scrum

The answer is in the Guide:

The Sprint Retrospective concludes the Sprint. It is timeboxed to a maximum of three hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.

Further reading: Sprint Retrospective

As stated in the guide:

Scrum is founded on empiricism and lean thinking.

Further reading: Scrum Theory

The Scrum Values are: Commitment, Focus, Openness, Respect, and Courage

Scrum Values