An organization is transitioning to agile delivery and is piloting the approach with a single project. The PMO manager asks how communications with the project team and stakeholders will be handled. What should the project lead recommend?

The correct answer balances formal reporting with agile transparency. Sending weekly reports to the PMO provides the necessary formal updates for organizational oversight, which is crucial during a transition. Using a Kanban board for the product owner and the project team ensures continuous visibility of work in progress, bottlenecks, and flow, fostering real-time collaboration and self-organization within the agile team. The other options are less effective: Sending weekly reports to the PMO and product owner, and using a Kanban board only for the project team, excludes the product owner from the primary agile communication tool, hindering their ability to prioritize and understand progress. Inviting the PMO manager to the daily standup can disrupt the team's focused, time-boxed event, as standups are primarily for the development team to synchronize and plan for the next 24 hours, not for external reporting. Sending weekly reports to all stakeholders, including the project team and product owner, creates unnecessary overhead and duplicates information that is better communicated through agile mechanisms for the team and product owner.