At present, there are many software companies that have a certain size of software companies are passionate about CMM certification. They not only want to raise the company's reputation, kick off and compete in the distance and make favorable positions in business bidding, but also to take this opportunity from essentially The company's software development strength reaches a qualitative leap. But what about small companies or small development groups? Due to funds, resources and scale, it is impossible to invest huge investment. Please ask for CMM certification, so it is also necessary to make some small companies, small development groups feel that there is no understanding and use CMM, but Is this really true? After learning the "Software Process Improvement and Management", and combined with the actual problems encountered in our work, I think even if a small company, a small development group, if it is possible to properly extract some of the Ideas of CMM to the daily software The development of work is also necessary to improve the development of the purpose, the purpose is not to be certified for certification, nor for the so-called CMM certification for the project, the key is to achieve the "improvement" purpose. Although our company is a listing IT company in Hong Kong, the main business is mainly system integration and solution, and the proportion of software part is not large, only technical support, software integration, and necessary software development, so and general professional Software development companies do have a lot of different places, so our department's software development can only belong to a small development group. Although it has passed ISO9001, this certification is mainly for system integration projects, and our company has always been in software development, and has not forming a very standardized management process, especially the textual transmission management is just the text of the company. Memory template. After learning the "Software Process Improvement and Management", I think many of the ideas in CMM are also useful in the previous development work, but there is only no very system sorting or rising to a certain level to do an improvement. Learn the theory of textbooks, recall the work of work, just can do theoretical guidance practice, practice the role of inspection theory, some thinking can be used in future work, it is indeed the development of our small group efficient. I roughly sorted out, with the following experience:
One. CMM is the upgrading of the ultimate goal of the programmer
Regardless of the software development, reuse is the ultimate pursuit of any programmer and program development group. From the previous structured development process, everyone races their brains to summarize public functions. It is now popular for object-oriented development processes; from previous public libraries to the current universal components ... It is a trajectory that the programmer's pursuit of reuse is the technique ... Some people say that the successful significance of software development is the technical, people and management, and the reuse has not been intermittent in the pursuit of technology, and people itself is also reused. Work hard, what about management? Although various management methods have emerged, from RUP iterations that are suitable for large teams, it is very specific, these development methods or is too specific, for domestic development groups, completely moving hard sleeves seem to have encountered This or that is difficult, or the midway die, or look for it, hesitate in various development models, and the level of CMM is different, it does not propose a specific operation guide, but From the perspective of the effect, its requirements are made and 5 different levels are developed: initial grades, repeated levels, defined, managed, and optimized. These levels are of course the higher level, but the groups of different sizes can make their own recent goals according to their own actual situation, and do not need to pursue unrealistic levels. For confiscated levels, it is actually the ultimate target - reusability of programmers have always been pursued. Combined with its own development process, like our small development group, there is no need to fully follow or meet each of these levels, then you have achieved anything level, these don't have any actual effects, it is better Several essence is taken from it, so that the purpose of improvement can be achieved. two. Strengthen project planning, specification plan
In the implementation of any project, you need to specify the necessary plans. Even if you haven't learned CMM, you should know if you have done it. After learning CMM, it is theoretically known that the plan is needed during the project implementation, which is the core content of SPP (Software Project Planning) in the CMM Level 2, and is also the basis for SPTO (Software Project Tracking and Oversight). This can be seen that the implementation of this activity of the project is directly affected to 2 KPA effects, and this is one of the difficulties of CMM secondary. In the previous project implementation, although it can be aware of the importance of the project plan, during the actual implementation, the work of the program tracking and progress record is often not sufficient, especially when the task is tight, tracking and The record sometimes became some facade of the project manager to lead the leadership, and did not really play the role. Since these records are not true, it is often not possible to make these data on the role of the later project, to the next similar project, all by the project manager, according to its own subjective experience, the distribution of the new project's progress and resources allocation It is estimated that the development of the project plan does not reach an improved effect. If the project personnel accept the idea of CMM, and can truly track the project process, the accumulation of real data is very effective for the improvement of future processes.
three. Establish configuration management mechanism
In the past, we also use some of the version control tools, such as CVS or VSS, but are just in order to synchronize everyone's code. After learning CMM, the reuse of the configuration management system is recognized, and the version control is also part of the configuration management. For small development groups, setting up an SCCB organization is completely unnecessary, but determines the controlled product and version management, the project group establishes the concept of baseline, milestones, version consistency, and more specification version of the CHECK-IN and Check-Out It is really necessary. Understand the CMM's configuration management mechanism, allow us to complete the previous version control from higher and more comprehensive perspectives during the development process, and this process improvement is also very obvious. four. Quality control system
Due to the reason for the human hand, for small development groups, in some extent, in the past development process, it is a thick line of quality assurance, and the developer has completed the Unit Test, I will go directly after I have a few times. The user has tested the user, and the result is often caused by the developers frequently called the on-site correction process error. This is inevitable, but there are many times, often affecting the progress of the entire project, and is very unfavorable to code management and overall monitoring. Under the guidance of CMM, the quality control management system cannot reduce its requirements because of the reasons of the human hand, Ning Kei's appropriate project time must also guarantee the quality.
Fives. Perfection of the supervision system
The supervisory system is not only the needs of management, but also the needs of members and project managers in the project team. Members of the project team should regularly report to the project manager, and the project manager is also obligated to periodically do project weekly reports and project progress summary. The supervision also includes the audit of the test personnel to work products, including demand documents, user manuals, code and product quality. Although this seems to seem to have a certain difficulty for the small development group, since there is a certain difficulty in implementation because of the reasons of human hand and resources, it should also pay attention to it in CMM. Understand, and finally reworked remedies. This will only have to get lost, but also make the entire development process less than a continuous improvement.
In general, CMM's thinking is not only suitable for big companies, but also can play a process improvement in the small development group. The key is to use limited resources to "ideal", making the entire development process towards a healthy, continuous Improved direction development.
