Please login or join to subscribe to this thread
The charter is not changed after project start. It is considered a birth certificate, which is not changed even if you change gender. The signature of the charter signals project start and initial authorization.
You are developing a project management plan including scope statement, budget, schedule etc. which reflect the latest approved status (including your change).
If the change is significant (e.g. from building a house to buying a car), you might consider closing the project and starting a new one.
If the project charter was not approved then the project does not exsts, there is nothing to start. That is the "as-is" by the book. In the real life you can face other situations. It will depend on your defined project management life cycle and governance process.
The project charter should not get into the details of project team composition. It's sole purpose is to act as a contract between parties, identifying what (at a very high level) is to be done and the associated price.
A Project Charter is not a contract as a contract is a legally binding agreement between two parties (normally buyer and seller).
Rather a Project Charter is an authorization that establishes the project under certain criteria and gives authority to the Project Manager to use resources and monies to complete the project.
Changes to a project (whether it be scope, schedule or cost) are managed through Change Control and cannot affect the overarching contours of the Project Charter.
Interesting your question
Thank you for formulating it
I agree with the views of Thomas Stéphane and James. These are complementary.
Sérgio's contribution is also very interesting because it bridges the gap between bay the book and reality
@Stéphane - yes, noted.
I guess this gets into semantics. I do not view a Project Charter as like a contract or acts as a contract. The use of the word 'contract' (to me) implies there could be action for recourse against one of the parties if terms/actions are not met.
For a Project Charter it may connote an agreement, but I see it as a declaration of intent as well as authorization that the PM is the person who is charged with delivering the business value under the contours of the project as described (high-level) in the Project Charter.
Anyway, perhaps I'm going too far astray!
Reading your message, you have resource change in your project, which you correctly managed through change management, having already approval. You need to document the change in the change log, and update resource plan.
Project charter - no need to update. A good practice is to have reference in the chapter to project plans / PMP - timeline, resource plan, etc. With this in mind, no need to change and sign the charter every time change occurs in PMP/ project plans. Changes of course are maintained through change management process.
Please login or join to reply