Yan WuTrainer/Consultant| Changeway Management Consulting Co., Ltd.Beijing, China, Mainland
When a project need to change it's charter, there's surely some process to deal with it. But that don't happen very often here in China.
So we need to figure out how it goes in real world and how we should tell trainees when asked during a PMP class.
My point is that, if you need to change your charter, you finish your current stage through 4.7 and review the charter through a new 4.1
Other trainer think that it might need to follow the change management plan or something in the charter, and conduct a 4.6 to decide.
Wanna know how you do this and how do you train this point in PMP. Saving Changes...
Eduardo Saravia NeyraElectronic Engineer| Compañía Latinoamericana de Radiodifusion SALima, Lima, Peru
When you are in the execution group, doing the work according to the plan if you want to do a change of the plan (scope, quality .. or add or change the requiriments) you have to follow the proccess of the Integrated Change Control.
First the PM Will understand the change that you want to do, knowing how it would affect the change in the Restrictions (scope, time, cost, quality..) then it would make the write the change request and sent it to the Integrated change control, whose decide to approve or deny the change. Saving Changes...
Ye Htet KyawAssociate Director| CBRE Inc.Yokohama, Kanto, Japan
As project charter is initially authorized by PM or Project sponsor, usually you need to seek top management engagement/meeting for a change as a PM. But first, make sure it's "actual change" necessary to change a project charter since eliminate/verify change at first sight is PM's responsibility. Then, you may bring up with your findings and solutions. Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Dear Yan
Interesting your question
Thanks for sharing
Is it important to change the charter or make changes to the project plan?
...
1 reply by Yan Wu
Dec 19, 2019 11:15 PM
Yan Wu
...
Well, Luis, I know that's charter changes don't happen all the time, but we do meet trainees discuss about the situation from time to time.
Saving Changes...
RAJON BANERJEEKalyani, District: Nadia, West Bengal, India
Hi Wu,
Branco has a very valid point.
Why you need to change charter? It's a very sensitive & top most important docs which describe business case & befit management plan. You can't change the charter as per PM. Because It's high level assumption & also the signatory authority. Even if PM also don't have the right to access & alter the same. Please make sure before doing that. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The project charter must not be changed. If you change the project charter then you are creating other project than the original.
...
1 reply by Yan Wu
Dec 19, 2019 11:20 PM
Yan Wu
...
Thanks for the clear point, Sergio.
Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Agree with Sergio. The project charter is owned by the sponsor not the project. It can be seen as a birth certificate which does not change even if you change your name or gender. It describes the project situation at one point in time and constitutes the baseline 0.
Any changes, even to parameters documented in the charter should be performed in the change management of the project.
If the change is so significant that it would alter the character of the project, one option is to close the project and create a new one.
There is a recent item in here that discusses the charter too. Saving Changes...
I'd support Sergio's view that that if your charter is a "true" charter, then it will be lightweight and contain specific information that, if changed, would represent a significant change to the purpose, expected benefits, scope or other aspects of the project.
As such, if there is a major change to the charter, you'd be better off closing out the current one and starting a new one.
If it is a minor tweak, then I'd question the value in updating the charter. Yes, you'd likely want to update requirements documentation, traceability matrices and so on, but the charter is not (usually) the starting point for traceability.
