PMPRocket
PMP Practice QuestionsScope and Change Control
Process Domain

Scope and Change Control PMP Practice Questions

Test yourself with 16 free, scenario-based PMP practice questions on scope and change control, drawn from the Process domain of the exam and aligned to PMBOK 8. Work through each scenario before revealing the answer — every question includes an explanation of why the correct choice is right. For randomized, interactive practice across all topics, use the practice question tool.

Study first: how to answer PMP situational questions

Question 1 of 16

A project team member implemented a technical improvement directly in production without raising a change request, arguing it was a minor fix. The change later caused a system outage. What process failed?

  1. A.Risk identification — the risk of introducing unauthorized changes was not formally identified, logged, and mitigated through the project's risk management process.
  2. B.Quality assurance — the fix was not tested adequately before deployment, allowing it to pass through without detection in the project's quality assurance process.
  3. C.Scope management — the hotfix added functionality outside the approved scope baseline, violating the project's defined boundaries without authorization from the change process.
  4. D.Integrated change control — all changes must be formally requested, evaluated, and approved before implementation.
Show answer and explanation

Correct answer: D

Integrated change control requires that all changes — regardless of perceived size — go through a formal request, impact assessment, and approval process. The team member bypassed this process entirely. While quality assurance and risk identification may also have gaps, the root cause is the absence of change governance.

Question 2 of 16

A change request has been approved by the Change Control Board (CCB). What should the project manager do IMMEDIATELY after CCB approval?

  1. A.Implement the change and then update the documentation
  2. B.Notify the project sponsor that a change has been approved
  3. C.Issue a change order to the vendor responsible for implementing the change
  4. D.Update the project management plan and relevant baselines to reflect the approved change
Show answer and explanation

Correct answer: D

After CCB approval, the project manager must update the project management plan — including affected baselines (scope, schedule, cost) — before implementation begins. Updated baselines provide the new performance measurement target. Implementing before updating means the team will be working against an outdated plan. Sponsor notification may be appropriate but is not the immediate priority if the sponsor was part of or informed by the CCB. Vendor change orders are specific to procurement situations.

Question 3 of 16

A project manager notices that multiple team members have been implementing small 'improvements' without formal change requests, each justifying them as 'too small to require approval.' The project is now over budget and behind schedule. What is this an example of?

  1. A.Scope creep — unauthorized incremental changes accumulating without impact analysis or approval
  2. B.Continuous improvement — a sign the team is proactively enhancing quality
  3. C.Progressive elaboration — the team is refining scope as the project progresses
  4. D.Fast-tracking — activities are being enhanced in parallel
Show answer and explanation

Correct answer: A

Scope creep is the uncontrolled expansion of project scope through unauthorized changes, each individually seeming minor but collectively having significant impact on schedule and cost. The absence of integrated change control allows these additions to accumulate without proper impact assessment. Progressive elaboration refers to iteratively refining plans with better information — it is a legitimate and planned process. The described scenario is a textbook case of scope creep.

Question 4 of 16

On a hybrid project, an agile team member argues that since agile welcomes change, no formal change request should be required for backlog additions. What is the CORRECT position?

  1. A.The team member is correct — all agile changes are automatically approved through the product owner's backlog authority, which eliminates the need for any formal change control process in hybrid environments.
  2. B.Agile teams welcome changes to requirements within the agile framework, but changes affecting project budget, schedule constraints, or governance boundaries still require formal change control.
  3. C.Hybrid projects must route every backlog addition through a formal change request — applying consistent change control across all components prevents governance gaps that could affect budget and schedule accountability.
  4. D.The product owner can approve all changes without CCB involvement — as the backlog owner, the product owner has organizational authority to accept any scope modification affecting their product's development.
Show answer and explanation

Correct answer: B

Agile's principle of welcoming change applies within the iterative delivery framework — backlog refinement and sprint planning handle this organically. However, on hybrid projects, changes that impact funding, contractual commitments, regulatory requirements, or approved project baselines still require formal integrated change control. The distinction is between changes managed within the agile framework (stories, priorities) vs. changes that affect the project's governance boundaries (budget, timeline, contractual scope).

Question 5 of 16

A project manager receives a change request that was verbally approved by the sponsor in a hallway conversation. The CCB has not reviewed it. What should the project manager do?

  1. A.Implement the change immediately — verbal direction from the project sponsor is organizationally authoritative, and requesting formal documentation delays a decision that has already been approved.
  2. B.Reject the change entirely since verbal approvals are not formally valid — only written CCB approvals are recognized under the project's governance procedures.
  3. C.Document the change formally and process it through the CCB before implementation, even if the sponsor already gave verbal approval.
  4. D.Implement the change immediately and submit a retroactive change request after completion — acting on sponsor direction demonstrates responsiveness, with documentation following the delivery.
Show answer and explanation

Correct answer: C

Integrated change control requires all changes to be formally documented and reviewed regardless of verbal approvals. Even if the sponsor has authority, bypassing the CCB means the impact on scope, schedule, cost, quality, and risk has not been formally assessed. The project manager should document the request, process it through the CCB, and only implement after formal approval. Retroactive submissions after implementation defeat the purpose of change control — impact analysis must precede implementation.

Question 6 of 16

Which of the following are valid outputs of the Perform Integrated Change Control process? (Select THREE)

Select all that apply.

  1. A.Change log updates
  2. B.Rejected change requests with documented rationale
  3. C.Approved change requests
  4. D.Work performance data from the change review
  5. E.Risk register
Show answer and explanation

Correct answers: A and B and C

Perform Integrated Change Control produces approved change requests, which are formally authorized for implementation, plus updates to the change log that record every request and its disposition, including rejected change requests with their rationale. Project management plan updates are also an output when approved changes affect the plan, which is why the plan is not listed here as an option. Work performance data is an output of Direct and Manage Project Work, not of change control. The risk register is updated through risk processes.

Question 7 of 16

Midway through a sprint, a senior stakeholder asks two developers directly to build a new analytics dashboard, saying the release plan should simply absorb it. The sprint goal is already committed. What should the project manager do FIRST?

  1. A.Let the developers start the dashboard now, treating the senior stakeholder's request as the kind of change that agile teams are expected to welcome.
  2. B.Guide the stakeholder to the product owner so the dashboard is captured in the product backlog and ranked against the current release goals.
  3. C.Analyze the dashboard's effort with the two developers and fit it into the current sprint if it turns out to be small enough.
  4. D.Have the product owner add the dashboard to the current sprint and handle the senior stakeholder's request right away.
Show answer and explanation

Correct answer: B

In an agile project, new requests are welcomed but flow through the product owner, who owns the product backlog and its priorities. Steering the stakeholder to the product owner protects the committed sprint goal while making sure the dashboard is evaluated for value against the release goals. Letting developers start now bypasses prioritization and disrupts the sprint. Analyzing the effort with the two developers in order to fit the dashboard into the sprint leaves a prioritization decision with the wrong people, and asking the product owner to push the dashboard into the current sprint involves the right role but breaks the committed sprint goal before the dashboard's value has been weighed.

Question 8 of 16

During execution of a predictive project, a customer asks the project manager to add end-user training materials. The project charter and scope statement explicitly list training as excluded. What should the project manager do FIRST?

  1. A.Remind the customer that the approved charter excludes training and close the request as out of scope for this project.
  2. B.Have the technical writer start drafting the end-user training materials during slack time and show the customer early progress.
  3. C.Submit a change request to the change control board right away asking it to approve the training materials.
  4. D.Document the training request and analyze its impact on scope, schedule, cost, and resources for the change control board.
Show answer and explanation

Correct answer: D

An explicit exclusion can still be changed, but only through integrated change control. The project manager should first capture the request and analyze its impact on the baselines so the change control board can make an informed decision. Closing the request outright ignores that customers can legitimately ask for changes. Having the technical writer start drafting is unauthorized work that creates scope creep. Submitting a change request right away uses the right process but skips the impact analysis, leaving the board without the information it needs to decide.

Question 9 of 16

At the final design review of a hybrid project, the sponsor asks for a new interface to an external billing system. The design is about to be baselined so the build iterations can start next week. What should the project manager do FIRST?

  1. A.Assess the billing interface's impact on design, build plan, cost, and risk, and present it to the sponsor as a change request.
  2. B.Update the design to include the billing interface before sign-off, accepting the sponsor's request as approved scope from the project's funder.
  3. C.Sign off the design as planned and tell the sponsor the billing interface can be scheduled for a later phase of the project.
  4. D.Have the architects sketch the billing interface informally this week and show it to the sponsor before any paperwork is raised.
Show answer and explanation

Correct answer: A

Even a sponsor's request should be evaluated before it changes the design that is about to be baselined. Analyzing the impact of the billing interface and presenting it as a change request lets the sponsor decide with full knowledge of the trade-offs. Updating the design before sign-off assumes approval and skips impact analysis. Signing off and deferring the interface decides on the sponsor's behalf without analysis. Informal sketches may help later, but they consume effort on unapproved work before the impact is understood.

Question 10 of 16

During a sprint review, an operations lead says data migration from the legacy system was assumed to be part of the product. Migration does not appear in the product vision, the backlog, or the definition of done. What should the project manager do FIRST?

  1. A.Request that the product owner add data migration stories to the next sprint to meet the operations lead's go-live expectations.
  2. B.Inform the operations lead that migration is out of scope, given that it is not documented in the backlog, the vision, or the definition of done.
  3. C.Ask the product owner to meet the operations lead and clarify whether migration is needed and how the expectation arose.
  4. D.Raise a change request for data migration, estimate its effort, and seek the sponsor's approval for the additional budget.
Show answer and explanation

Correct answer: C

This is an unclear scope expectation rather than a submitted change, so the first step is to clarify it. Having the product owner meet the operations lead surfaces whether migration is actually needed and why the assumption was made, and the product owner can then decide whether to add it to the backlog. Requesting that the product owner add migration stories to the next sprint involves the right role but skips confirming whether migration is needed at all. Declaring it out of scope because it is undocumented ignores a possibly real need. Raising a change request and seeking the sponsor's budget approval jumps ahead before anyone has confirmed what is required.

Question 11 of 16

Two weeks before a fixed go-live date on a predictive project, the customer's product manager asks to add a low-priority export feature. The scope baseline is approved. The project manager has analyzed the request: adding the export feature would push go-live by about a week and require another full regression cycle. What should the project manager do NEXT?

  1. A.Add the export feature to the release anyway, given its low priority and the developers' estimate of only a couple of days of coding.
  2. B.Submit a change request for the export feature, with the go-live and regression impact, to the change control board for a decision.
  3. C.Have the test lead re-evaluate the regression scope with the developers to see whether a shorter test cycle is possible.
  4. D.Log a change request and tell the customer the export feature is deferred to the first scheduled release after the go-live date.
Show answer and explanation

Correct answer: B

The impact analysis is already done, so the next step in integrated change control is to give the change control board a change request backed by that analysis. The board, not the project manager, decides whether a one-week slip and another regression cycle are worth a low-priority feature. Adding the feature anyway because the coding looks small ignores the schedule and testing impact that the analysis just revealed. Having the test lead re-evaluate the regression scope repeats work that is already complete and delays the decision. Logging a change request while announcing a deferral decides the outcome before the board has reviewed it.

Question 12 of 16

A department manager asks the project manager to slip a custom departmental KPI report into the current increment of a hybrid project. The increment backlog was agreed at increment planning and the report is not in it. How should the project manager BEST respond?

  1. A.Refer the department manager to the product owner so the report is added to the product backlog and ranked against other work.
  2. B.Swap the custom report in for a lower-value story in the current increment, keeping the total effort for the increment the same.
  3. C.Schedule the custom report as team overtime work, leaving the agreed increment commitments unaffected.
  4. D.Decline the request and tell the department manager to submit the report through the annual reporting budget cycle instead.
Show answer and explanation

Correct answer: A

In a hybrid project, the increment backlog agreed at planning should stay stable, and new items go to the product owner for prioritization. Referring the request to the product owner gets the report captured and ranked by the product owner against other work without disturbing the current increment. Swapping stories mid-increment is not the project manager's decision and disrupts the team's commitment. Using overtime hides the cost and is unsustainable. Sending the manager to an unrelated budget cycle dismisses a request that may have real value.

Question 13 of 16

A regulatory reviewer informs an agile team that the product must log every access to patient records to meet a new rule. After confirming the rule with the regulatory reviewer, the team estimates the access logging work at about two sprints, which puts the planned release date at risk. What should the project manager do NEXT?

  1. A.Place the logging stories at the bottom of the backlog as an outside reviewer's input rather than a product owner request.
  2. B.Stop the current sprint and redirect the whole team to the access logging work until the new rule is satisfied.
  3. C.Escalate to the sponsor to request funding for an additional sprint so the original release scope and date can both be kept.
  4. D.Work with the product owner to rank the logging stories at the top of the backlog and share the revised release forecast.
Show answer and explanation

Correct answer: D

The rule is confirmed and the work is estimated, so the next step is to have the product owner prioritize the mandatory logging stories and make the effect on the release visible. Ranking the stories at the top of the backlog and sharing the revised forecast lets stakeholders plan around the new date. Placing the stories at the bottom treats a compliance obligation as optional. Stopping the current sprint discards committed work when re-prioritizing the backlog for the next sprint is enough. Escalating to the sponsor for an extra sprint asks for resources to protect the original date before the product owner has re-planned around the mandatory work.

Question 14 of 16

During user acceptance testing on a predictive project, business users keep raising requests for minor enhancements such as new filters and color changes. Sign-off is due in one week. What is the BEST way for the project manager to handle these requests?

  1. A.Implement the small enhancements quickly to keep the business users satisfied and willing to sign off before the deadline.
  2. B.Pause acceptance testing until every enhancement request has been reviewed and decided by the change control board.
  3. C.Review acceptance criteria with the users, separate defects from enhancements, and log enhancements as change requests.
  4. D.Reject all the enhancement requests and insist that the users sign off on the deliverables exactly as originally specified.
Show answer and explanation

Correct answer: C

Acceptance testing verifies deliverables against the agreed acceptance criteria, so the project manager should first clarify that purpose with the users. Separating real defects from enhancements lets defects be fixed while enhancements go through change control as change requests. Implementing enhancements to win sign-off is scope creep. Pausing testing for every request delays validation of work that is ready. Rejecting everything risks ignoring genuine defects and damages the relationship.

Question 15 of 16

In a hybrid project, the project manager notices that a developer has begun building an extra search feature that is not in the scope or backlog because the developer believes users will love it. What should the project manager do FIRST?

  1. A.Propose that the product owner accept the search feature into the current iteration, given that the developer's work is underway.
  2. B.Talk privately with the developer about the cost of unapproved work and route the idea to the product owner for evaluation.
  3. C.Record the incident in the issue log and report the behavior to the developer's functional manager for formal follow-up.
  4. D.Submit a change request to add the search feature retroactively and let the developer continue while it is reviewed.
Show answer and explanation

Correct answer: B

Building features outside the approved scope is gold plating, which adds unvalidated cost, risk, and testing effort. A private conversation helps the developer understand why approved work comes first, while the idea is still captured for the product owner to evaluate. Proposing that the product owner accept the feature because work is underway rewards gold plating and lets sunk effort drive priorities. Reporting the developer to a functional manager escalates before the project manager has coached the developer directly. Submitting a change request while the developer keeps building still spends effort on unapproved work.

Question 16 of 16

On an agile project with a time-and-materials contract, the client's representative emails the team saying "go ahead with the extra reporting work." No backlog items, acceptance criteria, or contract update exist for this work. What is the MOST appropriate response from the project manager?

  1. A.Work with the product owner to capture the reporting work as backlog items and confirm the approval through the contract process.
  2. B.Start the reporting work in the current sprint, treating the written approval from the client's representative as sufficient authorization.
  3. C.Ignore the email and wait until the client submits a formal change request for the reporting work through its procurement office.
  4. D.Forward the email to the team and have them evaluate the reporting work at the next sprint planning meeting.
Show answer and explanation

Correct answer: A

An informal email shows intent but does not replace the agreed way of authorizing work, so the approval needs to be formalized. Capturing the work as backlog items with the product owner and confirming it through the contract process makes scope, priority, and cost explicit. Starting the work now relies on an informal approval and disrupts the sprint. Ignoring the email is unresponsive to a client who clearly wants the work. Having the team evaluate the work at the next planning meeting is useful but premature until the work is defined and authorized.

Ready for exam conditions?

Practice these questions with randomized answer order and instant scoring, or take a full domain-weighted mock exam with a real exam timer.

More Process practice questions