Courseiva
Process — Managing Technical AspectsmediumMultiple ChoiceObjective-mapped

PMP Integrated Change Control Practice Question

You are a project manager overseeing a 12-month ERP implementation. During sprint 6 of 20, the product owner informs you that a key stakeholder wants to add a new reporting module that was not in the original scope. The team estimates this would add 3 weeks to the schedule. What should you do FIRST?

⚠ Common exam trap

Do not confuse agile backlog management with formal change control. Even in an agile context, if scope is formally agreed upon, any new feature that significantly impacts schedule requires a change request.

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

Submit a change request through the Integrated Change Control process and assess the impact on scope, schedule, and cost

According to PMI, any change to scope must go through the Integrated Change Control process. The project manager must first submit a change request to formally assess the impact on scope, schedule, and cost before obtaining approval. Option A is wrong because adding to the backlog without formal approval bypasses change control. Option B is wrong because starting work immediately violates the change control process. Option C is wrong because refusing changes outright without assessment is not appropriate; changes can be made through proper control.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Add the requirement to the product backlog and let the team address it in a future sprint without formal approval

    Why it's wrong here

    Adding work to the backlog without change control approval bypasses formal governance and violates the project management plan.

  • Ask the team to begin work on the module immediately to accommodate the stakeholder

    Why it's wrong here

    Beginning work immediately bypasses the formal change control process required by the PMBOK for scope changes that impact the schedule baseline. The project manager must first assess the change request through the integrated change control system, evaluating trade-offs against the triple constraint, before authorising any work. This option is tempting because it appears to satisfy a powerful stakeholder quickly, and it would be correct only if the project had a pre-approved contingency budget and a flexible schedule buffer explicitly designated for unplanned stakeholder requests.

  • Inform the stakeholder that no changes can be made once the project has started

    Why it's wrong here

    This is incorrect — changes can be made through the formal change control process. Refusing outright without assessment is not the PMI approach.

  • Submit a change request through the Integrated Change Control process and assess the impact on scope, schedule, and cost

    Why this is correct

    PMI requires all scope changes to go through Integrated Change Control. The PM must document, assess impact, and obtain approval before proceeding.

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 →

How Courseiva writes practice questions · Editorial policy

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.