TOPIC: Impact estimate before submitting change request

I wonder if impact estimation for a proposed change is needed prior to submitting a change request.
PMBOK 6th Ed. page 115 mentioned impact estimates may be required prior to change request approval. But I cannot find whether the estimate is expected before or after change request submission.

Maybe I am not a 100% clear on the Integrated Change Control process flow.
Should a change request contain impact estimates and the options (what to do)? Then these information (including estimate and options) are reviewed and the change request is disposed based on the review?

Thanks!

Hi Vanlal,

In the exam setting, I recommend to follow this thought process when you encounter questions related to change requests:

1. Evaluate the impact
2. Identify options
3. Get the change request approved internally
4. Get customer buy-in (if required)

More info can be found in Rita's Exam Prep under Pg 161.

HI Vanlal,

PMBOK guide 6th edition page 117 stated that "Change requests that have an impact on the project baselines should normally include information about the cost of implementing the change, modifications in the scheduled dates, resource requirements, and risks", therefore, you need to have an estimated cost of the impact for each option and perhaps your rationale for choosing one option over the other.

Hope this helps.

Regards,
Cynthia

Thank you for responding, Joe, Cynthia.

I do not disagree with your points. But the following question from PM Prepcast mock test confused me a bit. Could you let me know your thoughts?
Hope it's alright to post a Prepcast question here.

Question ID 610083
During project planning, the project team rigorously defined the project scope. During project execution, a senior engineer calls the project manager and suggests a simpler and more efficient design which could benefit the project.

What should the project manager do next?
A. Nothing, no changes are needed since the project scope was rigorously defined
B. Discuss the change with the project sponsor
C. Evaluate impact of the proposed change on the project constraints ( I selected this option based on Rita's. But PM Prepcast's reasoning is that a change request must be submitted prior to the impact analysis.)
D. Ask that engineer submit a change request (This is the best answer, per PM Prepcast mock test. Referred PMBOK 6th Ed. page 115)

Hi Vanlal,

This would be my understanding to the question you posted:

The question did not mentioned anything about impact or project constraints, instead it mentioned a better design that could benefit the project. If the question mentioned, for example, a project constraint such as affecting project schedule, then answer C would have been a better answer.

Also, any stakeholder involved in the project can submit a change request. In this scenario, it is the senior engineer who suggested the better design and so the Project Manager can ask the engineer to submit a change request. This change request would have all the information on cost and how it could benefit the project.

Hope this helps.

Cynthia

Also about "impact analysis", I would think this step will take place in the M&C process group. Let me try and give you a scenario using the question by looking a little further.

Let's say, the CCB approved the change request, under the supervision of the senior engineer, the design team started executing the better design. Half way through the project, the senior engineer resigned and no one in the team is able to continue leading the better design. The project manager knows that this will impact the project schedule because it takes some time to find a replacement. Here, the project manager may conduct an analysis to determine how much this would affect the project, if it affects the baseline, then the project manager can submit a change request.

I hope my explanation helps.

Cynthia

Vanlal Peka wrote: Thank you for responding, Joe, Cynthia.

I do not disagree with your points. But the following question from PM Prepcast mock test confused me a bit. Could you let me know your thoughts?
Hope it's alright to post a Prepcast question here.

Question ID 610083
During project planning, the project team rigorously defined the project scope. During project execution, a senior engineer calls the project manager and suggests a simpler and more efficient design which could benefit the project.

What should the project manager do next?
A. Nothing, no changes are needed since the project scope was rigorously defined
B. Discuss the change with the project sponsor
C. Evaluate impact of the proposed change on the project constraints ( I selected this option based on Rita's. But PM Prepcast's reasoning is that a change request must be submitted prior to the impact analysis.)
D. Ask that engineer submit a change request (This is the best answer, per PM Prepcast mock test. Referred PMBOK 6th Ed. page 115)

Hi Vanlal,

Always remember to switch on the exam logic when writing the PMP exam.

In a real world setting, it is perfectly normal for my brain to start analyzing as soon as the senior engineer approaches me with the suggestion. However, in an exam setting, you only need to analysis the effect that the change makes after the change request has been made.

Therefore, both the answer C & D are correct, but D is a better answer because an impact analysis is only needed after a change request has been made.

Hope this helps,
Joe

Hello

I have developed a Change Management Flowcart based on Rita's book. Page 160-162. It might need some refinement but I think overall it is a good start to understand the activities before change requests/ during change request and outcomes that we expect.

Thank you for your inputs. It helped me get my head around this.

Looks like the keyword here is evaluate vs. identify.
So the sequence of events will be: identify the impact, submit change request, gather information and evaluate the impact, then review the change request.

Thanks this one confused me as well. So just to summarize and make sure I understand: the change request is the best answer because the change request already includes an analysis of impacts on the project constraints? If the question had mentioned concerns regarding the project constraints it would have been appropriate for the Project Manger in the scenario to do an impact analysis before the engineer submits the change request?

Hi Nathan,

I think the change request will be elaborated as it goes on i.e. it will begin with a 'skeleton' change request that has minimal information, which will be elaborated and reviewed.

In the question above, the change request will have something along the line of 'design change is needed to benefit the project'.

Should the question mention any impact on project constraints, the first step will still be logging a change request, which will later be assessed/evaluated/reviewed. The change request may contain suggested design changes and potential impact to the project constraints. Detailed impact analysis will be performed and updated/attached to the submitted change request. These information will be reviewed to dispose the change request.

I think the progression is similar to a risk entry in Risk Register. It starts with minimal information and potential solution/response.

References:
1. www.izenbridge.com/blog/integrated-chang...e-of-change-request/
2. greycampus.com/opencampus/project-management-professional/perform-integrated-change-control
3. Rita's page 161