Short Explanation: According to the Scrum Guide 2020 1 , the product has one Product Backlog, which is the single source of work undertaken by the Scrum Team. The Product Backlog is ordered by the Product Owner, who is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
There should be only one Product Owner per product, who may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item's priority must address the Product Owner 1 . Having multiple Product Owners or Product Backlogs would create confusion, inconsistency, and waste in the Scrum process.

The correct answers are B and C, because technical debt impacts transparency in these ways. It leads to false assumptions about the current state of the system, specifically of an Increment being releasable at the end of a Sprint, as it may contain hidden defects or incomplete functionality. It also results in future work being slowed down in unpredictable ways, as development progresses and code is added, the system becomes more difficult to stabilize and maintain.

The correct answer is D, because the Scrum Guide states that "a Sprint is a container for all other events. Each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt." Therefore, a Sprint is over when its time-box expires, regardless of whether all Product Backlog items or tasks are completed or not.

Several Sprints into a project, a key stakeholder begins using the product and finds the quality lacking. The Product Owner (PO) agrees and shares this concern with the Scrum Master (SM). The Scrum Master needs to determine the best way to respond.
Scrum emphasizes empiricism , which is based on transparency, inspection, and adaptation . This means that if quality concerns arise, the Scrum Team must inspect the issue, adapt accordingly, and ensure quality is built into the product incrementally.
# A. Encourage the Product Owner to include quality specifications in the Product Backlog and to communicate the stakeholders ' concerns to the Developers.
# Reference from the Scrum Guide :
* " The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team. "
* " The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. "
# Why is this Correct?
* Since the Product Owner represents the stakeholders , they should translate the stakeholder's concerns into actionable Product Backlog Items (PBIs) that reflect quality improvements.
* Developers can refine and plan these PBIs in upcoming Sprints to ensure quality is systematically addressed.
* The Product Backlog is the single source of work , meaning all quality requirements should be made explicit there.
* This approach aligns with Scrum's empirical process of making work transparent so that the team can inspect and adapt.
# C. Work with the Product Owner to understand their desired resolution and help formulate an approach for raising the concern with the Developers.
# Reference from the Scrum Guide :
* " The Scrum Master serves the Product Owner in several ways, including: Helping find techniques for effective Product Goal definition and Product Backlog management. "
* " The Scrum Master serves the Scrum Team in several ways, including: Helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done. "
# Why is this Correct?
* The Scrum Master is a servant leader , responsible for facilitating collaboration between the Product Owner and Developers so that the concern is effectively addressed.
* Instead of dictating a solution, the Scrum Master guides discussions and enables the team to decide how best to improve quality.
* The Definition of Done (DoD) should be reviewed to ensure it is clear, measurable, and includes quality standards .
* This approach ensures that all stakeholders-Developers, Product Owner, and Scrum Master- collaborate in a self-managing way to improve quality.
Incorrect Answers with Explanations
# B. Bring the concern to the testers to improve how the Product is verified.
# Reference from the Scrum Guide :
* " Developers are always accountable for: Instilling quality by adhering to a Definition of Done. "
# Why is this Incorrect?
* Scrum does not have a separate testing team ; instead, the Developers are responsible for all aspects of quality (coding, testing, integration, etc.).
* Quality should not be " verified " by an external group; rather, it must be built into the Increment from the start .
* Instead of passing the issue to testers, the Scrum Team should improve their Definition of Done to ensure the product meets the necessary quality standards.
# D. Tell the Product Owner they have noted the concern and will raise this issue at the Sprint Retrospective.
# Reference from the Scrum Guide :
* " The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. "
# Why is this Incorrect?
* While the Sprint Retrospective is useful for discussing improvements , waiting until the Retrospective delays the resolution of a critical issue.
* The Scrum Team should act immediately by addressing quality issues in the Product Backlog and adapting their work in upcoming Sprints.
* Transparency and fast feedback are key principles in Scrum- delaying discussions goes against empiricism .
# E. Explain to the Product Owner that it is up to the Developers to decide on acceptable quality standards.
# Reference from the Scrum Guide :
* " The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. "
* " If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. "
# Why is this Incorrect?
* While the Developers are responsible for meeting the Definition of Done , quality is a shared responsibility across the Scrum Team .
* The Product Owner must ensure that the product delivers value to stakeholders , which includes meeting their quality expectations.
* Ignoring the Product Owner's concerns contradicts Scrum's emphasis on collaboration and transparency.

According to the Scrum Guide1, Scrum is not a process, technique, or definitive method. Rather, it is a framework within which you can employ various processes and techniques. Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment.