Exam PMP topic 1 question 476 discussion

When new or conflicting requirements are discovered during Project Scope Management, and they differ from what is documented in the project charter, the project manager must follow the formal change control process. The project charter defines the original high-level scope. Any change to scope—especially if it deviates from what was initially approved—must go through integrated change control. This means documenting the change, assessing its impact, and submitting it to the Change Control Board (CCB) for approval before implementation. The configuration management plan is part of the project management plan that outlines how changes will be managed.

The PM should register the changes in the configuration management plan and send them to the CCB. This approach ensures that discrepancies are addressed through a formal change management process, maintaining project alignment and minimizing risks.

When new or different requirements emerge that deviate from the project charter or scope baseline, they represent a change in scope. According to standard project management practices (PMBOK), such changes must be: Documented properly, Evaluated for impact, Submitted through the change control process (typically involving the Change Control Board or CCB). The configuration management plan guides how changes are documented, tracked, and approved.

In Project Scope Management, when new or different requirements emerge that deviate from the project charter, the project manager must follow formal change control procedures. These procedures are usually outlined in the configuration management plan, which is part of the Project Management Plan. Any deviation from the original scope must go through the Change Control Board (CCB) for evaluation, approval, or rejection. This ensures that changes are properly assessed for their impact on scope, schedule, cost, and qualitY

A project manager has been assigned to a project and receives the project charter from the project management office (PMO). The document is very clear about customer requests. During Project Scope Management some requirements seem to be different from the ones specified within the project charter. What should the project manager do? A. Modify the baseline of the project for minor impact changes to the project scope B. Use a focus group and brainstorming sessions to gather more details about the project scope C. Register the changes in the configuration management plan and send it to the change control board (CCB) D. Explain to the sponsor that these requests could endanger the schedule and cost of the project

The project charter defines the high-level project scope, but detailed scope requirements may evolve during the project. If new requirements differ from the charter, they should go through formal change control. The configuration management plan ensures that all changes are documented, evaluated, and approved before implementation. This aligns with PMBOK’s "Perform Integrated Change Control" process. PMBOK Key Processes Referenced: Perform Integrated Change Control (Managing Changes to Scope, Schedule, and Cost) Configuration Management Plan (Ensuring All Changes Are Documented and Controlled) Validate Scope (Ensuring Deliverables Meet Approved Requirements)

When the project scope differs from what is defined in the project charter, it represents a potential change to the baseline of the project.

Next action

Must change request first and then proceed to the next steps accordingly such as brainstorming etc

Key is that this questions is for change management related, so choose C.

C. Register the changes in the configuration management plan and send it to the change control board (CCB). When there are differences or changes in project requirements that deviate from the project charter, it is important to follow the change control process. This involves documenting the changes in a configuration management plan and submitting them to the change control board (CCB) for review and approval. This ensures that changes are properly evaluated, and their impact on the project scope, schedule, and cost are assessed before any modifications are made. Option C aligns with the standard project management practice of formalizing and managing changes through a change control process.

When there's a discrepancy between the requirements specified in the project charter and the ones emerging during Project Scope Management, it's crucial for the project manager to gain clarity. Option B suggests using a focus group and brainstorming sessions to gather more details about the project scope.

C. Register the changes in the configuration management plan and send it to the change control board (CCB)

Project scope management is a process that helps in determining and documenting the list of all the project goals, tasks, deliverables, deadlines, and budgets as a part of the planning process. In project management, it is common for a big project to have modifications along the way. With the scope in the project management defined right in the beginning, it becomes much easier for project teams to manage and make the required changes.

B first, then D Brainstorm first, then explain

We should read the question very carefully. It said 'During project scope management' so the project is in execution stage, the scope has been baselined so B is not correct. the PM noted the requirements are not as the same as mentioned in project charter (High level). it intend to confuse you. He noted 'difference' means new requirements. when there is request, we have to perform integrated analysis on the change request impacts on schedule and cost and notified to the stakeholders. so D is the correct answer

Changing to D as B mention focus groups which refer to SME. Cannot find the reason for the difference with SME. So possible solution as all remain void is D to inform the sponsor about the changes impact.