Scrum Master Role Quiz

Developers

Changing the core design of Scrum is allowed

To break down and define Product Backlog items

To help people understand Scrum

Product Backlog items, Sprint Goal, and an actionable plan

Developers

Transparency

10

Stakeholders

Product Owner

To generate value through adaptive solutions for complex problems

Empiricism and lean thinking

It enables inspection and helps make informed decisions

To foster an environment for effective teamwork

To inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary

4 hours

To plan ways to increase quality and effectiveness

The single source of work undertaken by the Scrum Team

Ensuring that all Scrum events take place and are positive, productive, and kept within the timebox

Helping establish empirical product planning for a complex environment

Leading, training, and coaching the organization in its Scrum adoption

Sprints enable predictability by ensuring inspection and adaptation of progress toward a Product Goal at least every calendar month

The purpose of the Scrum Guide is to define Scrum and its elements, and to provide guidance on how to implement and use Scrum effectively.

Scrum was developed by Ken Schwaber and Jeff Sutherland in the early 1990s. The first version of the Scrum Guide was written in 2010.

Following the rules of Scrum and not leaving out any elements is important because it ensures that the core design and ideas of Scrum are maintained, problems are not covered up, and the full benefits of Scrum can be realized.

The three pillars of Scrum are transparency, inspection, and adaptation.

The five Scrum values are commitment, focus, openness, respect, and courage.

The purpose of the Sprint in Scrum is to turn a selection of work into an Increment of value.

The two foundations of Scrum are empiricism and lean thinking.

The purpose of Product Backlog refinement is to break down and further define Product Backlog items into smaller, more precise items.

The Product Goal describes a future state of the product which serves as a target for the Scrum Team to plan against.

The Sprint Backlog is composed of the Sprint Goal, the set of Product Backlog items selected for the Sprint, and an actionable plan for delivering the Increment.

The three specific accountabilities within the Scrum Team are the Developers, the Product Owner, and the Scrum Master.

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for effective Product Backlog management and making decisions that are visible in the content and ordering of the Product Backlog.

The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They help everyone understand Scrum theory and practice, both within the Scrum Team and the organization. They ensure the Scrum Team is effective in their work.

The values that give direction to the Scrum Team are focus, courage, openness, respect, and commitment to self-improvement.

The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations.

The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.

The Sprint Backlog consists of the Sprint Goal, the selected Product Backlog items for the Sprint, and the plan for delivering them.

The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary.

Coaching the team members in self-management and cross-functionality, helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done, causing the removal of impediments to the Scrum Team’s progress, and ensuring that all Scrum events take place and are positive, productive, and kept within the timebox.

Helping find techniques for effective Product Goal definition and Product Backlog management, helping the Scrum Team understand the need for clear and concise Product Backlog items, helping establish empirical product planning for a complex environment, and facilitating stakeholder collaboration as requested or needed.

Leading, training, and coaching the organization in its Scrum adoption, planning and advising Scrum implementations within the organization, helping employees and stakeholders understand and enact an empirical approach for complex work, and removing barriers between stakeholders and Scrum Teams.

Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint. The resulting plan is created by the collaborative work of the entire Scrum Team. It addresses topics such as defining a Sprint Goal, selecting items from the Product Backlog to include in the current Sprint, and finalizing the Sprint Goal.

False

True

False

False

True

True

True

True

True

True

False

True

False

False

True

True

True

True

True

True

True

True