Pass the Scrum PSPO PSPO-I Questions and answers with CertsForce

The Scrum Master should talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review. This is because:

The Scrum Team is self-managing and does not need to report to anyone outside the team1.

The Sprint Review is an event where the Scrum Team and the stakeholders collaborate on the product and inspect the Increment2.

The Increment is a concrete and usable outcome of the Sprint that provides a measure of progress and value delivery3.

The IT manager can attend the Sprint Review as a stakeholder and provide feedback on the product and the process4.

The Product Owner should not have the entire Product Backlog documented in detail before the first Sprint can start. This is because:

The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is never complete and constantly changes to reflect the needs and desires of the customers, users, and stakeholders.

The Product Owner 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 collaborates with the Developers and the stakeholders to refine the Product Backlog as needed to ensure that there are enough items that are sufficiently clear and ready for selection in Sprint Planning. The amount of detail and precision required for each Product Backlog item depends on its order, size, and complexity.

The Product Owner does not need to have the entire Product Backlog documented in detail before the first Sprint can start, as this would imply a fixed and upfront plan that does not allow for feedback, learning, and adaptation. Instead, the Product Owner only needs to have enough items that are well understood and valuable for the Scrum Team to start working on them in the first Sprint.

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.

The Product Backlog is an ordered list of everything that is known to be needed in the product. It 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.

All types of requirements are acceptable on a Product Backlog, as long as they are aligned with the product vision and goals, and they are transparent, clear, and valuable. The Product Backlog can include stability requirements, performance requirements, product functionality, documentation, fixes, or any other aspects that contribute to the quality and usability of the product.

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.

The Developers are accountable for creating a “Done” Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.

An Increment is a concrete stepping stone toward the product vision. It is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be “Done”, which means it meets the Definition of Done and is usable.

The Scrum Team decides when and how to release an Increment to customers or users. The Product Owner is responsible for maximizing the value of the product and the work of the Developers, and may decide to release an Increment at any time during or after a Sprint. The Developers are responsible for creating a potentially releasable Increment each Sprint, and may collaborate with the Product Owner and the stakeholders to determine the best way to deliver value.

Releasing an Increment to customers or users is not mandatory at the end of each Sprint. The Scrum Team may choose to release an Increment more or less frequently, depending on the product goals, market conditions, customer feedback, or technical feasibility. However, releasing an Increment regularly can provide many benefits, such as:

Validating assumptions and hypotheses about the product value and quality.

Obtaining feedback and data from real users and customers.

Increasing customer satisfaction and loyalty.

Reducing risks and uncertainties.

Improving transparency and collaboration.

 The Product Owner must spend enough time with the Developers so that they are confident the Increment will meet the intended value. This is because:

The Developers are accountable for creating a “Done” Increment in every Sprint. They must ensure that every Product Backlog item they work on meets the Definition of Done before it is considered complete.

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They must inspect the Increment at the end of each Sprint and assess how it delivers value and contributes to the Product Goal.

The Product Owner and the Developers must collaborate closely throughout the Sprint to ensure that they have a shared understanding of what they are building and why. The Product Owner must provide clarifications, feedback, and guidance to the Developers as needed to help them create a valuable Increment.

The amount of time that the Product Owner must spend with the Developers may vary depending on the context, complexity, and uncertainty of the product development. However, it should be enough so that both parties are confident that the Increment will meet the intended value.

Other options, such as 40%, as much time as the Developers tell them to be present, or 100%, are not valid answers as they imply a fixed or arbitrary amount of time that does not reflect the actual needs and dynamics of the product development.

The advantages of a Product Owner sharing a clearly defined Product Goal with the Scrum Team are:

It provides a good overall direction so Sprints will feel less like isolated pieces of work. The Product Goal is a long-term objective for the product that guides all the activities of the Scrum Team. It helps the Scrum Team align their efforts and focus on delivering value that contributes to the product vision.

It helps the Scrum Team keep focus and they can weigh any decision against the Product Goal. The Product Goal serves as a filter for deciding what to work on and what not to work on. It helps the Scrum Team prioritize and optimize their work based on value and impact.

It is easier to inspect incremental progress at the Sprint Review. The Sprint Review is an event where the Scrum Team and the stakeholders collaborate on the product and inspect how it meets the Product Goal. The Increment is a concrete and usable outcome of the Sprint that provides a measure of progress towards the Product Goal.

Other options, such as helping the Developers estimate the date that the Product Backlog will be complete or being not mandatory in Scrum, are not valid advantages of having a Product Goal. They may reflect a misunderstanding of what a Product Goal is or how Scrum works.

The best approach for Scrum Teams to produce valuable Increments is to be accountable for developing functionality from beginning to end, as this enables them to deliver potentially releasable products that meet the definition of “Done”. 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 This means that the Developers are not limited by the boundaries of components, layers, or technologies, but rather they collaborate and coordinate to deliver a complete and integrated product that satisfies the Sprint Goal and the Product Owner’s expectations.

1: The Scrum Guide2, page 7

2: The Scrum Guide

When multiple Scrum Teams are working on the same product, they should integrate their Increments every Sprint because:

It allows them to accurately inspect what is done and what is potentially releasable. By integrating their work frequently, they can ensure that the product is in a usable and valuable state at the end of each Sprint, and that it meets the Definition of Done and the Sprint Goal.

It enables them to adapt to changes and feedback faster. By integrating their work frequently, they can reduce the complexity and risk of integration, and discover and resolve any issues or dependencies sooner. They can also incorporate any new insights or requirements into their Product Backlog and Sprint Planning.

It fosters collaboration and alignment among the teams. By integrating their work frequently, they can share their learnings and best practices, and coordinate their efforts towards a common vision and goal. They can also leverage the collective intelligence and creativity of the teams to deliver a better product.

Developers are self-managing, which means that they decide how much work they can do in a Sprint, and how they will do it1. They manage the Sprint Backlog, which is the plan for how the Developers will achieve the Sprint Goal, and the single source of truth for the work to be done in the Sprint2. The Developers create and update the Sprint Backlog throughout the Sprint as more is learned[3][3] . The other options are not managed by the Developers, but by the Product Owner or the Scrum Team as a whole. The Product Owner is accountable for ordering the Product Backlog, which is an ordered list of everything that is known to be needed in the product4. The Product Owner also decides when to release the product, based on the value, risk, and stakeholder feedback5. The Scrum Team collaborates on inviting the stakeholders for the Sprint Review, which is an event where the Scrum Team and the stakeholders inspect the product Increment and adapt the Product Backlog. The Scrum Team also decides the Sprint length, which is the time-box within which the Scrum Team delivers a product Increment.

1: The Scrum Guide, November 2020, p. 6

2: The Scrum Guide, November 2020, p. 10

[3][3] : The Scrum Guide, November 2020, p. 10

4: The Scrum Guide, November 2020, p. 6

5: Managing Products with Agility, Scrum.org, accessed on December 16, 2023

 The Scrum Guide, November 2020, p. 13

 The Scrum Guide, November 2020, p. 9