Product Owner

Correct Answer: Assess the impact on the product goal and adapt the Product Backlog accordingly

As a Product Owner, the primary focus should be on assessing the impact of the technical issue on the product goal and adapting the Product Backlog accordingly. The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. If a technical issue requires a change in the backlog, it's essential to evaluate how this change affects the overall product goal and make necessary adjustments to ensure the team is working on the most valuable items. The other options, such as instructing the team to find a workaround, making decisions based on stakeholder preferences, or encouraging changes without updating the backlog, do not prioritize the product goal and may lead to misalignment or a lack of transparency.

Correct Answer: Gather feedback and collaborate with stakeholders on the product increment

The main objective of the Sprint Review is to gather feedback and collaborate with stakeholders on the product increment. The Scrum Team presents the work completed during the Sprint to the stakeholders, who provide feedback and insights. This feedback helps guide future development and adaptations to the product backlog. Presenting a detailed project status report or seeking approval are not the primary goals of the Sprint Review. The Sprint Review is not used to plan the next Sprint's goals and backlog priorities, as that is done during the Sprint Planning event.

Correct Answer: Validate feedback against product vision and roadmap for prioritization.

In the context of Scrum and Agile methodologies, the Product Owner is responsible for maximizing the value of the product resulting from the work of the Development Team. When faced with mixed feedback from various stakeholders on the prioritization of a new feature, the Product Owner should primarily validate the feedback against the product vision and the roadmap. This ensures that any action taken aligns with the long-term goals and strategies set for the product, maintaining a clear direction and focus. Prioritizing feedback based on the influence of the stakeholder could lead to biased decisions that might not serve the product's best interest. While involving the development team to assess technical feasibility is important, it should not be the sole basis for prioritization before considering the product vision and roadmap. Conducting a survey to decide democratically might seem fair but can dilute the product vision with too many conflicting interests, making it hard to achieve a coherent product strategy. Hence, the best approach is to align the feedback with the product vision and roadmap for prioritization, ensuring decisions are made in the best interest of the product's success.