Project Charter Creation Template

Modify or delete all information colored grey. Be sure to change all text to black before printing or sending. A project charter serves several important functions. It organizes the project so that you can make efficient and effective resource allocation decisions. It also communicates important details on the project purpose, scope definition, and the project parameters. 1. Project Purpose This includes a list and description of the goals the project is expected to achieve and the strategy to be followed. Goals should be prioritized as high (H), medium (M), or low (L). This should also describe, in detail, the critical success factors that will ensure on time, on budget delivery.

Project Goals: Goal Objective 1 Objective 2 Objective 3 Objective 4 Objective 5 Priority H|M|L H|M|L H|M|L H|M|L H|M|L

Strategic Decision:

Critical Success Factors:

2. Scope Definition This section includes: Tasks that must be performed in order to successfully complete the project. Tasks that will not be addressed, and any projects or other initiatives that deal with them. Procedure for managing a change in scope.

Project Scope Is (Includes): These tasks are all within the scope of the project and will be resolved.

Project Scope Is Not (Excludes): These tasks are not within the scope of the project; these are the issues that the project does not deal with.

Scope Change Control Procedures: A definition of scope includes a strong change control procedure to manage scope creep. This section is arguably as important as defining the scope itself. 1. 2. 3. 4. 5.

3. Project Parameters. This section contains an exhaustive list of project planning boundaries. It includes the following: Project title: The project title or project name is often overlooked, but is a critical identity-building tool for the project team. The project title should describe the projects purpose, but also contain some reference to the company and/or project team.

Project timing. Although you may not know every date at this stage of the project, the start date or the end date are usually known. These can be critical to staffing the project and allocating resources. Start Date:

End Date:

Project Organization: This section describes who is doing what for the project. It includes a listing of each person involved and what role each will play. These roles include the following:

o o o o o

Project sponsor. This person (or persons) initiate(s) the project and are ultimately responsible for it. Usually, functional managers sponsor a project to achieve something in their department. Project manager. This person is responsible for implementing the project plan. Business unit representatives. These people represent their departments or business functions within the project team, and have authority from their departments to make decisions on their behalf. External resources. Certain consultants or key external service providers may need to be identified also, especially if you have an outsourced IT environment. Internal resources. Anyone else inside the company who is critical to project competition should be identified here, such as the Business Analyst, Requirements Analyst, etc. The amount of their time required (e.g. 10 hours per week) should also be highlighted. Internal hardware or software resources (e.g. for testing) should also be listed. Project Sponsor: Project Manager:

Business Unit Representative:

3

Business Unit Representative: Business Unit Representative: External Resources: Internal Resources: Communication Standards: This area highlights the reporting structure (who the reports will go to, the frequency of reporting, etc.), as well as the kind of reporting necessary. Certain templates used in taking minutes, producing reports, and recording test data, may also be listed here. 1. 2. 3. 4. 5.

Key Deliverables: Each deliverable does not necessarily have to be listed. The deliverables highlighted below are the ones key to project success, or have associated issues that need to be addressed at the start of the project. 1. 2. 3. 4. 5.

Milestones (Interim Deliverables): This includes any milestones (e.g. conducting all questionnaires) as well as major hurdles in deployment (e.g. redeployed staff). 1. 2.

3. 4. 5. Budget: This is the estimated amount of money and other resources (e.g. user time) required for the project. Total Cost: Total Time: Other Resources:

Info-Tech Research Group tools and template documents are provided for the free and unrestricted use of subscribers to Info-Tech Research Group services. These documents are intended to supply general information only, not specific professional or personal advice, and are not intended to be used as a substitute for any kind of professional advice. Use this document either in whole or in part as a basis and guide for document creation. To customize this document with corporate marks and titles, simply replace the Info-Tech Information in the Header and Footer fields of this document.