The very first deliverable of a Project! A Project Charter is one of the most important documents and one that gives the Authority to the Project Manager. The primary purpose of a project charter is to Authorize the project manager to start the approved project and allow him to use organizational resources to accomplish the objectives of the project. Here we look at a Perfect example of a Project Charter with a Template
Here is a checklist of sections that you should expect and fill under a Project Charter Example Template.
Stakeholders identification is the first step in the Project Management Processes for many organizations. Under our Project Charter example template also this comes right at the top!!!
A Project Charter should have a detailed list of all stakeholders, Project Champions or Approvers, Sponsors, Project Manager and all other teams involved
A well defined Problem Statement helps the Project Manager to drive the Project in the right direction and gives purpose to the Project Team. There is no doubt this is an important aspect on the Project Charter Example Template!!
This section represents the problem that a Project Manager intends to resolve by the end of Project Completion.
We often get our Problem Statements incorrect. Sometimes they are more of Goal Statements and sometimes they are found mentioning the scope . Here is a brief overview of what needs to be included
A problem Statement should mention the following:
What is wrong or what outcome is not satisfactory?
- A clear description of the problem or concern
- The issue should be verifiable/ measurable fact; not a guess or assumptions
- Examples: Procurement Cycle time is high; Billing Accuracy is low etc
This section is often missed or not filled completely by the Project Managers and it is one of the most important sections on the Project Charter Example!!!
The criteria that not only defines what criteria will be used to term the project as success but also provides a direction for the Project Manager to consider the project as completed and clears roadblocks for his exit from the project
Scope refers to a detailed set of Deliverables for the project. It is with this section that the project manager defined boundaries for the Project team to comply with. The work that needs to be accomplished to deliver a product, service, or result with the specified features and functions. This section of the Project Charter also defines deliverables that would be considered out of scope for the project
Outlines the high level Budget available for the Project or the Program. This is where the Project Manager needs to anticipate and call out the travel requirements, IT, Facilities, Hiring, Procurement and any other costs associated with the Project. This is where the Project Manager needs to don a business analyst’s hat and integrate all the costs anticipated and keep reporting with any changes because of environment. Resource costs are managed very closely in some organizations and drive the hiring decisions.
This is where the charter outlines Frequency of Project Meetings and Agenda to drive those meetings. The Communication Plan is next big thing on Project Manager’s agenda after identification of stakeholders. This is where the PM answers the question on how he is going to engage stakeholders on his project. Remember the 4th Project Management Mistake is not Engaging Stakeholders enough!!! You may want to set up separate calls for departments driving some action items for you!!!
Milestones are critical activities or High Level Activities represented in a tabular format. Reporting consistent progress on milestone helps give traction to the project and also gives leadership teams a view on the status and stage of a project
High Level Risks that could impact the project are to be mentioned in the Charter.
Once the Project Manager has developed the High Level Plan he will have an understanding of the Critical Path for the Project. Critical Path Tasks like Hiring, IT Infra Set Up, Vendor Onboarding, Training will always be on the risk register and may be tracked as part of the charter.
Refer our article on Critical Path Method for understanding this aspect
Apart from this, the PM may want to consider appending standard risks like low volume of tasks, speed of execution, learning curve oriented risks in the Risks section of the Project Charter
You also may want to refer our Article on Risk Management Strategies in case you are wondering how to handle these risks you have just identified.
- It is created based on a business need, and the document must explain that need.
- The sponsor or the initiator Approves the charter
- It names and authorizes the PM
- It should include a high-level milestone view of the project schedule
- It is a high-level document that does not include the project details. The specifics of project activities will be developed later.
- It includes the summary level preliminary project budget
- Will you remember SPSSBCMR? This is very much the secret sauce of a Project Charter
A Template you could use…..