PMP · Question #1370
Just as a team reaches a mutual consensus on a preferred design, a stakeholder submits a request to add new features that enhance the company's competitive advantage. What should the project manager d
The correct answer is A. Start the process to include the new features of the product on the next iteration.. When new feature requests arise after design consensus, the project manager should initiate the process to incorporate them in a future iteration.
Question
Options
- AStart the process to include the new features of the product on the next iteration.
- BAllow all requested changes and bypass the company's change control process.
- CReject all requested changes and bypass the company's change control process.
- DEncourage the project team to add premium features to impress the client.
How the community answered
(24 responses)- A79% (19)
- B13% (3)
- C4% (1)
- D4% (1)
Why each option
When new feature requests arise after design consensus, the project manager should initiate the process to incorporate them in a future iteration.
Project management best practices, especially in agile contexts, advocate for managing changes through a structured process, often by incorporating new features in subsequent iterations after proper review and planning. This approach ensures that valuable enhancements are considered without disrupting current work and allows for appropriate resource allocation and prioritization.
Bypassing the change control process can lead to uncontrolled scope creep, budget overruns, and project delays, negatively impacting project success.
Arbitrarily rejecting changes without evaluation ignores potential business value and stakeholder needs; all proposed changes should be evaluated via a controlled process.
Arbitrarily adding features to impress a client without proper analysis and formal change control can negatively impact the project's scope, schedule, and budget.
Concept tested: Change management in iterative projects
Source: https://learn.microsoft.com/en-us/azure/devops/boards/backlogs/manage-backlogs?view=azure-devops
Topics
Community Discussion
3
Prof. SaraMay 19, 2026A. In an adaptive environment, new features flow through the change control process by entering the backlog for evaluation and prioritization in the next iteration, which is exactly why A is the correct path. B and C both foolishly bypass change control, and D introduces unapproved gold plating that violates scope discipline.
Fatima Z.May 7, 2026I first leaned toward D because who doesnt want to dazzle the client, right? But D and B both skip the formal change control process, and C just shuts everything down, so A is the only path that actually funnels those shiny new features through proper iteration planning. Remember my CRISP hook for these: Consensus Reached, Iteration Scoops the Proposal, never bypass!
Zlatan X.May 1, 2026A is correct but the phrasing is clumsy with that "on the next iteration" tacked on. D is the trap because adding premium features sounds value driven, but without integrated change control you are introducing scope creep that undermines benefits realization across the program.