A project charter formally authorizes a project, describes its high-level purpose and boundaries, and establishes the project manager’s authority.
Key Points
- It should explain the need for the project
- Written by the sponsor and/or customer but in many cases, the Project Manager will write it
Input
- Authorized by the project sponsor or another person with the authority to commit organizational resources
- The charter documents high-level risk, project requirements, high-level milestones. It should not provide the specifics of project activities
- Resource allocation and high-level budget
Benefits of a Project Charter
- Projects should be approved based on the business case not just opinions
- The charter helps align stakeholders on the purpose, boundaries, and authority of the project
- The project must align with the company’s strategic plan; if utilized correctly, the details in the Charter can provide assurance that it does.
- Serves as a great tool to kick off the project meeting.
- Solidifies the Project’s purpose
Additional Information
Some additional questions that can be asked to make your Project Charter more effective:
- Has the need for the Project been examined? Do the benefits outweigh the costs?
- Does this Project tie to the Organization’s overall goals?
- Is the scope clearly defined?
- Are the project goals realistic? Can they be attained?
- What do we risk by not undertaking this Project?
- Are the outcomes of the project measurable?
- Do we have resources available?
Many projects forgo writing a Project Charter primarily because they do not see the need for one or do not know how to write one. In NYIM’s Introduction to Project Management, our class will guide you on how to assemble a Project Charter and ensure you have all the right information.