Your software development project is following a predictive lifecycle with detailed upfront planning. You are currently in the execution phase, and the project is on schedule and within budget. A key stakeholder who was minimally involved during planning now requests a significant feature addition that would provide substantial business value but was not included in the original scope. The stakeholder insists this feature is critical and should be added immediately without formal approval processes. What is the most appropriate action?

Question

Accepted Answer

The correct answer is C. In a predictive project with an approved baseline, all scope changes must go through integrated change control (ECO Process Task 4.2 - Manage communications). This process evaluates the impact on scope, schedule, cost, quality, and other constraints before approval. Option C is correct because it maintains project governance while properly assessing the change. Option A violates change control procedures and could lead to scope creep. Option B is too rigid and doesn't consider that valid changes can be approved through proper channels. Option D assumes the change should be deferred without proper evaluation. The integrated change control process ensures that the change is documented, assessed for impacts, and decided upon by the appropriate authority, which protects project integrity while remaining responsive to legitimate business needs.

PMP Practice Question: Process — Predictive, Medium

More Process Questions