In a frequently changing project, the project manager discovers a customer requirement change during a daily meeting. What should the project manager do?

The correct answer is to validate the requirement change with the product owner and development team before changing the scope. In an agile or frequently changing environment, new requirements are common. The product owner represents the customer's voice and prioritizes changes, while the development team assesses feasibility and effort. This collaborative approach ensures the change aligns with project goals and is implementable before formally adjusting the scope. Escalating to management immediately is premature; the team needs to understand the change first. Deferring the change without assessment is not a proactive approach in a flexible environment. Asking only the scrum master to assess effort is insufficient; the entire development team's input is crucial for accurate estimation and commitment.