PMP · Question #544
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 D. Validate the requirement change with the product owner and development team before redefining. When a customer proposes a requirement change in an agile project, the project manager must first validate it with the product owner and development team before proceeding with redefinition.
Question
In a frequently changing project, the project manager discovers a customer requirement change during a daily meeting. What should the project manager do?
Options
- AEscalate to management for approval since the change was not included in the original
- BTell the customer that the requirement change will be put into the next project phase if
- CGive the change to the scrum master to investigate how much additional effort the change will
- DValidate the requirement change with the product owner and development team before redefining
How the community answered
(43 responses)- A12% (5)
- B2% (1)
- C5% (2)
- D81% (35)
Why each option
When a customer proposes a requirement change in an agile project, the project manager must first validate it with the product owner and development team before proceeding with redefinition.
Escalating to management without prior team validation is a traditional approach that bypasses the agile team's role in self-organization and backlog management.
Arbitrarily delaying a customer requirement to the next phase without evaluating its priority or impact contradicts agile's emphasis on embracing change.
While the Scrum Master facilitates, the Product Owner, not the Scrum Master, is responsible for backlog changes and prioritization, and the development team estimates the effort.
In agile, the Product Owner is responsible for the product backlog and representing stakeholder needs, making their validation crucial. Involving the development team ensures the change's feasibility, effort estimation, and alignment with the team's capacity, embodying agile principles of collaboration and adaptive planning.
Concept tested: Agile change management and roles
Source: https://www.pmi.org/pmbok-guide-standards/agile
Topics
Community Discussion
3
Carlos M.Feb 15, 2026D is correct. Frequent changes means agile, and in agile you validate with the product owner and team before redefining scope. A and B are too waterfall, C just hands it off without PM involvement.
Mateus R.Feb 2, 2026D is right. Think restaurant owner tasting the soup before changing the recipe, the product owner validates first.
Wesley A.Feb 12, 2026Failed my first attempt partly because I picked A on a nearly identical question, thinking any change needed formal escalation. D is correct because in an Agile environment you validate the change with the product owner and team first before redefining the work.