A project plan , according to the Project Management Body of Knowledge (PMBOK), is: "...a formal, approved document used to guide both project execution and project control . The primary uses of the project plan are to document planning assumptions and decisions, facilitate communication among project stakeholders , and document approved scope , cost, and schedule baselines . A project plan may be sumarized or detailed."
10-516: The latest edition of the PMBOK (v6) uses the term project charter to refer to the contract that the project sponsor and project manager use to agree on the initial vision of the project (scope, baseline, resources , objectives, etc.) at a high level. In the PMI methodology described in the PMBOK v5, the project charter and the project management plan are the two most important documents for describing
20-434: A "Team Charter" for the purpose of formalizing team roles and task structure at the outset of any team-oriented initiative. Teams that approach a task with a mindful design of team dynamics and task structure are more likely to be successful. The name of this document varies by institution. The Initiative for Policy Dialogue (IPD) refers to this document as the project charter. In customer relationship management (CRM), it
30-498: A project during the initiation and planning phases. PRINCE2 defines a project plan as: The project manager creates the project management plan following input from the project team and key project stakeholders. The plan should be agreed and approved by at least the project team and its key stakeholders. Many project management processes are mentioned in PMBOK® Guide, but determining which processes need to be used based on
40-470: 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
50-413: 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. A project charter should: A project charter typically documents most of the following: The project charter establishes
60-460: The PMBOK or PRINCE2, the project plan must also describe the execution, management and control of the project. This information can be provided by referencing other documents that will be produced, such as a procurement plan or construction plan, or it may be detailed in the project plan itself. The project plan typically covers topics used in the project execution system and includes the following main aspects: The project plan document may include
70-423: The authority assigned to the project manager, especially in a matrix management environment . It is considered industry best practice. The three main uses of the project charter are: 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
80-422: 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: 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
90-458: The following sections: Project charter 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 . More broadly, this document may be referred to as
100-407: The needs of the project which is called Tailoring is part of developing the project management plan. The objective of a project plan is to define the approach to be used by the project team to deliver the intended project management scope of the project. At a minimum, a project plan answers basic questions about the project: To be a complete project plan according to industry standards such as
#893106