On the second day of a sprint standup, the product owner asks a developer to add more functionality to a product backlog item already committed to in sprint planning, claiming the change is critical for the next release. What should the project manager do?

The correct answer is to organize a workshop after the standup to assess the impact. The daily standup is for team synchronization and progress updates, not for introducing new requirements or detailed discussions. A workshop allows for a thorough analysis of the proposed change's impact on the current sprint goals, scope, schedule, and resources, involving relevant stakeholders. Asking for more details during the standup would disrupt its purpose and duration. Preparing a budget change request is premature without understanding the full impact. Creating a new product backlog item for the next sprint planning might be a solution, but only after the impact on the current sprint is understood and the change is properly prioritized and refined.