After several months the completion date is uncertain because scope keeps changing as new knowledge emerges, and new stakeholders claim outcomes don't meet business goals. How can the project manager prevent this in future projects?

The correct answer is to create a prioritized backlog and define iteration review sessions with stakeholders. This approach, characteristic of agile methodologies, directly addresses the problems of changing scope and unmet business goals. A prioritized backlog allows for continuous refinement and adaptation as new knowledge emerges, ensuring the most valuable items are always at the top. Regular iteration review sessions (e.g., sprint reviews) with stakeholders provide frequent opportunities for feedback, ensuring that the project outcomes align with their evolving needs and business goals. Developing a detailed WBS and milestone schedule (a predictive approach) is less effective here because the problem explicitly states that scope keeps changing due to new knowledge, making a fixed plan quickly obsolete. Holding daily meetings is for team coordination, not for managing scope or stakeholder alignment. Hosting kick-off meetings for each phase is a one-time event and doesn't provide the continuous feedback loop needed to adapt to ongoing changes.