Project Management

Please login or join to subscribe to this thread

Handling change questions on PMP exam

linkedin twitter facebook  
avatar
Mohit Joshi Germantown, Tn, United States
Hi All,

I have a topic that continues to bring some confusion for the PMP certification exam (I have it scheduled next week). It's handling change.

As I do the practice tests and review the explanation, I get different correct answers to the situation, making it difficult to understand - what's the right way to answer "what do to next/first".

Sharing a couple of examples:

1. If there is a change which is business critical & urgent - should the PM first assess the impact or inform the stakeholders or submit the change via CCB or implement the change first & then submit the change request for documentation?

2. If there is an issue that would result in the project objectives no longer feasible to achieve - should the PM first update issue log or inform the stakeholders or work with team for a solution or submit a change to revise the baselines?

I guess the main factor is how to handle the situation if a change is needed & is business critical/urgent/due to law or regulations v/s something that needs assessment before an action can be taken?

Some answers state that you should always assess the impact of a change first. Others state, first always update the project documents. Another explanation states the correct thing to do is to inform the impact stakeholders first. What is right?

Any help to clarify & understand this would be appreciated.

Thanks,
Mohit
Sort By:
< 1 2 >
avatar
Stéphane Parent Self Employed / Semi-retired| Leader Maker Prince Edward Island, Canada
Apr 24, 2020 2:17 PM
Replying to Mohit Joshi
...
Quick additional question: If a requested/identified change doesn't impact the baselines (of scope, cost or schedule), does it still need to have a change request approval from CCB or can it be implemented directly? I believe it would still a change request to be documented but no CCB approval.

In relation to the above, I understand that an update to a team charter, issue log, change log, risk register etc. doesn't need a change request...is that correct?

Thanks.
I have had change requests to capture documentation-only changes. In my case, we were changing names of milestones reported on the project dashboard. We wanted to have the paperwork that showed why it was changed. We only sought the project director and project sponsor approvals, not the whole CCB.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"It is better to have a permanent income than to be fascinating."

- Oscar Wilde

ADVERTISEMENT

Sponsors