Why "Reject Change Requests" is an Input to "Monitor & Control Proj Work Process

Submitted by mezzat on Sat, 06/20/2009 - 03:25

Dear PMPs,

 I am studying for the test and as I am looking for ITTOs for each process and trying to understanding the purpose of each one. I found that "Reject Change Requests" is an input to Monitor and Control project work process (Integration). Any idea why we need to feed a rejected change request as input to this process. Please advice.

 Thanks

Forums: 
PMP / CAPM exam Question bank
  • Log in to post comments
  • 2385 reads

BM

Tue, 06/23/2009 - 09:21

Hi There:

 You are right this is an input to M&C process group in 3rd edition of PMBOK guide but in the fourth version of PMBOK this is not there anymore, well with regards to third PMBOK, Rejected Change Requests act as in input because in the earlier process that is Direct and Manage Execution the outputs are Requested Changes, now in Monitor and Control, it may so happens that these Requested changes might got Rejected so to properly execute your Monitor and Control work you need the list of the Rejected Change Requests this is what I got from my teacher while I was studying for my PMP. Hope you would find this answer convincing incase should you need to get more information kindly revert...

 

Regards,

 

Bhupesh Mansukhani, PMP

admin's picture

admin

Sun, 08/28/2011 - 16:23

Its an old terminology but not totally out of scope .

One should know what CRs were rejected by CCB, all stakeholders should
be informed so that relevant actions can be taken. For Eg Rejected CRs
may be in scope for next project. Or if a CR is rejected a new CR may be raised by a stakeholder with reduced scope  or some modifications to original CR. Reject reason would be useful for the person who has raised the CR.