Process Improvement for batch cmme Software

The four or five levels of high maturity level of CMMs emphasize data and quantitative project management, provided that the process itself is stable and the Organization has a mature and easy-to-use software development process management support platform, routine task feedback, changes, and defect records should be integrated into daily work. Data collection should be automated as much as possible, and data collection cannot interrupt developers' work and affect their thinking and efficiency.

When the technical platform and development model are inconsistent at the organization level, the process definition must avoid a one-size-fits-all standard software development process. You need to make appropriate adjustments based on the characteristics and personnel of the project to meet the project objectives.

Software is developed by people. The process is important but the people are more important. The two must be combined. It is inappropriate to emphasize or exaggerate one aspect. For small agile teams, we emphasize the importance of people and the importance of standards and processes for large software projects. This must be based on the characteristics and actual conditions of the project.

The reason why all certification and training markets become more appealing in China lies in the quick success and inpragmatic attitude of the management, as a result, cmme is only used to complete the image project and tender negotiation. If the cmme process improvement does not actually improve the quality and efficiency of the Organization, it will be difficult for a long time.

Cmme provides support for multiple iterations and rapid prototyping, but in fact many Pa and many evaluators still give suggestions based on the waterfall model. In actual software development, especially projects with a delivery cycle of only 2-3 months or shorter, it is difficult to develop based on the waterfall model.

All of them comply with the process specifications and requirements of cmme. will the project be successful? The answer here is still not necessarily. The key issue is that cmme is based on many assumptions. For example, if an organization can provide qualified personnel, the requirements are basically stable, these assumptions are often not satisfied. Cmme provides us with an ideal model based on many assumptions. The actual situation is that if these assumptions are well met, you may not need cmme to guarantee the project success.

CMMS emphasizes evidence, Data, processes, and documents. Cmme tells you what to do and you need evidence to prove that you have done it. Therefore, preparing data and documents is a very costly process, when we were not mature in the early stage, we were more concerned with the actual benefits brought about by the cost of a job, that is, the input-output ratio. For example, demand tracking is often considered to be less cost-effective.

A mature agile team (such as thoughtworks) naturally has a maturity of Level 5 of CMPs, the problem solving process is clear, repetitive, measurable, manageable, and self-optimized in the face of projects. If these goals are not met in the software process improvement, the real improvement effect will not be achieved.

Documents cannot completely replace communication, but they cannot deny the importance of documents and code. When we focus on the management and standardization of the development process, software projects and teams will become mature. One advantage of maturity is that the entire project and team will not depend entirely on one or two cool people. The advanced experience and lessons learned during the continuous implementation of the project can be truly solidified to form important assets of the Organization and project.

What every Pa of CMMs needs to do is that CMMS won't tell you how to do it. But what you need to figure out first is why it is necessary to do it. What is its significance? We must be objective and problem-driven in the process of software process improvement so that we can take the initiative to make improvements in a critical manner.