CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Scrum
  5. PSPO-I

Free PSPO-I Exam Braindumps (page: 6)

Page 6 of 43
PDF with 171 Questions

True or False: During the Sprint Review the stakeholder's role is to reorder the Product Backlog.

  1. True
  2. False

Answer(s): B

Explanation:

During the Sprint Review, the stakeholder's role is not to reorder the Product Backlog, but rather to provide feedback and suggestions on the product and the process. Therefore, the answer is false because:
The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration. The stakeholders are invited to attend the Sprint Review as observers, participants, or customers, and they can share their opinions, ideas, or requests regarding the product and its features, functionality, quality, value, etc. The ordering of the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions. The Product Owner may consider the feedback and suggestions from the stakeholders, as well as other factors such as dependencies, risks, costs, etc., when ordering the Product Backlog. However, they are not obliged to follow or implement them.
The Product Backlog is not a fixed or final list of requirements, but rather an emergent and dynamic artifact that represents all the possible changes to the product. The Product Owner is accountable for effective Product Backlog management, which includes refining, communicating, and optimizing the Product Backlog items. The Product Owner may update the Product Backlog at any time, not only during the Sprint Review.


Reference:

Scrum Guide 2020, page 11: "The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner."
Scrum Guide 2020, page 11: "The Product Owner is accountable for effective Product Backlog management, which includes ... ordering Product Backlog items; and ensuring that the Product Backlog is transparent, visible and understood."
Scrum Guide 2020, page 15: "The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration."



As the Developers start work during the Sprint, they realize they have selected too much work to finish in the Sprint.
What should they do?
(choose the best answer)

  1. Find another Scrum Team to give the excess work to.
  2. As soon as possible in the Sprint, work with the Product Owner to remove some work or Product Backlog items.
  3. Inform the Product Owner at the Sprint Review, but prior to the demonstration.
  4. Reduce the Definition of Done and get all of the Product Backlog items done by the new definition.

Answer(s): B

Explanation:

This is the best answer because it respects the Scrum values of openness, commitment, and focus. The Developers should be transparent about their progress and collaborate with the Product Owner to adjust the Sprint scope accordingly. The Product Owner is responsible for maximizing the value of the product and the work of the Developers, so he or she should be involved in any decisions that affect the Sprint Goal and the Product Backlog.


Reference:

Scrum Guide, page 10: "If the work turns out to be different than the Developers expected, they collaborate with the Product Owner to negotiate the scope of Sprint Backlog within the Sprint." Scrum Guide, page 11: "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team."



What are two effective ways for a Scrum Team to ensure security concerns are satisfied? (choose the best two answers)

  1. Add security concerns to the Definition of Done.
  2. Delegate the work to the security department.
  3. Have the Scrum Team create Product Backlog items for each concern.
  4. Add a Sprint to specifically resolve all security concerns.
  5. Postpone the work until a specialist can perform a security audit and create a list of security- related Product Backlog items.

Answer(s): A,C

Explanation:

These are the best answers because they ensure that security concerns are addressed in a transparent and consistent way. By adding security criteria to the Definition of Done, the Scrum Team can make sure that every Increment meets a high standard of quality and security. By creating Product Backlog items for specific security concerns, the Scrum Team can prioritize and plan them in collaboration with the Product Owner and stakeholders.


Reference:

Scrum Guide, page 14: "The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product."

Scrum Guide, page 15: "The Product Backlog is an emergent, ordered list of what is needed to improve the product."



The "cone of uncertainty" can be used to do what?
(choose the best answer)

  1. Determine whether to cut quality, similar to the "Iron Triangle" of project management.
  2. Determine the cost of a project before it begins.
  3. Illustrate that as a project forecast lengthens, it is increasingly less certain.
  4. Determine the length of the next Sprint.

Answer(s): C

Explanation:

The "cone of uncertainty" is a graphical representation of the degree of uncertainty in a project estimate over time. It shows that the range of possible outcomes is wider at the beginning of the project and narrows down as the project progresses and more information becomes available. The "cone of uncertainty" can be used to illustrate that as a project forecast lengthens, it is increasingly less certain. This means that the longer the time horizon for a project, the more variability and risk there is in the estimate. This also implies that shorter iterations and frequent feedback can help reduce uncertainty and improve accuracy. The "cone of uncertainty" cannot be used to determine whether to cut quality, similar to the "Iron Triangle" of project management. The "Iron Triangle" is a model that shows the trade-offs between scope, time, and cost in a project. Quality is often considered as a fourth dimension that is affected by these three factors. Cutting quality is not a desirable option for any project, especially for Scrum projects that value delivering high-quality products that meet customer needs. The "cone of uncertainty" cannot be used to determine the cost of a project before it begins. The cost of a project depends on many factors, such as the scope, the resources, the complexity, the risks, and the market conditions. The "cone of uncertainty" only shows the range of possible outcomes based on the available information at a given point in time. It does not provide a definitive or accurate estimate of the cost before the project starts. The "cone of uncertainty" cannot be used to determine the length of the next Sprint. The length of the next Sprint is determined by the Scrum Team based on their empirical experience and their ability to deliver a potentially releasable Increment of value. The "cone of uncertainty" does not provide any guidance on how long a Sprint should be or how much work can be done in a Sprint.


Reference:

Scrum Guide: https://www.scrumguides.org/scrum-guide.html Cone of Uncertainty: https://www.agilealliance.org/glossary/cone-of-uncertainty/



Page 6 of 43



Post your Comments and Discuss Scrum PSPO-I exam with other Community members:

Barbara commented on October 07, 2024
good content!
UNITED STATES
upvote