Lenin said: learn, learn, and work hard!
I. objective of improving the process management system
1. Integrate the advantages of existing frameworks and organize the organization of project modules in development tools to reduce labor investment in repetitive and inefficient work in development, testing, and release;
2. Sort out, simplify, and clarify various routine processes, standardize the overall software development process, facilitate new employees to quickly understand and integrate the development process, and shorten the growth cycle;
2. Make good use of various tools, such as design, license management, and installation package creation, to standardize the work process, simplify manual operations, and reduce work difficulty, so as to save labor costs;
Ii. Process Management System Concepts and work content levels
Note:
1. The resource management layer provides resource services for the company's project and product development for non-project-based basic work;
2. The project management system layer is a management concept, which mainly clarifies various work owners, regulators, and control priorities;
3. Implement the assurance system layer to monitor and correct the project process through a series of reviews and reviews to reduce project risks;
4. The project management layer plans, tracks, and records the project process through existing management specifications and document templates for implementation of specific project processes. At the same time, according to the requirements of the assurance system, submit the project stage report documents by project node or periodically.
Iii. Process Management System work form
Note:
1. Document Type: system standard documents, Project Process documents, and regulatory control documents are displayed in different colors;
2. The system standard documents are basically existing, but most of them are text-based content. We recommend that you change them to flowcharts to help developers quickly master and understand the work process, however, the testing and version release processes need to be supplemented;
3. the project process documentation is relatively complete and can be extended with existing standards;
4. The regulatory control documents are more embodied in team interaction, the participation of the company's backbone in project management, technical review, and other work, as well as timely discovery and rapid solution to problems, ensure smooth development of projects or products as planned.
Iv. Process Management system organization work plan
1. Merge and optimize frameworks and class libraries (this work has started );
2. Simplify and organize various specifications and processes, aiming at being easy to understand, executable, and controllable (including routine stages such as development, testing, and release );
3. describes how to use various gadgets during development (including database initialization, preparation of upgrade packages, version release, and license management. At present, there are some foundations ).