Software Configuration Management Salon Activity Record 20041212
Yesterday, I participated in the software configuration management of the PKSPin organization, and some communication with some configuration management. It mainly learns the following aspects:
1. Everyone's career development path is basically the same, mostly to make development / integration work, then do QA or test, now go to configuration management.
[Note]: Every area has been aid in the development of personal careers, but pay attention to one or two aspects to be done, reaching the expert level.
2. Software configuration management is not long, some concepts do not matter, the key is that these understandings and practices are in line with the actual situation of the company and can solve problems.
3. The hardest configuration management work is to change the work habits of developers.
[Note]: According to the specific situation, if the developer does not understand configuration management, it will need to conduct relevant training; if the developer understands the configuration management, just do not want to implement according to the specification, then solve it from the heart and pay, standing in the developer The angle shows what benefits do they do. In addition, analyze the experiences and lessons advanced in the past, is beneficial to drugs.
4. Several larger software companies use CC as a configuration management tool, of course, small companies are VSS and CVS.
[Note]: I assessed CC, Firefly, CVS, VSS, PVCS, and JBCM, where Hansky's firefly and butterfly were still good, recommended.
5. The speaker also introduced the content of 6Sigma,
[Note]: Just exposure to 6Sigma's fur, behind the deep thoughts and methods have not blended into software quality management.
In addition, personal findings, baseline management, and branch strategies in configuration management are important, but few people mention.
