Custome
logo here
Project Name: Project Charte
Company
logo here
Project Name:
Project Charte
The blue-colored text passages within this document are tips and guidance for filling out
this template. If you are ready with your first draft, you should delete these passages before sending the document to your sponsor.
Project:
Project Name
Title:
Project Charte
Document number:
Version
0.1
Document status:
Draft
Author:
Doe, John
Responsible:
Date created:
dd.mm.yy
Protection class:
"For internal use only"
The Project and Author fields are filled automatically with the data from the document properties (File Properties). Once the appropriate entries have been made here, these fields can be updated with the "Update Field" function (can be found in the context menu for the individual fields).
Possible states for the document status include "Draft," "Released," and "Final." The status of the cu
ent document should be specified respectively in the field above.
Document history
Version
Date
Autho
Comment/Change
0.1
dd.mm.yy
Draft
The document history should provide an overview of the development of the document. Different versions with their date, author, and possible comments should be entered here.
Tips for Using This Template:
The Statement of Work (SOW) forms the basis for the project order. The project order represents a further level of detail. Information that is often only outlined roughly in the SOW has to be provided in greater detail in the project order. Furthermore, internal points can also often be listed in the project order, which are essential for project success.
The blue text contained in the template should provide assistance for usage. It
iefly describes how the individual elements and styles are to be understood.
Please delete all of the blue text before you disseminate or print the document; it is intended exclusively for internal use.
Page
1 Background/Project purpose or justification
2 Goals
2.1 Goals
2.2 Scheduling goals/milestones
3 Project product description
4 Delivery units
4.1 Delivery units/services
5 Project success criteria
6 High-level risks
7 Key stakeholders
8 Assumptions, restrictions and external dependencies
9 Responsibility of the customer
9.1 Tasks
9.2 Resources and staffing
10 Project category
11 Project budget (overview)
12 Project startup
13 Project end
13.1 Signatures for release
Annex
A. Glossary and a
eviations
B. References, accompanying documents
1
1. Background/Project Purpose or Justification
This section describes why the project was initiated and how significant it is for the company.
2 Goals
This section describes which goals are to be realized with the project. These goals serve as a point of reference for the project closing. Measurable goals should be defined.
2.1 Goals
Goal
Description
2.2 Scheduling Goals/Milestones
Schedule
Description
3 Project Product Description
This section describes the project end product to be supplied.
Product Scope Description
The product scope description documents the characteristics of the product, service, or results that the project will be undertaken to create. The description should also document the relationship between the products, services, or results being created and the business need that the project will address.
4 Delivery Units
A list of all project products/deliverables whose complete and satisfactory delivery indicate the completion of the project.
4.1 Delivery Units/Services
Delivery Unit
Description/Comment
A deliverable is any unique and verifiable product, result, or capability to perform a service that is required to be produced to complete a process, phase, or project. Deliverables are typically tangible components completed to meet the project objectives and can include elements of the project management plan. Deliverables also include ancillary results, such as project management reports and documentation. These deliverables may be described at a summary level or in great detail.
5 Project Success Criteria
This section outlines the quantifiable criteria that have to be fulfilled so that the project can be performed successfully.
Project Success Criteria
6 High-Level Risks
This section describes some of the key project risks and their potential impact on the success of the project. This list of risks should be regarded as provisional rather than complete because risks are usually identified and dealt with continuously during the course of the project.
Risk
Possible Impacts on the Project
7 Key Stakeholders
This section should at least contain the key stakeholders with their names and roles in the project context. This is your starting point for further stakeholder management and analysis.
Name
Role
8 Assumptions, Restrictions and External Dependencies
Assumptions are expectations that form the basis for decisions. This section lists the main assumptions on the basis of which appraisals, plans, and methods are defined for the project.
A
R
E
Item
A = Assumption
R = Restriction
E = External dependency
9 Responsibility of the Custome
This section lists what the customer is to contribute in the course of the project. These responsibilities can be split into two categories.
9.1 Tasks
Task
Comment
Contact
9.2 Resources and Staffing
Resources/Staffing
Comment
Contact
10 Project Category
According to the relevant requirements and experiences in the company, the project is classified based on the following predefined features.
Project Category
Project Categories:
C Projects:
B Projects:
A Projects:
Complexity
Low
Average
High
Risk & Impact on Company
Low
Average
High
Strategic Importance
Low
Average
High
Number of Persons on Project
Generally 5–10
Generally 10–20
Generally > 20
Project Duration
Up to six months
6–12 months
6–24 months
Once the categories have been defined, please enter them above. In addition, we recommend that you mark the individual criteria in the table. The category parameters should be modified accordingly to your company/industry parameters.
11 Project Budget (Overview)
The financial framework within which the project has to operate is described here. Depending on the size of the framework, it may make sense to provide further details for individual parts.
Area
Amount
Project
Subproject
12 Project Startup
The project is deemed started with the following signatures:
Representative
of Steering Committee
Custome
Project Manage
Signature
Name
Date
13 Project End
Planned Project End:
13.1 Signatures for Release
The project manager is released with the signatures provided here following the project closing phase:
Representative
of Steering Committee
Custome
Project Manage
Signature
Name
Date
Annex
I. Glossary and A
eviations
If a
eviations have been used in this document (as well as terms that need to be defined in greater detail) and common understanding for every user is a prerequisite for the success of the project, this is an opportunity to explain them.
Term
Explanation
II. References, Accompanying Documents
If references have been made in this document to other external documents, these documents should be listed here.
Reference No.
Title
Doc. No.
File name: Project Charter.docx Page 19 of 19
Print date XXXXXXXXXX