1. Configuration Management is part of management
The premise of UCM is that the company's management specifications are well organized, but what about looking for such a good small company there? Which small company's boss is not profit-oriented? Isn't the employee of that small company squashed by the company without dignity? In this case, no one will consider standardizing the company's management, and reducing the chance of seeking fish.
There is no standardized management, the most direct manifestation is unclear responsibilities and rights, chaotic plans, untracked and refined plans, Uninformed reporting to whom, unknown who is doing what, wrong or held accountable, and doing too much. will not get any extra benefits ...... UCM is based on activities, activities come from planning, poor planning, and unclear responsibilities. It is naturally impossible to use UCM.
2. The training cost is too high.
CC & CQ operations are a little complex and developers will not understand many operations. This is because the concept of configuration management is not deeply rooted in the hearts of the people. On the other hand, the CC and CQ interfaces are not very friendly, and developers will not bother to study this concept, therefore, many simple operations are difficult for skilled users to implement. In this case, many Configuration Management trainings are required for employees. But the actual situation is that small companies always have more tasks than people, and none of them can afford to be delayed. How to Train?
3. Low employee Quality
In particular, the quality of cooperation with people and the quality of software engineering
4. Many functions of CC & CQ are not available for general enterprises.
General enterprises only need to achieve basic version management, and the selling points of CC and CQ are not in this basic function. For example, configuration auditing, personal space, and multiple servers... for small companies, it is not only a waste of cost, but also impossible to make full use of its efficiency.
However, with its small size, VSS and CVs are more likely to become the configuration management tool in the hands of developers.
5. Poor performance
In actual use, there are often inexplicable slowness, leading to boredom of developers.
6. Management and maintenance costs
A development team of 20 members must have at least one full-time CC & CQ configuration administrator and several collaborators. Otherwise, they should not be used at all.
7. Summary
It seems that the positioning of tools is very important before any tool is selected, but it is also difficult to determine, especially for an inexperienced team, the first thing to do is to prioritize the use of cheap and easy tools, instead of being confused by the features and indicators of some products, these indicators are usually effective at a certain scale.
Tools can never replace management methods. The transformation of People's concepts is the first. At this time, the key lies in the determination of teams and leaders. Without determination, it is impossible to complete the transformation. In that case, nothing is empty...