A project charter is designed to formally authorize the project and give the project manager authority to complete it. Regardless of the reason the project is started, every project should have a charter. The sections of the project charter can vary quite a bit because there are many types of projects.

Typically, a charter has the following types of sections.

1. Project title and purpose-What is the business challenge we are attempting to solve with technology? What are the business requirements we must meet. What will we call our project?

2. Project goal-Given the business need, what is the goal of our project?

3. Measurable objectives-What are our objectives in business terms? For example, do we want to increase revenues by 5%?

4. Vision or preliminary scope of the project-What tasks will the project accomplish?

5. Project constraints or assumptions-Are there business or technical constraints that will limit the project solution? For example, do we have to use existing customer information system resources or skill sets? Are we assuming this will be an Oracle solution? Do we have to be done by a certain date or within a certain budget?

6. Communication-Who are the project stakeholders, and how will we document project activities and communicate with them during the project? Who decides if the project is complete and approves the project?

7. Signature page-At a minimum, the charter should be signed by the sponsor and the project manager. Are there other key stakeholders that need to sign?

As you research your business and define the business needs, the sections of the charter will help you document your project.