PSPO-I Online Practice Questions and Answers

Correct Answer: B

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. References:

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."

Correct Answer: B

Explanation: Cross-functional teams are not optimized to work on one component or layer of a system only. This is because:

Cross-functional teams are teams that have all the skills and competencies needed to accomplish the work without depending on others who are not part of the team.

Cross-functional teams are able to deliver value across the entire product, rather than focusing on a specific component or layer. They can work on any aspect of the product that is needed to achieve the Sprint Goal and the Product Goal.

Cross-functional teams are more agile, collaborative, and creative than teams that are specialized or siloed. They can reduce dependencies, handoffs, and delays, and increase feedback, learning, and adaptation.

References:

[Scrum Guide], page 7, section "Developers"

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

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

Correct Answer: A

Correct Answer: A

According to Scrum.org, when splitting a large group into multiple Scrum Teams, it can be beneficial to allow the people to self-organize into smaller teams12. This approach respects the principle of self-organization, which is a key aspect of Scrum12. It allows individuals to choose the team they feel they can contribute to most effectively12. However, it's important to note that this process should be facilitated and guided to ensure a balanced distribution of skills and capabilities across the teams12.

Correct Answer: A

The Developers are accountable for managing the progress of work during a Sprint, as they are the ones who plan, execute, and deliver the work. The Scrum Guide states that "The Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint."1 The Developers are also responsible for conducting the Daily Scrum, a 15-minute event for the Developers to synchronize activities and create a plan for the next 24 hours.1 The Developers are self-managing, which means they decide how best to accomplish their work, rather than being directed by others outside the Scrum Team.1 References:

1: The Scrum Guide2, page 7

2: The Scrum Guide

Correct Answer: CD

Explanation: The Product Owner should care that the Scrum Team adheres to its Definition of Done because:

It helps to forecast the team's productivity over time. By having a clear and consistent Definition of Done, the Product Owner can measure the amount of work that the team can deliver in each Sprint and plan accordingly. It affects the

product's total cost of ownership. By ensuring that the work done by the team meets the quality standards and expectations of the stakeholders, the Product Owner can reduce the risk of technical debt, rework, defects, and maintenance costs

in the future.

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 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 14: "The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done,

it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration."

Correct Answer: B

Scrum

According to the Scrum Guide 2020, the entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint1234. This includes the Developers, the Product Owner, and the Scrum Master4. The Developers are committed to creating any aspect of a usable Increment each Sprint12, while the Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team12. The Scrum Master fosters an environment where the Scrum Team can work effectively1.

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.

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/

Correct Answer: BC

In Scrum, there is only one product and one Product Backlog for a given product. The Product Backlog is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements,

fixes, and anything else that can deliver value to the customers and users of the product. The Product Backlog is ordered by the Product Owner based on the product vision, goals, and value.

Having multiple Product Backlogs for one product would create confusion, duplication, inconsistency, and waste. It would also make it harder to align the Scrum Teams and the stakeholders on the same product direction and priorities.

Therefore, each Scrum Team should not have a separate Product Backlog. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for

managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake

in the product and ensures that the Scrum Team works on the right things at the right time.

Having multiple Product Owners for one product would create conflicts, overlaps, gaps, and inefficiencies. It would also make it harder to maintain a clear and consistent product vision, strategy, roadmap, and backlog. Therefore, there should

be only one Product Owner for one product.

In some cases, when there are multiple Scrum Teams working on one product, it may be necessary to have some form of scaling or coordination mechanism to ensure alignment and collaboration among the teams. However, this does not

mean that there should be multiple Product Owners or Product Backlogs. Instead, there should be ways to facilitate communication, feedback, integration, and transparency among the teams and with the Product Owner. For example, some

frameworks or practices that can help with scaling Scrum are Nexus, LeSS, SAFe, or Scrum of Scrums.

References:

Scrum Guide: https://www.scrumguides.org/scrum-guide.html Nexus: https://www.scrum.org/resources/what-is-nexus LeSS: https://less.works/

SAFe: https://www.scaledagileframework.com/

Scrum of Scrums: https://www.agilealliance.org/glossary/scrum-of-scrums/