How to Handle Scope Changes That Conflict with Strategic Goals
You are the project manager for a multinational corporation that is launching a new software product. The organization's strategic goal is to increase market share in emerging markets by 15% within the next two years. The project has completed the planning phase, and you are about to start execution. During a stakeholder meeting, the product owner insists on adding a feature that is popular in developed markets but has not been validated for emerging markets. The product owner argues that this feature will differentiate the product, but the development team estimates it will add three months to the schedule and increase costs by 20%. The sponsor is concerned about the budget and timeline. You have reviewed the business case, which does not mention this feature. What should you do?
Quick Answer
The correct approach is to conduct a cost-benefit analysis and assess alignment with the strategic goal, then recommend against the feature if it does not align, or submit a change request if it does. This is correct because the PMP framework requires that any scope change be evaluated against the business case and strategic objectives before altering the baseline; here, the feature conflicts with the goal of increasing market share in emerging markets and has not been validated for that audience, so a cost-benefit analysis would reveal whether it adds value or merely introduces risk. On the PMP exam, this scenario tests your ability to handle scope changes that conflict with strategic goals, often appearing as a trap where stakeholders push popular but misaligned features—common distractors include immediately rejecting the change or escalating without analysis. Remember the memory tip: “Align or decline—analyze first, then formalize.”
⚠ Common exam trap
Many candidates assume the product owner's authority is absolute (leading to Option B) or that escalation is the only path (Option A), without recognizing the project manager's duty to first analyze the change's strategic fit and then follow the formal change control process.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Conduct a cost-benefit analysis and assess alignment with the strategic goal. If it does not align, recommend against it and proceed with the original scope. If it aligns, submit a change request.
It follows the PMI framework for managing scope changes: first, evaluate the proposed feature against the business case and strategic goal (increasing market share in emerging markets by 15% within two years). A cost-benefit analysis will determine if the feature delivers value in the target market; if not, the recommendation is to proceed with the original scope. If it does align, a formal change request is required to adjust the baseline schedule and budget, ensuring the sponsor and other stakeholders can make an informed decision.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Escalate the issue to the project sponsor and ask for a decision.
Why it's wrong here
Escalation is premature without first evaluating the impact and alignment.
- ✗
Accept the feature because the product owner is responsible for the product vision.
Why it's wrong here
The product owner's vision must still align with the business case and strategic goals.
- ✗
Add the feature to the backlog and proceed as requested to satisfy the product owner.
Why it's wrong here
This bypasses change control and may harm strategic goals.
- ✓
Conduct a cost-benefit analysis and assess alignment with the strategic goal. If it does not align, recommend against it and proceed with the original scope. If it aligns, submit a change request.
Why this is correct
This approach ensures the feature is evaluated for value and follows proper change management.
Go deeper
Related to this question
About these practice questions
One of 800 original PMP practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on PMP
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. An organization is transitioning from a traditional waterfall approach to agile. The project manager is tasked with leading a pilot agile project. During sprint planning, the product owner prioritizes features based on stakeholder feedback. However, the team is concerned that the prioritized features do not align with the organization's strategic goals. What should the project manager do?
medium- A.Request a change to the project charter
- ✓ B.Facilitate a meeting with the product owner and key stakeholders to realign priorities
- C.Tell the team to trust the product owner's decisions
- D.Escalate the issue to the project sponsor
Why B: The project manager's role in an agile transition includes ensuring alignment between the sprint backlog and the organization's strategic goals. By facilitating a meeting with the product owner and key stakeholders, the PM enables a collaborative re-prioritization that respects both stakeholder feedback and strategic objectives, which is a core agile principle of continuous stakeholder engagement.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PMP practice question is part of Courseiva's free PMI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PMP exam.