The Risks of the Project. Give a basic breakdown of the project life cycleand list the various stages that your project will go through. Provide a basic, but complete, glossary that defines special terms related to the project.
If certain resources will only be needed during specific phases of the project, make note of that as well. Project Background and History: In addition, if the project will require resources from other departments or groups, a representative from each of these divisions should be listed in the Approval section as well.
At a very high-level, the project charter should be able to outline the boundaries of the project, i. See link at end of article. This field indicates the major milestones the project aims to accomplish and the target completion date for each milestone.
Every project undertaken will result in a tangible or intangible outcome. Give any background information that will help explain how the project came to be. It is usually created collaboratively as a team and shared with stakeholders upon completion. It is a document that summarizes the key information about a project and that announces to the world, aka, your organization, that there is a new project on the block.
Ideally it should be pages. This field indicates the project manager who has the authority to execute the project.
The Description of the Project.
Make sure to include the objectives of each stage and why the stage is necessary. How will you measure this success?
For more in-depth information about what a project charter is, and why it is instrumental in project management, read the article What is a Project Charter. Every project charter should consist of at least three primary components: The duties, roles, and responsibilities of the project manager as well as all the team members should be included there so that everyone is clear on what they need to do to help in the completion of the project.
How will you measure this success? Why are you undertaking this project?
After all, it should capture key, high-level information! Without establishing things like: Explain why the project is needed. This field defines activities that are in scope of the project. Project Goals and Objectives: The Roles and Responsibilities of the Participants.
The Timeline and Participants of the Project. No Charter, no project. While most project management methods and frameworks prescribe the use of a project charter of some sort — either called one-pager, charter, or mandate - there is no defined composition for its template.
It can be used as a reference for the targets and goals of the projects through the objectives. This gives details on why the project is necessary.
The Project Charter is the key document in the Initiation phase of a project and is the first opportunity that the project manager has to build the right foundations for the project. This also includes any outcomes to be anticipated in terms of the performance of the team members.
See link at end of article. These names should also be included in the Project Approval section—see the next page of this guide for more details on that section of the project charter.
This section should list all of the names and roles of the major stakeholders along with their signatures, indicating that each of these individuals is satisfied with the details included in the project charter.
This would make it so that everyone in the team is aware when the project will begin, when it will end and all the deadlines in between. If applicable, include details of why existing tools or products are inadequate.
If you are aware of the milestones of your project, be sure to include them in this charter. An easy to use template for developing a project charter is available in the Project Managment Media Gallery.
So, what should you be sure to include in this form?A compendium of ready-made forms for managing every project in line with the latest PMBOK ® Guide—Fifth Edition Completely editable electronic versions of all the blank forms, in Microsoft Office–compatible format.
The Project Charter documents the formal conversation between the Project Sponsor and the Project Manager/Team, including identifying metrics of success for the project.
A project charter is a central document that defines the fundamental information about a project and is used to authorize it. In a nutshell, a charter provides a picture of where you are going, why you are going there, who will be impacted, the main risks involved, and who is going to help you.
A good project charter template should contain and provide a comprehensive summary of the essence of the project. It is meant to be a document of agreement between the major stakeholders, the sponsor of the project and the whole team.
A project charter is one of many project management forms used in the initiation and planning stages of project management—and one of the most crucial documents. Proper construction of a project charter can help ensure the success of any project and, likewise, taking shortcuts in the preparation of this all-important document can subject your project to numerous pitfalls and unnecessary hold-ups.
The PMBOK ® Guide, 3 d Edition defines a project charter as “a 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.” (PMI,) The key word in this definition is “authority.” It authorizes both the project and the project manager.Download