Project Charters

Getting Your Project Off to a Good Start

You can use a Project Charter in discussions with your team, and other stakeholders.

You've just been appointed project manager for a new project. Senior managers have already signed off the project's business case, and you're busy recruiting your full-time project team.

You're also identifying a wider group of people in your organization from whom you'll need to get support for certain project tasks. Some of these people have already been involved in developing the business case, and some are completely new to the project.

As project manager, you'll often need to implement a business case that's already been approved. You'll have team members who have had different levels of involvement in the project so far. The problem is that some of these people may have different views of the project's goals, particularly if the project has been planned over a long period of time.

So, how can you get your team working in a positive and productive manner, and how can you make sure that everyone understands the goals of the project?

This where a Project Charter can help. In this article, we'll review the reasons you might use a Project Charter, and look at the main things that you'll need to include in one.

Why Use Project Charters?

Project Charters outline project goals, and give an overview of how projects will look and feel while you work on them. You can use Project Charters in discussions with project team members, governance groups, and other stakeholders – either individually or as part of workshops – as a way of ensuring that everyone understands the project's requirements.

Writing a Project Charter forces you to think through the project as a whole. You must understand all of the existing project documentation, consider how you want to approach implementing certain parts of the project, and identify the key points that everyone involved in the project needs to understand.

You can also use a Project Initiation Document (PID) instead of a Project Charter for these purposes as they are very similar documents. However, a Project Initiation Document is usually much more detailed. So a Project Charter is more suited to projects where you don't have the resources to write a detailed Project Initiation Document, or where you want to start work on the project quickly.

Tip:
The project management methodology that your organization uses may also determine whether you should use a Project Charter or a Project Initiation Document.

Format of a Project Charter

You can deliver your Project Charter as a report or a presentation.

In report format – Use this if the Project Charter must be self-explanatory. For example, you may want to use it as a team reference document, to provide a baseline of what you and your stakeholders require and expect from the project. You can then submit the Project Charter as part of the project approval process.
In presentation format – Use this if you'll present the Project Charter as part of a discussion. For example, you can use the charter to give a project overview to your team at a project meeting; or use it to brief your governance group and stakeholders at their first project meeting.

Contents of a Project Charter

The contents of each Project Charter are specific to the project, but they generally include the following:

... for the complete article:

Mind Tools Club members, click here.

Join the Mind Tools Club to finish this article AND get 1,000 more resources

Join now for just $1, first month

"When I started using Mind Tools, I was not in a supervisory position. Now I am. Along with that came a 12% increase in salary." – Pat Degan, Houston, USA

Add this article to My Learning Plan