Free Scrum PSPO-I Practice Exam with Questions & Answers | Set: 5

In Scrum, feedback loops are essential mechanisms that allow for inspection and adaptation at regular intervals. The three feedback loops from the options provided are:

Sprint Review (A): This is a feedback loop that occurs at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. It involves stakeholders and provides an opportunity to inspect the progress towards the Product Goal.

Daily Scrum ©: This is a daily feedback loop for the Developers to synchronize their work and plan for the next 24 hours. It helps in identifying challenges and creating a plan to achieve the Sprint Goal.

Sprint Retrospective (D): This feedback loop occurs after the Sprint Review and before the next Sprint Planning. It is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

The Refinement Meeting (B) is not considered a feedback loop but rather an ongoing process of adding details to Product Backlog items. Release Planning (E) is not a formal event in Scrum and thus not a prescribed feedback loop.

The Scrum Guide and the Professional Scrum Product Owner™ (PSPO I) materials describe these events as integral parts of the Scrum framework that serve as feedback loops1

The Developers are the people in the Scrum Team who are committed to creating any aspect of a usable Increment each Sprint. The Developers are accountable for organizing and managing their work.Only the Developers can decide how to perform the work during the Sprint1. The Developers plan the work necessary to create an Increment that meets the Definition of Done during the Sprint Planning event. This is often done by decomposing Product Backlog items into smaller work items of one day or less.How this is done is at the sole discretion of the Developers2.The Developers also inspect their progress toward the Sprint Goal and adapt their plan during the Daily Scrum1.The Developers are self-managing, which means they decide internally who does what, when, and how1. The Scrum Master, the Product Owner, the team manager, and the subject matter experts are not involved in determining how the work is performed during the Sprint.They may provide guidance, feedback, or support, but they do not interfere with the Developers’ autonomy and accountability134.References:

Scrum Guide

What is a Developer?

Who Determines How Work Is Performed During The Sprint?

What is Sprint Planning?

The Developers are the ones who are accountable for tracking the remaining work toward the Sprint Goal. The Developers are self-managing and decide how much work they can do in a Sprint1. They also create and update 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 use the Daily Scrum to inspect their progress toward the Sprint Goal and adapt the Sprint Backlog as necessary[3][3] . The Product Owner, the Scrum Master, and the Project Manager (if any) do not have the accountability for tracking the remaining work toward the Sprint Goal, as this is the responsibility of the Developers.

The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for creating and communicating a vision, ordering the Product Backlog, and ensuring that the best possible job is done to delight customers. The Developers are the people in the Scrum Team that are committed to delivering a “Done” Increment that meets the Definition of Done and the Sprint Goal. They are responsible for managing and organizing their work within the Sprint, collaborating with the Product Owner and the Scrum Master, and applying their skills and creativity to create a product that delivers value to the stakeholders and customers. A Project Manager is not a role in the Scrum Team, as Scrum does not recognize titles for Developers, regardless of the work being performed by the person. There is no need for a Project Manager, as the Scrum Team is self-managing and accountable for delivering value.

The Scrum Guide

The Scrum Team

Professional Scrum Product Owner™ I Certification

The Developers on the Scrum Team share accountability for the Sprint Backlog, which is a forecast of the work and the plan to deliver the Sprint Goal12. The Sprint Backlog is dynamic and can be updated by the Developers as more is learned during the Sprint34. The Developers are not individually accountable for the items in the Sprint Backlog, nor are they assigned by the Scrum Master or the Product Owner5.

 A Sprint may be cancelled when the Sprint Goal becomes obsolete. This is because:

The Sprint Goal is a short-term objective that provides guidance and focus to the Scrum Team throughout the Sprint. It is a flexible and negotiable commitment that can be adjusted as more is learned throughout the Sprint.

The Sprint is a container for all other Scrum events and activities. It is a time-box of one month or less during which a “Done” Increment is created that meets the Sprint Goal. The Sprint has a consistent duration throughout a development effort and only changes duration between Sprints.

A Sprint may be cancelled before it is over by the Product Owner if they determine that the Sprint Goal is no longer valid or valuable. This may happen due to various reasons, such as a significant change in the market, technology, business direction, or customer needs.

A cancelled Sprint should be rare and exceptional. It implies a waste of time and resources that could have been spent on delivering value. It also disrupts the rhythm and flow of the Scrum Team and the stakeholders.

When a Sprint is cancelled, any completed and “Done” Product Backlog items are reviewed and potentially released. Any incomplete Product Backlog items are re-estimated and put back on the Product Backlog. The Scrum Team then plans for a new Sprint.

Other options, such as when the Developers determine the product plan is infeasible, when it becomes clear that not everything will be finished by the end of the Sprint, or when the sales department has an important new opportunity, are not valid reasons for cancelling a Sprint. They may reflect a misunderstanding of what a Sprint Goal is or how Scrum works.

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 job of a Product Owner focuses on the following aspects:

Working with customers and stakeholders to identify the most valuable product requirements: The Product Owner engages in frequent and regular interactions with the people who have a stake or interest in the product, such as customers, users, sponsors, managers, or other teams. The Product Owner solicits and incorporates their input, feedback, and insights to understand their needs and expectations, discover new opportunities or ideas, align and collaborate on the product direction and priorities, and validate and deliver value to them. The Product Owner translates these requirements into Product Backlog items that can deliver value to customers or users.

Clearly communicating project or release status and strategies to customers and stakeholders: The Product Owner communicates effectively and transparently with the customers and stakeholders about the progress, outcomes, and plans of the product development. The Product Owner shares relevant information and data about the product vision, goals, value proposition, roadmap, backlog, increment, feedback, or metrics. The Product Owner also communicates the strategies and decisions for delivering value to customers or users, such as release frequency, scope, quality, or risk management.

The other options are not valid or relevant aspects of a Product Owner’s job. They are either too narrow, unrealistic, or unrelated to the product value delivery. They are:

Writing clear, transparent User Stories: This is not a valid aspect of a Product Owner’s job. User Stories are a common format for expressing product requirements in an agile way. They consist of a brief description of a feature or function from the perspective of a user or customer. They usually follow a template such as “As a < role > , I want < goal > , so that < benefit > ”. However, User Stories are not mandatory or universal in Scrum. The Product Owner can use any format or method to express product requirements, as long as they are clear, concise, and valuable. The format or method does not affect the value or quality of the product or service delivered.

Being with the Scrum Team all the time, just in case they need me to clarify a requirement: This is not a realistic aspect of a Product Owner’s job. The Product Owner does not have to be physically present with the Scrum Team all the time. The Product Owner can work remotely or asynchronously with the Scrum Team, as long as they maintain effective communication and collaboration. The Product Owner should also empower and trust the Developers to make technical decisions and trade-offs that best meet the product goals and quality standards. The Product Owner should also ensure that the Product Backlog items are sufficiently clear and refined before they are selected for a Sprint.

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.

To ensure that the product delivers value, a Scrum Product Owner might focus on the following aspects:

How much of the functionality of the product is being used: This is an indicator of how well the product meets or exceeds the needs and expectations of the customers and users. It can also reveal which features or functions are more or less valuable or useful for them. The Product Owner can use various methods or metrics to measure the usage of the product functionality, such as analytics, user behavior, retention, or engagement.

Direct customer feedback: This is a source of valuable input and insights from the people who use or benefit from the product. It can also help to validate or invalidate assumptions or hypotheses about the product value and quality. The Product Owner can use various methods or channels to collect and incorporate customer feedback, such as surveys, ratings, reviews, interviews, focus groups, or social media.

How quickly or easily the product can be absorbed and used by its customers: This is a measure of how well the product delivers value to customers or users in a timely and convenient manner. It can also affect customer satisfaction and loyalty. The Product Owner can use various methods or metrics to measure the ease of use or adoption of the product, such as time to value, learning curve, usability testing, or net promoter score (NPS).

The other options are not valid or relevant aspects that a Scrum Product Owner might focus on to ensure that the product delivers value. They are either too narrow, unrealistic, or unrelated to the product value delivery. They are:

Velocity is increasing over time: This is not a valid aspect that a Scrum Product Owner might focus on to ensure that the product delivers value. Velocity is a measure of how much work a Scrum Team can deliver in a Sprint. It is not a measure of value or quality. It is also not a goal or target for improvement. It is only a planning tool that helps the Scrum Team forecast their future work based on their past performance. Focusing on increasing velocity over time may lead to unrealistic expectations, pressure, or compromise on quality.

Minimizing changes to project scope: This is not a valid aspect that a Scrum Product Owner might focus on to ensure that the product delivers value. Scrum is an agile framework that embraces change as an opportunity for delivering more value to customers and users. Scrum does not have a fixed project scope, but rather an adaptive Product Backlog that evolves as the product and the market change. The Product Owner should welcome and respond to changes in customer needs and expectations, rather than resist or avoid them.

the Product Owner is responsible for refining the Product Backlog, which is an ongoing activity that can occur at any time, including between Sprints.The other options are not typical activities for the Product Owner between Sprints, as the next Sprint starts immediately after the current Sprint1, the project plan is replaced by the Product Backlog2, and the Quality Assurance is done by the Developers of the Scrum Team within the Sprint1.

1:The Scrum Guide | Scrum.org2:What is a Product Backlog? | Scrum.org