Document directory
- Project Supervision and Control Methods
Project Supervision and Control Method 1. Process and guidelines for establishing project monitoring
1. Establish a policy: the project monitoring policy is described in our organizational process policy.
2. creation process: According to the organizational process flow, refer to the cropping guide and work out the project process definition based on the project conditions, which includes the project monitoring process.
2. Plan project monitoring activities
3. planning process: the project monitoring process is planned in the Project master plan and project schedule.
4. Resource Acquisition: The project master plan describes the personnel and hardware and software environment resources required for project monitoring. The company provides system rules and template support.
5. Clarify personnel responsibilities: the project personnel role responsibilities are clearly defined in the Organization team building guide. The project participants, roles, responsibilities, and tasks are described in the Project Master Plan and quality assurance plan.
6. Training: participated in the organizational process training, including the project monitoring process training.
3. Implement project monitoring activities
7. supervise the plan: weekly meetings are held every week, weekly reports are prepared, and the actual data in the Project Plan, including the demand scale, schedule, workload arrangement, and quality management planning, are monitored. The Project Manager monitors the project progress through the project data statistical table every week. Make a phased Summary of the project at the milestone meeting.
8. Supervise the completion of the plan: Check the work status through weekly meetings. When the milestone is reached, the Project Manager summarizes the task completion status in this phase and verifies the product of relevant stakeholders.
9. Supervise risks: Manage risks on a weekly, every milestone, and when an event is triggered based on the risk management plan.
10. Supervise Configuration Management: Listen to the work report of the configuration management personnel at the weekly meeting and query the configuration item status record table.
11. monitor stakeholder participation: Follow the stakeholder management plan to monitor their actual participation, for example, whether XXX attended the XXX review meeting.
12. supervise project problems: during project implementation, the Project Manager records the problems found in the project problem management table and develops a solution to the problems in the project problem management table, the solver is specified, and the status is recorded until the problem is closed.
13. Regular review of project progress and problems: hold weekly meetings to learn about the project progress and track the problem status.
14. milestone review: milestones and objectives are clearly defined in the project master plan. At each milestone point, we will review the milestones in the form of meetings. The middle and senior managers, QA and related stakeholders will be invited to attend the meeting to assess whether the milestone goal has been reached. Resolve the problems with relevant stakeholders. Until the problem is closed.
4. supervise and inspect the project monitoring process
14. Product inclusion configuration Library: Based on the configuration management plan, we include weekly meetings, milestones, project data statistical tables, and other process products into the configuration library.
15. ensure stakeholder involvement: In the Project Master Plan, we identify stakeholders involved in the project monitoring process and monitor stakeholder participation as appropriate based on the plan.
16. Monitoring Plan Completion: based on the main plan and progress plan, we supervise the completion of the plan.
17. Quality Audit: Project QA audits the project monitoring process and products during project execution based on the quality assurance plan.
5. Report to superiors
18. Report: The Project Manager prepares weekly reports and milestone reports to the middle and high-level managers. In case of major problems, work with the middle and high-level managers to solve them.
19. Collection of lessons learned: each milestone of the project has some experiences and lessons learned. The EPG collects improvement suggestions for lessons learned in the project team and records them in the process improvement suggestions table.