As a servant leader on an agile pilot, after three sprints the team demos and main stakeholders give negative feedback even though the features met the product owner's acceptance criteria. The team is confused. How should the project manager mitigate the product rejection?

Engaging main stakeholders in upcoming sprint review sessions is the most effective approach. This allows for direct feedback and collaboration, ensuring their expectations are understood and incorporated early, preventing future rejections. The sprint review is specifically designed for stakeholder feedback and adaptation. Sharing the product backlog in advance is helpful for transparency but doesn't guarantee understanding or acceptance of the implemented features. Creating dedicated sprints for fixes addresses the symptom, not the root cause, and can lead to wasted effort if stakeholder needs aren't fully understood. Asking for a new product owner is an extreme measure that doesn't address the communication gap between the team and stakeholders.