Clearly define the start | boundary of the project, establish the formal status of the project, and directly express support for the project from senior management

Goals must be quantified and measurable. Project goals have the following characteristics: ① Project goals have different priorities ② Project goals are hierarchical;

Project charter: a document that formally approves the project, issued by an outside organization; the project manager participates, does not issue it, and cannot be prepared independently)

1. The culture and composition of the organization or company; 2. Government or industry standards (such as management department rules and regulations, product standards, quality standards and process standards); 3. Infrastructure (such as existing software and hardware infrastructure); 4. Current Some human resources (such as skills, expertise and knowledge; 5 Personnel management (such as hiring and firing guidelines, employee performance evaluation and training records); 6 Company work approval system; 7 Market conditions; 8 Business database (such as standard cost estimation data, industry risk research information and risk database); 9 project management information system [The project manager cannot control it, cannot be tailored, and originates from outside the organization]

1 Processes and procedures: ① The organization’s standard process; ② Standard guidelines, templates, and work instructions; ③ Modification guidelines for the standard process to meet the specific needs of the project; ④ The organization’s communication requirements and reporting system; ⑤ Project closing guidelines or requirements ;⑥Financial control procedures; ⑦Problem and defect management procedures; ⑧Change control procedures; ⑨Risk control procedures; ⑩Approval and release work authorization procedures;

2 Organize all knowledge: ① project files; ② process measurement database; ③ experience learning system; ④ problem and defect management database; ⑤ configuration management knowledge base; ⑥ financial database. [Controllable by the project manager, tailorable, and sourced from within]

1 Organizational or company culture and structure; 2 Government or industry standards (such as regulations, product standards, quality standards, labor relations standards); 3 Infrastructure, such as existing facilities and fixed assets; 4 Existing human resources, Such as: skills, professional knowledge (design, development, legal, contract and procurement); 5 human resource management, such as recruitment and firing guidelines, employee performance evaluation and training records, etc.; 6 market conditions; 7 project stakeholders’ understanding of risks Tolerance; 8 commercial database, industry risk research information and risk database, cost budget data, etc.; 9 project management information system, but does not include contracts

Tools and Techniques: Expert Judgment Guidance Techniques

Determines the ways and means to execute, monitor, control and close the project. The project management plan is the main plan or overall plan of the project. It determines the ways and means to execute, monitor and end the project. It is the basis and basis for the formulation of other sub-plans. It guides the orderly progress of the project work as a whole. . Participation of all stakeholders (full participation); gradual accuracy (iteration)

Generally include project scope management plan, schedule management plan, cost management plan, quality management plan, process improvement plan, staffing management plan, communication management plan, risk management plan, procurement management plan and other sub-plans. The project management plan can be detailed and can be composed of one or more partial plans and other matters. Other parts can include: milestone list, resource calendar, schedule baseline, cost baseline, scope baseline, risk register, etc.

content

Corrective Action: Purposeful activities (for actual deviations that have occurred) to bring project work performance back into line with the project management plan;

Preventive Action: Purposeful activities (against possible future deviations) to ensure that the future performance of the project work is consistent with the project management plan;

Defect Remediation: (Product or product component, defect remediation measures only address project quality issues) Purposeful activities to correct inconsistent products or product components;

Update: A change to a formally controlled project document or plan, etc., to reflect modified or added comments or content.

To people

right thing

Work performance reports provide a comparison of current project status with expected project status. Results from schedule control, cost control, quality control, and scope validation assist in project team management, help determine future human resource needs, develop recognition and rewards, and update staffing management plans.

Analysis techniques: regression analysis; grouping methods; causal analysis; root cause analysis; forecasting methods (such as time series, scenario construction, simulation, etc.); failure mode and impact analysis; fault tree analysis; reserve analysis; trend analysis; earned value management; Difference analysis

Approved changes: The result of implementing an overall change control process. Their implementation needs to be confirmed to ensure that they are implemented correctly. Confirmed changes use data to demonstrate that the changes have been correctly implemented.

The overall change control process runs throughout the project. Because projects rarely follow the project management plan exactly, change control is essential.

Configuration management activities include: ① configuration identification, ② configuration status recording, ③ configuration verification and auditing

A configuration management system with a change control system provides a standard, effective and efficient process for centrally managing changes within a project. Configuration management with change control involves identifying, recording, and controlling changes to deliverables within the project baseline. Configuration management related activities occur throughout overall change control.

The process of completing all activities of all project management process groups to formally close a project or phase.

Formal acceptance and handover of final products, services and results submitted by authorized projects. Acceptance includes the receipt of a formal statement that the requirements of the contract terms have been met (at the end of the phase, it is the handover of the intermediate products, services or results produced in that phase).

Deliverables for acceptance: Approved product specifications, delivery receipts, and work performance documentation. Phased projects or canceled projects may include incomplete or intermediate deliverables.

Project closing management work: ① project acceptance work; ② project summary work; ③ system maintenance work; ④ post-project evaluation work.

The acceptance phase of a system integration project includes: ① acceptance testing; ② system trial operation; ③ system document acceptance; ④ final project inspection.

For system integration projects, the documentation should include the following parts: ① system integration project introduction, ② system integration project final report, ③ information system instruction manual, ④ information system maintenance manual, ⑤ software and hardware product instructions, and quality assurance letter.

Management closing (administrative closing), which belongs to the project closing, is to check whether the project team members and relevant stakeholders have performed all their duties as required.

Significance: ① Understand the working conditions of the entire project process and the performance status of relevant teams or members; ② Understand the problems that have arisen and summarize improvement measures; ③ Understand the lessons learned during the entire project process and summarize them; ④ Discuss the summarized documents, and after approval, they will be stored in the company's knowledge base and incorporated into the company's process assets.

Project summary meeting discussion content: ① project performance; ② technical performance; ③ cost performance; ④ schedule performance; ⑤ project communication; ⑥ identification of problems and problem solving; ⑦ opinions and suggestions.

1. Follow-up work of the software project: ① software bug modification; ② software upgrade; ③ follow-up technical support.