CMM (Project Planning and Tracking Project Management)

Simple planning and tracking are only part of project management. Here we will start with project management to sort out daily management experiences and methods.
I. Basic responsibilities and methods:
A. Evaluate the project.
B. Plan the project:
Including:
The selection and cropping of this software process (specifically, the selection of the life cycle process and method)
Assign WBS to project jobs,
Quality Plan.
Test policy.
Risk plan.
Configure the management plan.
Personnel Training Program (if necessary, such as using new technologies, the current level of personnel is not high)
C. Tracking projects:
Weekly, daily, monthly, and phase meetings should be used to identify and solve problems on a regular basis, and QA data analysis should be conducted.
D. Conduct quality control, strengthen review, and coordinate measurement personnel to measure relevant data.

Coordinates with other departments ..

2. More requirements:
A. Training and mentor program.
B. componentized reuse management.
C. Team building management.

3. Management from the perspective of life cycle:
first, obtain the requirement from the user or product manager -- conduct feasibility analysis-> System Analysis (hardware-related division to hardware department) -assign tasks to the project team (specify pm, QA, MC, Tc) -Conduct software evaluation-plan-Software Requirement Analysis-Design and Development-test-release
in this process, the project is tracked according to the original plan, the plan is fixed at each stage. PM/QA carries out process and quality tracking (Process Tracking and auditing). PM/MC also measures process data and accumulates experience data as experience data for other project management, and the Ability Evaluation of the organization and the basis for team building.