Project Charter

Project Charter

Below are the description of all the uses of the working document “Project Charter”:

“Project Charter” is an output for the process “Develop Project Charter”.
The project charter is the document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. It documents the business needs, assumptions, constraints, the understanding of the customer?s
needs and high-level requirements, and the new product, service, or result that it is intended to satisfy, such as:
– Project purpose or justification,
– Measurable project objectives and related success criteria,
– High-level requirements,
– Assumptions and constraints,
– High-level project description and boundaries,
– High-level risks,
– Summary milestone schedule,
– Summary budget,
– Stakeholder list, – Project approval requirements (i.e., what constitutes project success, who decides the project is
successful, and who signs off on the project),
– Assigned project manager, responsibility, and authority level, and – Name and authority of the sponsor or other person(s) authorizing the project charter.

“Project Charter” is an input for the process “Develop Project Management Plan”.
The size of the project charter varies depending on the complexity of the project and the information known at the time of its creation. At a minimum, the project charter should define the high-level boundaries of the project. The project manager uses the project charter as the starting point for initial planning throughout the Initiating Process Group.

“Project Charter” is an input for the process “Plan Scope Management”.
The project charter is used to provide the project context needed to plan the scope management processes. It provides the high-level project description and product characteristics from the project statement of work.

“Project Charter” is an input for the process “Collect Requirements”.
The project charter is used to provide the high-level description of the product, service, or result of the project so that detailed requirements can be developed.

“Project Charter” is an input for the process “Define Scope”.
The project charter provides the high-level project description and product characteristics. It also contains project approval requirements. If a project charter is not used in the performing organization, then comparable information needs to be acquired or developed, and used as a basis for the detailed project scope statement. Organizations that do not produce a formal project charter will usually perform an informal analysis to identify the content necessary for further scope planning.

“Project Charter” is an input for the process “Plan Schedule Management”.
The project charter defines the summary milestone schedule and project approval requirements that will influence the management of the project schedule.

“Project Charter” is an input for the process “Plan cost management”.
The project charter provides the summary budget from which the detailed project costs are developed. The project charter also defines the project approval requirements that will influence the management of the project costs.

“Project Charter” is an input for the process “Plan Risk management”.
The project charter can provide various inputs such as high-level risks, high-level project descriptions, and high-level requirements.

“Project Charter” is an input for the process “Identify Stakeholders”.
The project charter can provide information about internal and external parties related with the project and affected by the result or the execution of the project, such as project sponsor(s), customers, team members, groups and departments participating in the project, and other people or organizations affected by the project.

This definition was found in the PMBOK V5

Go back to the Glossary or to the Mapping

Leave a Reply

Your email address will not be published.