If the Project Management Plan integrates and consolidates all these other subsidiary plans as recommended by the PMBOK, then why not should it yet be an input to those Plans?....
Lets constructively debate/discuss and challenge this theory by the following:
1. How would the integration be if the subsidiary plan were strictly inputs to the Project Management Plan?
2. That instead be the Project Charter that becomes the Input into the Plans processes
All the other processes of engaging the Project management plan for effecting changes or updates remains the same, despite the change of theory.
With this one is trying to challenge some issues of logic within the profession.
Your contributions will be much welcome.
Regards, Saving Changes...
Sort By:
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
One difference between Project Charter and Project Management Plan is that the Charter is never updated (in PMBoK). Some consider it to be the birth certificate of a project, and your birth certificate also is never updated.
Planning progress is reflected in the Project Management Plan (and maybe other documents), and hence it has to be input to planning processes to reflect the current status of the project.
Remember, planning is an iterative process (group), refining, detailing, updating the plans, in previous PMBoK editions, this was called progressive elaboration, an example was rolling wave planning.
...
1 reply by Dumisani Churchill Fulani
Apr 05, 2019 2:32 AM
Dumisani Churchill Fulani
...
I like the "Birth Certificate" analogy. avery good example for explaining to a layman indeed.
I'm not sure I completely understand your question but when drawing relationships between processes, there is often a double sided arrow, and which direction the arrow points is dependent on the context. For example:
A change process can alter a project management plan, therefor the PM plan is both an input the the change process prior to the change to the PM plan, and an output following the change execution.
In other contexts, the PM plan can alter the change process plan, such as when it is decided that the change process plan is deficient in some regard. In that context, the change process plan is both an input and an output to the PM plan, as the integrating plan may require changes to the subsidiary plan. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
A project plan is a document which is composed by all the other plans (subsidiary plans).
...
1 reply by Dumisani Churchill Fulani
Mar 24, 2019 10:22 AM
Dumisani Churchill Fulani
...
Thanks Mr Sergio
Im absolutely understanding your point, but now my question that of itself serving as an Input those subsidiary Plans. how about a Project Charter should have been subsituted in that regard. and then the logic could be, that a Project Management Plan cannot be amended without having initially amended those other subsidiary plans.
I hope you are getting my point.. lets analise this..
A project plan is a document which is composed by all the other plans (subsidiary plans).
Thanks Mr Sergio
Im absolutely understanding your point, but now my question that of itself serving as an Input those subsidiary Plans. how about a Project Charter should have been subsituted in that regard. and then the logic could be, that a Project Management Plan cannot be amended without having initially amended those other subsidiary plans.
I hope you are getting my point.. lets analise this..
...
1 reply by Sergio Luis Conte
Mar 24, 2019 6:55 PM
Sergio Luis Conte
...
Sorry, but I did not get your point.
Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Dumisani,
the Project Charter never changes. It represents the status of the project when it was authorized. Some call it a birth certificate.
The Project Management Plan is not a plan or document in itself but rather a composition of (subsidiary) plans, baselines and other documents.
If you see the Project Management as input to planning processes, it means that some of its components are inputs, and they may be further refined, developed and updated during the process. It was once called 'progressive elaboration' and 'rolling wave planning' is an example of it. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Mar 24, 2019 10:22 AM
Replying to Dumisani Churchill Fulani
...
Thanks Mr Sergio
Im absolutely understanding your point, but now my question that of itself serving as an Input those subsidiary Plans. how about a Project Charter should have been subsituted in that regard. and then the logic could be, that a Project Management Plan cannot be amended without having initially amended those other subsidiary plans.
I hope you are getting my point.. lets analise this..
Sorry, but I did not get your point. Saving Changes...
RAJESH K LProject Manager, PMP| Bharat Electronics, Bengaluru, IndiaBengaluru, Karnataka, India
Project Plan is a document which undergoes changes/modifications till the project closure happens formally. Saving Changes...
Certainly, the project plan can be an input to other plans. Our project plans typically have some over lap with the Project Charter, and subsidiary plans. For example, let's say that the project staff has changed and hiring/ staffing processes have changed. The Project Charter would be changed to reflect change in personal, project plan would be as changed as a result to reflect changes in roles and responsibilities. Project plan could make reference to the fact that hiring processes have changed, and for further details, reference the HR Staffing & Resource Management Plan. Saving Changes...
One difference between Project Charter and Project Management Plan is that the Charter is never updated (in PMBoK). Some consider it to be the birth certificate of a project, and your birth certificate also is never updated.
Planning progress is reflected in the Project Management Plan (and maybe other documents), and hence it has to be input to planning processes to reflect the current status of the project.
Remember, planning is an iterative process (group), refining, detailing, updating the plans, in previous PMBoK editions, this was called progressive elaboration, an example was rolling wave planning.
I like the "Birth Certificate" analogy. avery good example for explaining to a layman indeed.
Thanks very much for the contribution. Saving Changes...
