Scrum Artefacts

Correct Answer: Product Backlog

The best way to manage stakeholder expectations is by adjusting the Product Backlog. This artifact holds the list of work the Development Team aims to accomplish, which can be prioritized and adjusted to meet stakeholder expectations more closely. The Definition of Done ensures that work meets a quality standard, but doesn't directly impact stakeholder expectations on product content. The Product Vision provides a long-term goal but doesn't offer the immediate adjustment tool for expectations. The Product Backlog Refinement process is a method to keep the Product Backlog up to date and in line with stakeholder needs, but it is the Backlog itself that should be adjusted to reflect work that will satisfy stakeholder expectations.

Correct Answer: Sprint Backlog

When unexpected issues arise during a Sprint, the Development Team needs to consult the Sprint Backlog to adjust their focus and plan for the rest of the Sprint. The Sprint Backlog is a dynamic artifact that provides a plan by the Development Team about what to work on next. On the other hand, the Definition of Done is a set of criteria that adds transparency and ensures that a Product Backlog item meets the necessary quality standards before it can be considered complete. The Daily Scrum is a daily meeting for the Development Team to plan work for the next 24 hours. The final incorrect option, while more detailed, relates to the Sprint Review, which is a time to inspect the Increment and adapt the Product Backlog if needed, not for adjusting the current Sprint's work.

Correct Answer: Work with the Scrum Team to refine and prioritize backlog items that will resolve the issue.

The correct approach for a Product Owner in addressing a recurring issue that affects the quality of Increments involves collaborating with the Scrum Team to understand the problem and together refine and prioritize backlog items that offer a solution. This ensures that the resolution aligns with the team's capabilities and the Product Goal. Assigning a fixed number of hours for addressing issues without considering the specific context of the work or consulting external experts without team input can lead to solutions that may not be feasible or effective. Recommencing the implementation of a new technology stack without assessing its impact disregards the value of empiricism and team collaboration, essential aspects of Scrum. The correct answer supports the principles of transparency, inspection, and adaptation, allowing for an informed decision-making process that involves the team who are most familiar with the work.