A project charter is a document that formally approves a project, or approves whether an existing project will move to the next phase.

The initiator should be a project initiator outside the project organization, or it can be issued by an investor. Issuers should be at a level within their organization to approve the project and have the appropriate authority to provide the required funding for the project.

Determine the project manager's authority and determine the project manager as early as possible.

content:

A description of the products, results, or services to be provided by the project.

Environmental, organizational factors and systems that influence project success.

A systematic set of automation tools available within an organization.

1. Project and scope goals

2. Requirements and characteristics of products or services

3. Project requirements and deliverables

4. Product acceptance criteria

5. Project boundaries

6. Project constraints

7. Project assumptions

8. Initial project organization

9. Initial definition of risk

10. Progress milestones

11. Preliminary breakdown of project work

12. Preliminary magnitude cost estimate

13. Project configuration management requirements

14. Approval requirements

In the process of formulating the project scope statement (preliminary), the statement of work SOW is an important basis and reference.

1. Project background

2. Project manager, supervisor, client contact person, project management team, project implementation team members

3. Overall technical solution for the project.

4. Description of the tools and techniques used to complete these processes

5. The life cycle and related stages of the selected project

6. Final goals and phased goals of the project

7. Progress plan

8. Project budget

9. Change Process and Change Control Board

10. Communication management plan

11. Conduct critical management reviews of content, scope and timing to identify overhang issues and outstanding decisions

In addition to the schedule and project budget mentioned above, the project management plan can be summary or detailed and can contain one or more sub-plans

The three goals of project schedule, cost and quality are interrelated and restrict each other. When preparing a project management plan, it is necessary to unify the relationship between the three.

Each management process is closely related to each stage of the project life cycle. Each management process occurs at least once in each stage and will cycle multiple times if necessary.

Unified management of the project phase must first be achieved by formulating a unified project plan. The project is then implemented by actively executing the project plan, and any changes are managed uniformly during the project implementation until the project is completed.

Should include the main body of the plan and other sub-plans in the form of annexes

Help the project management team to formulate targeted project management plans and change control strategies based on customer requirements and specific project conditions, such as schedule priority, quality priority, and cost priority.

content:

After being unified by relevant project stakeholders, it becomes the baseline of the project, providing a basis for project execution, monitoring and changes.

By identifying product configuration items at different points in the product life cycle and systematically controlling changes to these identified product configuration items, the requirements for maintaining product integrity, consistency and traceability can be achieved.

It is a subsystem of the overall project management information system.

Configuration management systems in most domains include change control systems.

include:

A collection of formal specifications for technical guidance and management oversight

A collection of formal specifications that define how project deliverables and documents are controlled, changed, and approved.

1. Filling of deliverables

2. Actual progress

3. Costs incurred

4. Actual quality, actual productivity, etc.

See related content on cost control

Completed activities, results, milestones, incidents and issues discovered.

1. Suggested corrective measures

2. Recommended preventive measures

3. Suggested defect fixes

Includes status reports, progress reports, cost reports, performance reports, configuration status reports, and forecasts.

Identification of configuration items

configuration status

Configuration verification and auditing

The relationship between local changes and overall changes

change control process

1. Confirm the actions and activities of the project or phase that meet the needs of relevant stakeholders.

2. Actions and activities that confirm that completion standards for a project phase or the entire project have been met, or that confirm rollout standards for a project phase or the entire project.

3. When necessary, actions and activities that move project products or services to the next phase, or to production and/or operations.

4. Activities need to collect project or project phase records, check project success or failure, collect lessons learned, and archive future project management

1. Formal acceptance document

2. Project documents

3. Project closing documents

4. Historical information