I'm sure you are setting me up with a trick question here :-)
I'm a purist so I would say you have one charter - if there is the need to issue a new one, then that's a new project vs. a rewrite of the existing one. That is if the charter truly is a simple 1-2 page document which vests the PM with the authority to use organization resources and which clearly explains the purpose behind the investment.
In some companies, the term "charter" is used to refer to the PM Plan - I'm not a fan of that nomenclature...
Agree with Kiron, one project one charter. Some other documents are sometimes refer as Charter. Saving Changes...
Deepesh RammoorthyICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood ServiceTarneit, Vic, Australia
Yes I have seen examples of "Charter" being used in a different context
An example of a document that I have seen is called "Customer Charter" . This is an agreement with a customer that the organization will deliver a product or a service as per the business case outlined by the customer.
Then there is the Project Charter which authorizes the Project Manager and which was for the delivery of the project to satisfy the customer's business case. Saving Changes...
Anonymous
Dec 11, 2017 5:46 PM
Replying to Kiron Bondale
...
Mounir -
I'm sure you are setting me up with a trick question here :-)
I'm a purist so I would say you have one charter - if there is the need to issue a new one, then that's a new project vs. a rewrite of the existing one. That is if the charter truly is a simple 1-2 page document which vests the PM with the authority to use organization resources and which clearly explains the purpose behind the investment.
In some companies, the term "charter" is used to refer to the PM Plan - I'm not a fan of that nomenclature...
Kiron
LOL
Yes and you fell for it :) Saving Changes...
Rohit Kumar GoelCybersecurity | IT Consultant| Various ClientsDwarka, New Delhi, Delhi, India
I do agree with all replies to the post that there is only one charter per project that is created by the performing organisation to primarily assign the project manager formally to the project and authorise the project manager to commence the project work.
However, it is also a widely accepted truth that each organisation has some individuality in the way it does business and manage its affairs and as a result may chose to call some other documents having word ‘charter’ as a suffix as Deepesh had well shared a similar example about Customer Charter in his reply above. Saving Changes...
One. It is independent from the PLC. If there is a new charter, there is a new poject with different goals, business case and mission statement. Saving Changes...
Anonymous
All
Please read the question again.
Here is a hint- I am not asking about "Project Charter"
...
1 reply by Kiron Bondale
Dec 13, 2017 6:11 AM
Kiron Bondale
...
Mounir -
I have enough difficulty getting organizations to create a Project Charter, let alone team charters, or other variants! :-)
Product Operations Program ManagerBarcelona, Cataluña, Spain
Does the trick lay on the "life cycle", thus "project phases", thus one charter per each phase in project's life cycle? Saving Changes...
Anonymous
Dec 13, 2017 6:11 AM
Replying to Kiron Bondale
...
Mounir -
I have enough difficulty getting organizations to create a Project Charter, let alone team charters, or other variants! :-)
Kiron
Well think about this Kiron
The charter should be very short and brief --- it can even be an email or online approval. Also, think of the charter as an authorization document.
...
1 reply by Kiron Bondale
Dec 15, 2017 11:10 AM
Kiron Bondale
...
No argument from me - I've always been an advocate of short & sweet charters, but even that is perceived in some organizations as "too much paperwork".
Whenever I teach a PMP prep class and ask the students how many of their companies align with the principle that a project shouldn't exist without an approved charter, it's usually the minority who raise their hands...
Community Champion
