A company must launch a new product before the summer season. After discovery, the team finds the requirements are highly uncertain. What should the project manager do?

When requirements are highly uncertain, an agile approach is best. Proposing a Minimum Viable Product (MVP) allows the team to deliver core value quickly, gather feedback, and iteratively refine future increments. This approach embraces uncertainty by focusing on learning and adaptation. Requesting SMEs might help, but doesn't directly address the uncertainty in requirements or provide a path forward. Logging a risk and creating a contingency plan is a reactive measure for known risks, not a proactive strategy for high uncertainty in requirements. Inviting stakeholders to prioritize requirements is a good practice, but without further discovery or an iterative approach, it won't resolve high uncertainty.