The sponsor of a newly formed agile project is unclear about scope and when key product features will be available. What should the project manager do?

The correct answer addresses the sponsor's lack of clarity regarding scope and feature availability, which are fundamental aspects of agile project planning. Establishing a project vision provides a high-level understanding of the product. Decomposing features into a backlog and prioritizing them clarifies the scope and order of work. Finally, creating an overall release plan directly addresses when key features will be available. Moving the Kanban board to a more visible location might improve communication but doesn't resolve the underlying issues of unclear scope and feature availability. Creating a detailed project management plan with all releases and tasks is more indicative of a predictive approach and might be too rigid for an agile project where scope evolves. Inviting the stakeholder to daily meetings provides visibility into daily progress but doesn't offer the strategic overview of scope and feature delivery that the sponsor needs.