Project charter in MS Project Pro (server version)

Contents:

1. How to use the Project Charter report in MS Project Pro (server version)
2. How to customize the Project Charter report in MS Project Pro (local version)
3. Chat

How to use the Project Charter report in MS Project Pro (server version)

General Information

General information of the charter refers to:

• Project name - The name of the project, which will subsequently appear in project documentation and reporting documents
• Customer - the name of the company that ordered the project.
• Start date - Project start date
• Project Manager - Last name and first name of the project manager.
• Project location - the place where the project will be implemented.
• Project type - the name of the project type.

Purpose and products of the project

• Purpose of the project: describe the purpose of participation in the project for the company. List of goals to achieve this project. Goals are indicated, the achievement of which will satisfy the needs/solve the problems of the potential customer.
• Basic product requirements:

To complete this section, it is necessary to break down the final result of the project into several intermediate results and highlight the project stages necessary to achieve the designated results. In the case of further breakdown of intermediate results, the stages can be divided into sub-stages. If the result of one stage is necessary for the implementation of another stage, then such stages can only be executed sequentially. Otherwise, the stages can be executed in parallel, independently of each other. Both the stages of the project and their results that are subject to acceptance upon completion (documents, organizational charts, products, models, etc.) are indicated. The result of filling out this field is formatted as follows: Stage name – Result.

The criteria for assessing the success/effectiveness of the project in relation to the classification are indicated. The following types of criteria are distinguished:

• key performance indicators – key performance indicators adopted by the company, the values ​​of which will be changed by the implementation of the solution;
• expected characteristics of the project result - characteristics of the solution being developed;
• degree of solution to the problem - problems that the implemented solution will partially or completely solve;
• the degree of satisfaction of the Customer's needs - the Customer's needs that will be satisfied by the implemented solution;
• compliance with the main parameters of the project - quality, deadlines, resources.

The criteria for assessing the success/effectiveness of the project in relation to the classification are indicated. The following types of criteria are distinguished:

• key performance indicators – key performance indicators adopted by the company, the values ​​of which will be changed by the implementation of the solution;
• expected characteristics of the project result - characteristics of the solution being developed;
• degree of solution to the problem - problems that the implemented solution will partially or completely solve;
• the degree of satisfaction of the Customer's needs - the Customer's needs that will be satisfied by the implemented solution;
• compliance with the main parameters of the project - quality, deadlines, resources.

Project risks

Be aware of the key risks of the project, the occurrence of which could lead to failure. The presence of a corporate risk register in a company greatly simplifies the process of describing risks. Read more in the material “Risk Initiation” (pm-way.com/materials/material/show/145).

A description of the risks and measures to prevent them is provided. The following types of risks are distinguished:

• risks of project participants - risks associated with the fulfillment by participants of their obligations within the project, with the emergence of new participants;
• commercial risks – risks associated with the sale of the product (obtaining project results);
• financial risks – risks associated with the financing of the project, the timing of its implementation and the return of invested funds;
• political risks – risks associated with political aspects;
• legal risks – risks associated with legislation and execution of legal documents;
• environmental risks – risks associated with the environment;
• technical risks – risks associated with technologies, competencies, materials and equipment;
• other – risks associated with the implementation of other projects (indicated in accordance with the interfering connections with the company’s projects).
• Project participants

This paragraph indicates all interested parties of the project (stakeholders) participating in the project. If there are many of them and it is desirable to group them, the name of the group and its participation should be determined by general corporate documents.

Project deadlines

List of tasks indicating deadlines for receiving project products.

Project participants

This paragraph indicates all interested parties of the project (stakeholders) participating in the project. If there are many of them and it is desirable to group them, the name of the group and its participation should be determined by general corporate documents.

Project deadlines

List of tasks indicating deadlines for receiving project products.

Top level tasks

The scope of the project includes work on the design, implementation and implementation of logically completed and interconnected functional blocks and components of the project product and is defined from four perspectives:

• The functional scope determines the functional characteristics of the implemented product. The decision to use this or that product functionality is dictated by the business processes of the enterprise where the project results are being implemented.
• The organizational volume, which is determined by the divisions of the enterprise - organizational units (departments, specifically defined jobs) within these divisions, covered by the implementation of the product.
• Technical scope, which is determined by the requirement for the normal functioning of the project product within a given functional and organizational scope.
• Another scope, which is determined by the requirements for interaction with other products in the enterprise or other requirements that are not part of the functional, organizational and technical scopes.

How to customize the Project Charter report in MS Project Pro (server version)

To obtain the Project Charter report:

• Register or go to the website.
• Pay for the report
• Download the project's llan-garfic with the report.

To install the report you need:

• Create enterpricse columns: "Strategic", "Customer", "Location" and "Project Type".
• Open the project schedule with a connection to the server.
• Copy the following filters: “Strategic objectives” and “Extreme terms” into the global corporate template.
• Replacing the "Flag 1" field with the corporate field "Strategic"
• Copy the Project Charter report to the global enterprise template.