Hi Omar,
Back in June, I sent the same PrepCast Simulator Question ID: 610083 to the Simulator HelpDesk via email:
support@pm-exam-simulator.com.
I hope the response below from
Stan Po, MBA, PMP, PMI-ACP, CSM, gives you PrepCast’s thought process on this particular scenario.
-Lisa
“As clarified in the explanation, our team had an extensive debate on the subject of change requests and the sequence of steps involved in this process. The reason being is that the PMBOK® Guide does not do a good job in explaining the exact process in detail. We have discussed the sequence of steps among our team of certified project management professionals and have concluded that the first thing that should be done when a change is requested on a project is the physical creation of the change request, a document if you wish, or in other words, filling out a form. Otherwise, on what basis would a project manager, the project team, the change control board (CCB) spend time evaluating a request that is not even documented? While the PMBOK® Guide does not explicitly specify the above sequence, it does imply that a change request should first be documented and only then evaluated. On page 120, the PMBOK® Guide reads, "Change control meetings are held with a change control board (CCB) that is responsible for meeting and reviewing the change requests and approving, rejecting, or deferring change requests. Most changes will have some sort of impact on time, cost, resources, or risks. Assessing the impact of the changes is an essential part of the meeting. Alternatives to the requested changes may also be discussed and proposed. Finally, the decision is communicated to the request owner or group." Therefore, the fact the CCB meets to review change requests and evaluate their impact on project constraints implies the change requests have already been submitted prior to the meeting.
Therefore, we still strongly believe that creating a change request is the 'first' step the project manager should take in this scenario.”