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: 3)

Page 3 of 68
PDF with 268 Questions

When is a Sprint over?

  1. When the Product Owner says it is done.
  2. When all Product Backlog items meet their definition of "Done".
  3. When all the tasks are completed.
  4. When the time-box expires.

Answer(s): D

Explanation:

The correct answer is D, because the Scrum Guide states that "a Sprint is a container for all other events. Each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt." Therefore, a Sprint is over when its time-box expires, regardless of whether all Product Backlog items or tasks are completed or not.



Scrum has a role called "Project Manager".

  1. True
  2. False

Answer(s): B

Explanation:

The correct answer is B, because there is no role called "Project Manager" in Scrum. The Scrum Guide states that "Scrum recognizes no titles for Development Team members other than Developer, regardless of the work being performed by the person; there are no exceptions to this rule." Therefore, Scrum has only three roles: Product Owner, Scrum Master, and Developer.



What are two good ways for the Development Team to make non-functional requirements visible? (Choose two.)

  1. Put them on a separate list on the Scrum board, available for all to see.
  2. Add them to the Product Backlog and keep the Product Owner posted on the expected effort.
  3. Run the integration and regression tests before the end of the Sprint, and capture the open work for the Sprint Backlog of the next Sprint.
  4. Add them to the definition of "Done" so the work is taken care of every Sprint.

Answer(s): B,D

Explanation:

The correct answers are B and D, because adding non-functional requirements to the Product Backlog and keeping the Product Owner posted on the expected effort helps prioritize and plan them in alignment with the product vision and goals. Additionally, adding non-functional requirements to the definition of `Done' ensures that they are met every Sprint and do not accumulate technical debt.


Reference:

Suggested Reading for Professional Scrum MasterTM I



How much time is required after a Sprint to prepare for the next Sprint?

  1. The break between Sprints is time-boxed to 1 week for 30 day Sprints, and usually less for shorter sprints.
  2. Enough time for the requirements for the next Sprint to be determined and documented.
  3. Enough time for the Development team to finish the testing from the last Sprint.
  4. None. A new Sprint starts immediately following the end of the previous Sprint.
  5. All of the above are allowed depending on the situation.

Answer(s): D

Explanation:

The correct answer is D, because there is no gap between Sprints in Scrum. The Scrum Guide states that "a new Sprint starts immediately after the conclusion of the previous Sprint." Therefore, there is no time required after a Sprint to prepare for the next Sprint.






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

PSM I Exam Discussions & Posts