Yasser KidwaiPM III| Boeing InternationalDelhi, Delhi, India
Hi, I had read somewhere that in a project if project charter is signed and a broad area of work is defined by it, then after that, any change request which is outside the scope of Charter should not be entertained. is it true?
If this is true then any scope which is outside PMP but within Project Charter is only to be sent to Change Control Board. Am I right? Saving Changes...
PARAG KANDEKARVP Operations| SoftNice IncAllentown, Pa, United States
Project charter being described and documented at high level may not be the right benchmark when we discuss Change Approval process. For change approval process "Scope Baseline" is considered as benchmark which consist of Project Scope statement (project scope, major deliverable, assumptions and constraints), WBS & WBS Dictionary.
If proposed change is not part of baseline then it is entertained as CHANGE. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Not true. The first thing to do when you start working inside an initiative is defining and communication the change management process. Because the amount of information you have into each stage of your initiative and because the Lehman´s Laws of change (is a must, everyone must read and understand it in my opinion) you ever have changes. Changes are allways welcome. The project manager is not the owner of changes. The project stakeholders are the owner of changes. Saving Changes...
The Sponsor signed off the Project Charter. The Sponsor also reviews the Project Management Plan and verify that the project scope defined in the project plan shall represent the requirements defined in the project charter. It's highly unlikely that the requirements defined in the Project Charter differ with the scope defined in the PMP. In any case, any changes to the project scope that affected the project charter (these are usually additional requirements) can still be included in the PMP if the PMP has not been signed off by the project stakeholders including the Sponsor, else it would have to go the Change Control Board for approval. Saving Changes...
Praveen MalikIndependent Consultant| Independent ConsultantNew Delhi, India
Main purpose of PC is to authorize the project and not scope definition. Usually, only high level of scope is defined in PC. PC does not replace PMP and it is also not complementary to PMP. PMP contains Scope Statement which completely describes & elaborates the high level scope defined in PC.
If any changes in Project Charter, it must be reviewed by Change Control Board for approval Saving Changes...
ABHAY MISHRATeam Leader| AECOM INDIA PVT. LTD.Patna, Bihar, India
If any changes in Project Charter, it must be reviewed by Change Control Board for approval. Let us consider two cases if the project is internal and change is within project charter it must be reviewed by the Change Control Board for approval. In second case of external project generally the RFP and other contract conditions serves the purpose of project charter and the contract documents authorize the sponsor to make addition or withdrawal of the scope and it is weel defined in the contract document.For exaple in a EPC contract generally it happens upto 10% of the contract value as a part of permissible change and beyond this figure by mutual consent if contracting party agrees.
Therefore we can conclude changes in Project Charter, it must be reviewed by Change Control Board for approval and all such changes have to fallow the procedure of change control process. Saving Changes...
ABHAY MISHRATeam Leader| AECOM INDIA PVT. LTD.Patna, Bihar, India
If any changes in Project Charter, it must be reviewed by Change Control Board for approval.
Let us consider two cases if the project is internal and change is within project charter it must be reviewed by the Change Control Board for approval.
In second case of external project generally the RFP and other contract conditions serves the purpose of project charter and the contract documents authorize the sponsor to make addition or withdrawal of the scope and it is well defined in the contract document.For example in a EPC contract generally it happens up to 10% of the contract value as a part of permissible change and beyond this figure by mutual consent if contracting party agrees.
Therefore we can conclude changes in Project Charter, it must be reviewed by Change Control Board for approval and all such changes have to fallow the procedure of change control process. Saving Changes...
ABHAY MISHRATeam Leader| AECOM INDIA PVT. LTD.Patna, Bihar, India
If any changes in Project Charter, it must be reviewed by Change Control Board for approval.
Let us consider two cases if the project is internal and change is within project charter it must be reviewed by the Change Control Board for approval.
In second case of external project generally the RFP and other contract conditions serves the purpose of project charter and the contract documents authorize the sponsor to make addition or withdrawal of the scope and it is well defined in the contract document.For example in a EPC contract generally it happens up to 10% of the contract value as a part of permissible change and beyond this figure by mutual consent if contracting party agrees.
Therefore we can conclude changes in Project Charter, it must be reviewed by Change Control Board for approval and all such changes have to fallow the procedure of change control process. Saving Changes...
I have a similar question to this thread.
Does a new Project Charter need to be written and signed if a role changes within the project? (such as the project manager leaves and is replaced by someone else) Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
I have answered this in other thread.
Is like any other change into any other project deliverable. It will be determined based on your project change management process. Project Charter is "the contract" between all project stakeholders, mainly key project stakeholders, then your project change management process will determine that after impact analysis how other things inside the project must be updated due to forward traceability. It could be a change into the document itself and in the extreme it could be the whole project must be killed. Saving Changes...
