PMP Referenced Question 11: Handling New Requirements After Stakeholder Changes
This PMP-style scenario addresses how a project manager should respond when organizational changes result in new stakeholders and unexpected requirement requests mid-project. It tests your understanding of stakeholder engagement and change control.
📘 Scenario
Due to organizational changes, several key stakeholders are replaced by new ones in the middle of a project. As a result, numerous new requirements are raised.
❓ Question
What should the project manager do to ensure success of the project?
A. Review and prioritize new requirements with stakeholders to determine which change requests are needed.
B. Seek immediate approval to amend the project timeline and budget in order to deliver all new requirements.
C. Escalate the issue to the project sponsor and seek support to keep the original requirements.
D. Emphasize to the new stakeholders that new requirements are not allowed at this stage of the project.
⚠️ Disclaimer: This PMP-style question is presented for educational and commentary purposes only. It is not sourced from any official PMI exam and is not intended to violate any copyright. This content reflects interpretations based on the PMI mindset and principles, and is designed to help learners prepare for the PMP exam. If this question resembles real PMP exam content, it is coincidental and used solely under the doctrine of fair use for academic discussion. No claim of affiliation with or endorsement by PMI is made.
✅ Correct Answer: A. Review and prioritize new requirements with stakeholders to determine which change requests are needed
🔄 PMI promotes **continuous stakeholder engagement** — especially after organizational shifts.
📋 New requirements should be reviewed, prioritized, and formally processed through **change control**.
💡 This shows responsiveness while maintaining project governance and feasibility.
✔ Why Option A is Correct
Reviewing and prioritizing the new requirements allows the team and stakeholders to collaboratively decide which changes add value, which can wait, and which are not feasible. It keeps the project aligned with updated expectations and within manageable scope.
✖ Why Other Options Are Incorrect
B. Automatically approving all changes disrupts the schedule and budget without analysis.
C. Escalating too early limits collaboration and stakeholder trust — project managers are expected to handle such changes proactively first.
D. Flatly refusing new input violates the PMI principle of adaptive planning and stakeholder engagement.
📌 Key Takeaway
Stakeholder changes often introduce scope evolution. A successful project manager applies change control, prioritization, and stakeholder collaboration to align project outcomes with current business needs.
PMP candidates must understand how to respond to evolving stakeholder expectations mid-project. Engaging new stakeholders through prioritization and formal change management is key to maintaining project control and success.
PMP Referenced Question 22: Validating Budget Inputs for Analogous Estimation This PMP-style scenario focuses on avoiding estimation errors when using historical projects as a baseline. PMI...
PMP Referenced Question 21: Rebaselining a Delayed Project Through Change Control This PMP-style scenario focuses on how a project manager should respond when a project is...
PMP Referenced Question 20: Resolving Sprint Failures Caused by Scope Volatility This PMP-style scenario focuses on the project manager’s role in facilitating Agile collaboration and backlog...
PMP Referenced Question 19: Supporting Team Members Through Knowledge Gaps This PMP-style scenario tests how a project manager should respond to a team member’s performance issue...
PMP Referenced Question 18: Empowering Contractors Under Tight Project Deadlines This PMP-style scenario highlights best practices in empowering contracted teams during urgent rollouts. PMI encourages clear...