Page 1 of 1

Fine line between proj managemnet plan/docs updates Vs Change Request

Posted: Sat Nov 17, 2018 8:35 pm
by PCS
Hi Manish,

Request clarification on fine line when PMBOK says in its process Outputs: proj man plan/docs updates in general and Change Requests in specific.

In some of the processes like planning process, in outputs it just says proj man plan/docs updates taken thru org. change control process which eventually results in CR.
On the contrary in other process like manage and control, it specifically mentions Change Request ?

Why is it so ?

Regards,
PCS.

Re: Fine line between proj managemnet plan/docs updates Vs Change Request

Posted: Mon Nov 19, 2018 10:48 am
by manishpn
PCS wrote:Hi Manish,

Request clarification on fine line when PMBOK says in its process Outputs: proj man plan/docs updates in general and Change Requests in specific.

In some of the processes like planning process, in outputs it just says proj man plan/docs updates taken thru org. change control process which eventually results in CR.

On the contrary in other process like manage and control, it specifically mentions Change Request ?

PMBOK is a bit unclear and loos in this context.
it says'Any change to the project management plan goes through the organization’s change control process via a change
request' but then it says 'PMP Components may require a change request for the project management plan
Also CRs are output to some of the non M and C process like 'Define Activities' 'Develop Schedule' 'Develop Team'
However the reason it is explicit in M and C processes is that we will usually need a CR when we are M and C process.

As I always say PMBOK is not the rule book, its a framework and should be looked into to clear the concepts, if it misses an input or output for a process which you think is important or you used in your work, it is ok, as long the use is justified and inline with the PM framework,


Why is it so ?

Regards,
PCS.

Re: Fine line between proj managemnet plan/docs updates Vs Change Request

Posted: Mon Nov 19, 2018 12:44 pm
by PCS
Thanks a lot Manish for the clarification. It makes sense.
I understand, CRs in define activity and develop schedules may be due to rolling wave planning used in WBS/Work Packages.

Re: Fine line between proj managemnet plan/docs updates Vs Change Request

Posted: Sat Nov 24, 2018 10:48 pm
by Adel_M
Hi,
Why is there NO “change requests” output in the process “10-2 Manage communications”, the process output includes: project plan updates and project documents updates and OPAs updates?

Re: Fine line between proj managemnet plan/docs updates Vs Change Request

Posted: Thu Nov 29, 2018 1:12 pm
by Agihan
manishpn wrote:
PCS wrote:Hi Manish,

Request clarification on fine line when PMBOK says in its process Outputs: proj man plan/docs updates in general and Change Requests in specific.

In some of the processes like planning process, in outputs it just says proj man plan/docs updates taken thru org. change control process which eventually results in CR.

On the contrary in other process like manage and control, it specifically mentions Change Request ?

PMBOK is a bit unclear and loos in this context.
it says'Any change to the project management plan goes through the organization’s change control process via a change
request' but then it says 'PMP Components may require a change request for the project management plan
Also CRs are output to some of the non M and C process like 'Define Activities' 'Develop Schedule' 'Develop Team'
However the reason it is explicit in M and C processes is that we will usually need a CR when we are M and C process.

As I always say PMBOK is not the rule book, its a framework and should be looked into to clear the concepts, if it misses an input or output for a process which you think is important or you used in your work, it is ok, as long the use is justified and inline with the PM framework,


Why is it so ?

Regards,
PCS.
Thank you for this answer! I had the same question!