What is in a project charter?

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Project charter" – news · newspapers · books · scholar · JSTOR (January 2021) (Learn how and when to remove this template message)

Table of Contents Show

Establishing authority
Table of contents
What is a project charter?
What does the project charter contain?
Main components of a project charter
Why are project charters useful?
Key sections of a project charter
One-page project charter example
Tips for writing a project charter
Next steps for your project charter

This article is written like a personal reflection, personal essay, or argumentative essay that states a Wikipedia editor's personal feelings or presents an original argument about a topic. Please help improve it by rewriting it in an encyclopedic style. (November 2021) (Learn how and when to remove this template message)

(Learn how and when to remove this template message)

In project management, a project charter, project definition, or project statement is a statement of the scope, objectives, and participants in a project. It provides a preliminary delineation of roles and responsibilities, outlines the project's key goals, identifies the main stakeholders, and defines the authority of the project manager.[1]

In Initiative for Policy Dialogue (IPD), this document is known as the project charter. In customer relationship management (CRM), it is known as the project definition report. Both IPD and CRM require this document as part of the project management process.

The project charter is usually a short document that explains a project clearly and concisely, and refers to more detailed documents for additional information.[2] A project charter should:

Identify the scope of the project.
Provide a shared understanding of the project objectives.
Act as a contract between the project sponsor, key stakeholders and the project team, detailing responsibilities.[3]

A project charter typically documents most of the following:[4][5]

Reasons for undertaking the project
Objectives and constraints of the project, including in-scope and out-of-scope items
Identities of the main stakeholders
Risks and issues (a risk management plan should be part of the overall project management plan)
Benefits of the project
High level budget and spending authority

Establishing authority

The project charter establishes the authority assigned to the project manager, especially in a matrix management environment.[6] It is considered industry best practice.

The three main uses of the project charter are:

To authorize the project - using a comparable format, projects can be ranked and authorized by Return on Investment.
Serves as the primary sales document for the project - ranking stakeholders have a 1-2 page summary to distribute, present, and keep handy for fending off other project or operations runs at project resources.
Serves as a focal point throughout the project. For example, it is a baseline that can be used in team meetings and in change control meetings to assist with scope management.

A project charter will be created in the initiating process group of a phase or a project at the very start. Developing the charter and identifying the stakeholders are the two main actions of the initiating process group. Typically a project manager takes the lead in developing the charter. The project manager will employ his or her expertise and experience to develop the charter. The project manager will work with the key stakeholders (customers and business sponsors), the PMO, Subject Matter Experts inside and outside the organization, other units within the organization and may also work with Industry groups or professional bodies to develop the charter. The project manager will employ facilitation techniques such as brainstorming, problem solving, conflict resolution, meetings, expectations management etc. to develop the charter.

Inputs to develop a charter can be:

Project Statement of Work
Business Case
Agreements
Assumptions
Enterprise standards, industry standards, regulations and norms
Organizational process, assets and templates

The charter once signed will provide authority to the project manager to officially execute the project and employ organizational funds and resources to make the project successful.

For a large multi-phased project, the charter can be created for each individual phase.[6] For example, there can be an initial charter during the Scope and Seek phase of a project, followed by a Planning charter and an Execution Charter during the build phase of the project.

Project scope

^ "The Concord Middle School Building Committee Report". The Concord Journal. Retrieved 24 December 2019.
^ Project-Management.com (2021-05-04). "What is a Project Charter?". Project-Management.com. Retrieved 2022-03-19.
^ Martins, Julia (5 April 2021). "3 Elements Every Project Charter Needs". Asana. Retrieved 2022-03-19.
^ "Project Charter". Adobe Workfront. Retrieved 2022-03-19.
^ "What Is a Project Charter in Project Management?". Wrike. Retrieved 2022-03-19.
^ a b Brown, Alex S. (2005). "The Charter: Selling Your Project". PMI Global Congress 2005. Project Management Institute.

Project Charter Template-WIKIVERSITY

Retrieved from "https://en.wikipedia.org/w/index.php?title=Project_charter&oldid=1078108175"

When you initially charter a plane, you don’t need to provide a seating chart or list of names to the airline company. But you need to know how many passengers you have, the cost of the trip, and your destination. The project charter is similar to that for your project.

What is a project charter?

A project charter is a short document that explains the project in clear, concise wording for high level management. Project charters outline the entirety of projects to help teams quickly understand the goals, tasks, timelines, and stakeholders. It is is an essential deliverable in any project and one of the first deliverables as prescribed by the PMBOK Guide and other best practice standards. The document provides key information about a project, and also provides approval to start the project. Therefore, it serves as a formal announcement that a new approved project is about to commence. Contained also in the project charter is the appointment of the project manager, the person who is overall responsible for the project.

What does the project charter contain?

When preparing the project charter, utilize the SMART method. Be Specific, ensure your goals are Measurable, Attainable, Relevant to the project, and Timely. The project charter includes:

Purpose and objectives of the project in clear, concise language
Requirements of the project at a very high level and without much detail
Project description in a paragraph or two that explains the project
Known high-level, major categories of risks for the project
Schedule of events with the start and end dates
Major events or milestones along the path.
Budget or summary of how much the project will cost
Requirements from the organization for approval, including what to approve, who will approve, and how to get the approval
Key players or stakeholders in charge of which parts of the project and who will approve the plans to go through
An introduction of the project manager, project sponsor, and their authority level

Read also: How to Write SMART Project Management Goals

Main components of a project charter

A project charter is a living document outlining the issues, targets and framework of a process improvement effort. A charter should have six main components that frame the document. Each of these component helps define the reasons for the project, explains how it improves the business, enumerate what steps are necessary to complete, and identifies the stakeholders responsible for the project. The project charter components are:

Problem statement
Business case
Goal statement
Timeline
Scope
Team members

Why are project charters useful?

The main reason every project needs a project charter at the very start is because without it, there is no proof or official document that an authorized project manager defined and presented a project and gained its approval from stakeholders to proceed. A project charter also provides several benefits:

Formally authorizes the project to commence
Creates a common vision and shared understanding of the project
Empowers the project manager to lead the project
Identifies the high-level objectives and scope of the project
Defines what success will look like at the end of the project
Gains support for the project by announcing it to the whole organization
Ensures that key stakeholders are aware of the project
Secures budget and resources for the project
Serves as the point of reference for the project team

Read also: Significance of Keeping Documentation in Project Management

Key sections of a project charter

Most project management methodologies and frameworks prescribe the use of a project charter but do not define the actual contents of the template. This is understandable, because projects differ in a variety of ways, such as in size, criticality, type, or approach. But the accepted principle in writing a project charter is that the document should help clarify the what, why, who, when, and what cost aspects or questions of the project. Referencing the PMBOK Guide, the inclusion of following sections in a project charter will answer these aspects and questions:

Project information

This section includes the name of the project, its ID (if organizations use one), the name of the project manager, and its sponsor(s). It can also include additional but brief project description details.

Business need, problem, or opportunity

This section tries to identify what the main driver for the project is for it to exist. It provides the context or situation that led the sponsor to start the project.

Project objectives and benefits

This lists the goals that the project will try to achieve. A guide for writing the objectives is to use the SMART acronym: they should be Specific, Measurable, Attainable, Realistic, and Time-bounded.

Project organization

This section identifies the people governing the project. It should clearly show the key roles for its management and direction. Using a RACI chart can be helpful.

High-level project scope

This section outlines the boundaries of the project at a high level. It is important to identify not only its scope, but also what is out of scope. Specifying key deliverables of the project should also fall in this section.

High-level project timescale

The project charter should list the key stages and the estimated duration of the project at a high level, including its milestones. However, the project manager should exercise caution in writing the project schedule, assuming that the project will immediately start after the approval.

High-level project budget

This section identifies the budget requirements of the project at a high level. It should include capital and revenue expenditure forecasts.

Key assumptions

This section lists the main assumptions that the project team took. It is important also to assess how these assumptions can impact the project should the team realize later that the assumptions they made were false or inaccurate.

Key project risks

This lists the main risks that may impact the project if they materialize. It assumes that the project team cannot avoid encountering the identified risks.

Success criteria

This section identifies the key metrics to help assess if the project is successful or not. The measurable terms describe an outcome that is acceptable to the end-user, customer, and stakeholders.

One-page project charter example

When creating a project charter, it is important to understand context. Project charters are usually very lengthy documents. This is to ensure that it completely describes the background of the project, the different options considered, the details of the scope, and other factors. For large projects, an additional one-page Project Charter Summary provides the summary of the most important sections of the full project charter. For small projects, this one-page template is an acceptable alternative. This short project charter is also useful when communicating with executives, who are usually not interested in all of the details and particulars. The sections of the document are as follows:

Project Name
Project Description
Target Date
Costs
Gains
Project Team
Key Milestones

Tips for writing a project charter

Writing effective project charters comes with experience. However, it is possible to write good enough ones early on by following some advice from professionals who have spent their careers learning how to write great project charters.

Keep it brief

Try to keep the project charter simple and brief. Most likely, the more pages it contains, the less chances it will get read.

Be explicit

Try to get to the point as early as possible. Project sponsors and other stakeholders are busy professionals who may not show interest or enthusiasm reading a vague summary of a project.

Build it with your sponsor

Most often, the sponsor hands it over to the project manager to write the project charter. However, the project charter is always better with the involvement of the sponsor, whether in support or actually co-creating and reviewing the document.

Next steps for your project charter

After creating the project charter, let the sponsor sign it without delay. Without the sign-off, there is no formal approval and authorization—and no project. Also, it is advisable to share the document promptly after approval. When more people in the organization know what the project is about, the easier it is to have supporters on board. Since the project charter is a key document in the initiation phase of a project, creating a great project charter lays the right foundation for the project and provides a greater chance it will proceed smoothly in its remaining phases.

A helpful tool in creating a project charter is project management software, which allows your team to analyze risks and choose appropriate stakeholders based on their existing resources and abilities. Project management tools also provide a view of the project’s timeline, each goal, and the progress team members make. Five of the best project management software listed below can make teams more aware of what exactly should be in each project charter.