A project manager on a cross-functional agile team has a software project with many features that will take about a year to complete. The CEO insists the solution must meet business goals by year-end in 6 months. How should the project manager align stakeholder needs and expectations?

The correct answer is to work with stakeholders to create a prioritized backlog and release a roadmap. In an agile environment with conflicting timelines and high expectations, prioritizing features and developing a realistic roadmap is crucial. This approach ensures that the most valuable features are delivered first, aligning with the CEO's goal of meeting business objectives by year-end, even if the full project takes longer. It manages expectations by showing what can be achieved within the shorter timeframe and what will follow. Reducing requirements to only those completable in 6 months might discard essential features needed for the business goals. Fast-tracking and crashing are traditional project management techniques less applicable to agile and might compromise quality or team well-being. Including all stakeholders in daily scrums would be inefficient and disruptive, as daily scrums are for the development team.