The correct answers are B, E, and F, because these activities would probably help the team in starting

up. Having the Scrum Team members introduce themselves and give a brief background of their skills

and work history helps build trust and rapport among them. Ensuring the team understands they

need a definition of “Done” helps create transparency and alignment on the quality standards for the

product. Asking the Product Owner to discuss the product or project, its history, goals, and context,

as well as answer questions helps clarify the vision and value of the product.

Reference: [Suggested Reading for Professional Scrum Master™ I]

Explanation of Correct Answer: According to the Scrum Guide1, the only required events in

Explanation: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.

Reference: Scrum Guide

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.

Reference: Scrum Guide

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.

According to the Scrum Guide1, Scrum is not a process, technique, or definitive method. Rather, it is

a framework within which you can employ various processes and techniques. Scrum makes clear the

relative efficacy of your product management and work techniques so that you can continuously

improve the product, the team, and the working environment.

The answer is A. True. The Sprint Backlog is a result of Sprint Planning, and it includes the Sprint

Goal. According to the Scrum Guide, the Sprint Backlog is composed of the Sprint Goal (why), the set

of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering

the Increment (how)1. The Sprint Goal is the single objective for the Sprint, and it provides

coherence and focus for the Scrum Team2. The Sprint Backlog is a plan by and for the Developers,

and it is updated throughout the Sprint as more is learned2.

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.

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.

The correct answer is B, because the Product Owner does not make sure the team selects enough

from the Product Backlog for a Sprint to satisfy the stakeholders. 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.

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.