QUESTION: 97

Which two statements best describe a Sprint Goal? (Choose two.)

Sprint Goals are defined when the completed work is reviewed at the end of a Sprint.
Sprint Goals give the Development Teams flexibility and creativity on how to implement functionality during the Sprint.
During the Sprint Planning, the entire Scrum Team collaboratively crafts a Sprint Goal based on a business objective that the Product Owner would like to achieve that Sprint.
Sprint Goals can change as new insights emerge during the Sprint.

Answer(s): B,C

Explanation:

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.
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 Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.

Reveal Solution Next Question

QUESTION: 98

If there are multiple Scrum Teams working on the same product, all of the Scrum Teams must mutually define a Definition of Ready (DoR). The DoR is a checklist that the Product Owner must fulfill before a Product Backlog item can be presented at the Sprint Planning. This protects the Development Team from interruptions and disruptions during the Sprint.

True
False

Answer(s): B

Explanation:

Product Backlog items should be clear enough and have enough information for the Product Owner and Development to understand the work that needs to be done and to create a forecast of Product Backlog items to implement the Sprint Goal. Nothing stops the flow of Sprints, for example, we do not delay the Sprint because the items are not ready. In such cases, the “unready” items would be selected for the Sprint anyway and refined during the Sprint.
In the case that the Product Backlog items are not clear enough, the Development Team forecasts the most likely Product Backlog items to meet the goal and create a Sprint Backlog based on a likely initial design and plan. Once the time-box for the Sprint Planning meeting is over, start the Sprint and continue to analyze, decompose, and create additional functionality during the Sprint. At the end of the Sprint, the Scrum Team can discuss in theupcoming Sprint Retrospective why this happened and what changes will make it less likely to recur.

Reveal Solution Next Question

QUESTION: 99

How should a Scrum Master coordinate the work when more than one Scrum Team is working on one product?

Teach them that it’s their responsibility to coordinate with the other teams to integrate and create a shippable product Increment at the end of every Sprint.
Identify and manage the dependencies between Scrum Teams.
Have the Product Owner work with the tech leads of each team to parse the Product Backlog and minimize overlap in User Stories.
Merge the teams and work from a single Sprint Backlog.

Answer(s): A

Explanation:

One of the benefits of self-organized teams is the ability to decide how best to work together to produce a shippable Increment.

Reveal Solution Next Question

QUESTION: 100

What would be typical Scrum Master activities during the Sprint?

Monitor the progress of the Development Team and assigning tasks.
Remove impediments and facilitating inspection and adaptation opportunities as requested or needed.
Avoiding conflicts and escalating to the line managers if conflicts occur.

Answer(s): B

Reveal Solution Next Question

Free PSM II Exam Braindumps (page: 26)

QUESTION: 97

Explanation:

QUESTION: 98

Explanation:

QUESTION: 99

Explanation:

QUESTION: 100

PSM II Exam Discussions & Posts