In an agile environment, even a chaotic one, a release plan should focus on providing a high-level view of the product's objectives, the key features to be developed, and the iteration timelines. Including dependencies and specifying the responsible teams for each component ensures that expectations are set clearly for stakeholders while also providing the flexibility needed to adapt to changes. By outlining both the objectives and iteration details, the product owner ensures transparency and alignment with stakeholders while maintaining the iterative nature of agile development. This approach allows for informed decision-making without locking the team into overly rigid plans.

In Scrum, theproduct owneris the primary point of contact betweenstakeholders and the development team
. According to thePMI Agile Practice Guide (Section 3.3: Roles and Responsibilities), the Scrum Master ensures thatcommunications flow properlyand protects the team from distractions.
Mike Griffiths in thePMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement)emphasizes the importance of having asingle point of contactfor stakeholder feedback to avoid miscommunication and overload.
* Option Ais correct: redirecting communication through the product owner keeps the team focused and the backlog structured.
* Option Bis unprofessional and discourages stakeholder engagement.
* Option Cbypasses review and prioritization-backlog management should be intentional.
* Option Dcould blur roles and bypass proper channels.