Scrum Scrum Certifications PSPO-I Questions & Answers

• Question 111:

  Several Sprints into a project, the Product Owner tells the Scrum Master that a key stakeholder just started using the product. The stakeholder is unhappy with the quality of the product.

  What are two good options for the Scrum Master?

  (choose the best two answers)

  A. Coach the Product Owner on how to talk with the Developers about this concern.

  B. Wait to bring this up until the Sprint Retrospective.

  C. Explain to the Product Owner that it is up to the Developers to decide on acceptable quality standards.

  D. Encourage the Product Owner to put quality specifications on the Product Backlog and express the stakeholder's concern to the Developers.

  E. Bring the concern to the testers to improve how the Product is verified.

  Correct Answer: AD

  If a stakeholder is unhappy with the quality of the product, the Scrum Master can coach the Product Owner on how to effectively communicate this concern to the Developers1. The Scrum Master can also encourage the Product Owner to put quality specifications on the Product Backlog1. This allows the Developers to understand the stakeholder's expectations and work towards meeting them1. The Developers are responsible for building quality into the product, but the stakeholders (through the Product Owner) are responsible for setting what is expected in terms of product and process quality1.

• Question 112:

  True or False: The Scrum Team is accountable for creating a valuable increment every Sprint.

  A. True

  B. False

  Correct Answer: A

  Explanation: The Scrum Team is accountable for creating a valuable increment every Sprint. The Increment is the sum of all Product Backlog items Done during a Sprint and the value of all the previous Increments. The entire Scrum Team is accountable for creating a valuable and useful Increment every Sprint1. The Product Owner is responsible for maximizing the value of the product resulting from the work of the Scrum Team1. The Developers are responsible for creating a Done Increment that meets the Sprint Goal1. The Scrum Master is responsible for establishing Scrum as defined in the Scrum Guide and helping everyone understand Scrum theory, practices, rules, and values1. References: Scrum Guide What is an Increment and how Does it Connect with the other Elements of Scrum? The Professional Product Owner

• Question 113:

  Which of the following are criteria to order Product Backlog items?

  (choose the best three answers)

  A. The value of the Product Backlog items.

  B. The availability of the Scrum Master.

  C. Dependencies between Product Backlog items.

  D. Their relevance to achieving the Product Goal.

  E. The number of stakeholders who approve of the item.

  Correct Answer: ACD

  Explanation: A Product Owner orders a Product Backlog in any way they think will maximize the value of the product1. They take various factors into consideration when ordering the Product Backlog such as business value, risk, return on investment (ROI), dependencies and impact1. Dependencies between Product Backlog items and their relevance to achieving the Product Goal are two of these factors12. The availability of the Scrum Master and the number of stakeholders who approve of the item are not valid criteria for ordering the Product Backlog3.

• Question 114:

  Who can cancel a Sprint?

  (choose the best answer)

  A. The Scrum Team.

  B. The Scrum Master

  C. The Product Owner.

  D. The Stakeholders.

  Correct Answer: C

  The Product Owner is the sole person responsible for managing the Product Backlog and ensuring that the value of the work the Scrum Team performs is understood by everyone involved. The Product Owner is the only person who can cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master1. 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. A Sprint would be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be cancelled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense1. References: Scrum Guide Sprint Cancellation Can Scrum Master cancel a sprint?

• Question 115:

  A Scrum Team is required to deliver a done Increment by the end of a Sprint. Select two statements that explain what done means.

  (choose the best two answers)

  A. No work is left to meet the Definition of Done.

  B. Whatever the Product Owner defines as quality.

  C. Ready for integration.

  D. Ready to be released to end users.

  E. All work the Developers are willing to do.

  Correct Answer: AD

  A Scrum Team is required to deliver a done Increment by the end of a Sprint. Done means:

  No work is left to meet the Definition of Done. The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It is a shared understanding among the Scrum Team and

  the stakeholders of what it means for work to be complete. It may include criteria such as coding standards, testing, documentation, security, performance, etc. If a Product Backlog item or an Increment does not meet the Definition of Done, it

  cannot be released or presented at the Sprint Review. Ready to be released to end users. The Increment is a concrete output of the Sprint that adds value to the product. It is a potentially releasable functionality that adheres to the Scrum

  Team's current Definition of Done. It is not necessarily released at the end of each Sprint, but it must be in a state that allows for immediate release if the Product Owner decides so. The Increment should also align with the Sprint Goal and

  the Product Goal, and satisfy the needs and expectations of the customers and stakeholders.

  References:

  Scrum Guide 2020, page 10: "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 2020, page 10: "The moment a Product Backlog item meets the Definition of Done, an Increment is born."

  Scrum Guide 2020, page 14: "The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current Definition of Done."

• Question 116:

  An organization has decided to adopt Scrum, but management wants to change the terminology to fit with terminology already used.

  What will likely happen if this is done?

  (choose the best answer)

  A. Without a new vocabulary as a reminder of the change, very little change may actually happen.

  B. The organization may not understand what has changed within Scrum and the benefits of Scrum may be lost.

  C. Management may feel less anxious.

  D. All answers apply.

  Correct Answer: D

• Question 117:

  A Project Manager working with your Scrum Team has raised concerns about progress and money spent. What are the two best responses?

  (choose the best two answers)

  A. Promote transparency by sharing the Product Backlog and ensuring the Project Manager has access.

  B. Have a discussion with the Project Manager; share the current impediments and forecast for the Sprint.

  C. Show the Earned Value Analysis (EVA) report.

  D. Scrum does not have Project Managers so disregard their concerns.

  E. Share the last stakeholder briefing document prepared by the Product Owner.

  Correct Answer: AB

  The two best responses to a Project Manager who has raised concerns about progress and money spent are:

  Promote transparency by sharing the Product Backlog and ensuring the Project Manager has access. This helps communicate what is needed to improve the product, what is planned for each Sprint, and what has been done so far. It also

  helps align expectations and priorities among different stakeholders. Have a discussion with the Project Manager; share the current impediments and forecast for the Sprint. This helps address any issues or risks that may affect the delivery of

  value and the achievement of the Sprint Goal. It also helps provide feedback and adaptation based on the empirical evidence and data. Other options, such as showing the Earned Value Analysis (EVA) report, Scrum does not have Project

  Managers so disregard their concerns, or sharing the last stakeholder briefing document prepared by the Product Owner, are not the best responses as they do not reflect how to effectively collaborate and communicate with the Project

  Manager or how to apply the Scrum values and principles.

  References:

  [Scrum Guide], page 11, section "Product Backlog" [Scrum Guide], page 15, section "Sprint Backlog" [Scrum Guide], page 10, section "Increment"

  [Scrum Guide], page 5, section "Scrum Theory"

  [Scrum Guide], page 4, section "The Scrum Team"

• Question 118:

  True or False: The value delivered by a product can only be determined by revenue.

  A. True

  B. False

  Correct Answer: B

  The value delivered by a product can not be determined by revenue alone, because:

  Revenue is only one aspect of value, and it may not reflect the true impact or benefit of the product for the stakeholders, the users, and the society. For example, a product may generate high revenue, but also cause environmental damage,

  ethical issues, or customer dissatisfaction. Value is a subjective and relative concept, and it may vary depending on the context, the perspective, and the criteria of the evaluation. For example, a product may have different value for different

  segments of customers, or for different markets or regions.

  Value is dynamic and emergent, and it may change over time due to various factors, such as feedback, competition, innovation, or regulation. For example, a product may lose its value as new alternatives or solutions become available, or as

  customer needs or preferences evolve.

  References:

  Scrum Guide 2020, page 6: "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team." Scrum Guide 2020, page 11: "The Product Goal describes a future state of the product

  which can serve as a target for the Scrum Team to plan against." Scrum Guide 2020, page 11: "The Product Owner is accountable for effective Product Backlog management, which includes ... optimizing the value of the work the Scrum

  Team performs."

• Question 119:

  True or False: The Product Owner makes sure the correct stakeholders are invited to the Sprint Retrospective. They might have important instructions for team improvements.

  A. True

  B. False

  Correct Answer: B

  It is not true that the Product Owner makes sure the correct stakeholders are invited to the Sprint Retrospective. They might have important instructions for team improvements. This is because:

  The Sprint Retrospective is an event where the Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. The purpose of the Sprint Retrospective is to plan ways to

  improve quality and effectiveness.

  The Sprint Retrospective is an internal event for the Scrum Team only. It is a safe and confidential space where the Scrum Team can openly and honestly reflect on their strengths and weaknesses, and identify actions to improve their

  performance and collaboration.

  The stakeholders are not invited to the Sprint Retrospective. They do not have a say in how the Scrum Team works or what they should improve. The stakeholders can provide feedback and suggestions to the Scrum Team in other events,

  such as the Sprint Review or the Product Backlog refinement sessions. The Product Owner is a member of the Scrum Team who is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are

  responsible for identifying and articulating the Product Goal, which is a long-term objective for the product that guides all the activities of the Scrum Team. The Product Owner does not make sure the correct stakeholders are invited to the

  Sprint Retrospective. They might have important instructions for team improvements. This would violate the self-management and autonomy of the Scrum Team and undermine their trust and empowerment.

  References:

  [Scrum Guide], page 18, section "Sprint Retrospective" [Scrum Guide], page 7, section "The Scrum Team"

  [Scrum Guide], page 17, section "Sprint Review"

  [Scrum Guide], page 6, section "Product Owner"

  [Scrum Guide], page 10, section "Product Goal"

• Question 120:

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

  A. Determine whether to cut quality, similar to the "Iron Triangle" of project management.

  B. Determine the cost of a project before it begins.

  C. Illustrate that as a project forecast lengthens, it is increasingly less certain.

  D. Determine the length of the next Sprint.

  Correct Answer: C

  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.

  References:

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