Cisco®
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
MuleSoft
All Vendors
  2. Home
  3. Exams
  4. Scrum
  5. PSM I

Free PSM I Exam Braindumps (page: 2)

Page 2 of 68
PDF with 268 Questions

When many Scrum Teams are working on the same product, should all of their increments be integrated every Sprint?

  1. Yes, but only for Scrum Teams whose work has dependencies.
  2. Yes, otherwise the Product Owners (and stakeholders) may not be able to accurately inspect what is done.
  3. No, each Scrum Team stands alone.
  4. No, that is far too hard and must be done in a hardening Sprint.

Answer(s): B

Explanation:

The correct answer is B, because 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, all the increments from different Scrum Teams working on the same product should be integrated every Sprint to enable inspection and adaptation by the Product Owner and stakeholders.



When can a Development Team cancel a Sprint?

  1. It can't. Only Product Owners can cancel Sprints.
  2. When functional expectations are not well understood.
  3. When the Product Owner is absent too often.
  4. When the selected Product Backlog items for the Sprint become unachievable.
  5. When a technical dependency cannot be resolved.

Answer(s): A

Explanation:

The correct answer is A, because the Scrum Guide states that "a Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master."

Therefore, a Development Team cannot cancel a Sprint by itself.



Which output from Sprint Planning provides the Development Team with a target and overarching direction for the Sprint?

  1. The Sprint Backlog.
  2. The Sprint Goal
  3. The release plan.
  4. Sprint Review minutes.

Answer(s): B

Explanation:

The correct answer is B, because the Scrum Guide states that "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." Therefore, the Sprint Goal provides the Development Team with a target and overarching direction for the Sprint.



How should a Development Team deal with non-functional requirements?

  1. Ensure every Increment meets them.
  2. Make sure the release department understands these requirements, but it is not the Development Team's responsibility.
  3. Handle them during the Integration Sprint preceding the Release Sprint.
  4. Assign them to the lead developers on the team.

Answer(s): A

Explanation:

The correct answer is A, because the Scrum Guide states that "the definition of `Done' is a formal description of the state of the Increment when it meets the quality measures required for the product." Therefore, non-functional requirements should be part of the definition of `Done' and ensure every Increment meets them.






Post your Comments and Discuss Scrum PSM I exam prep with other Community members:

PSM I Exam Discussions & Posts