Old Problems in software development-CommunicationThere is a rule in software development (the brook rule): Adding manpower to projects with low progress can only make the progress more backward. We can often hear the saying "1 + 1> 2", but from this rule we can know that in software development, 1 plus 1 is less than 2, or even less than 1, why? The main reason is communication. Communication between project developers produces additional time overhead and may even lead to new problems due to communication, as a result, newly added developers have major design defects due to incomplete understanding of the problem, making software development more difficult. In the Mythical man-month, this article discusses the reasons for the failed construction of the ancient Babylon Tower Project: lack of communication and the result of communication-organization. "Because the left hand does not know what the right hand is doing, so progress disasters, unreasonable functions and system defects have emerged ." Due to various assumptions about other people, the understanding between team members began to deviate, resulting in project failure. I also mentioned several elements of "Organization", which are very meaningful. One of them impressed me the most: the goal of a team is to reduce the amount of communication and collaboration required. When you contact your work, you will find that this description is very accurate. Since communication will incur additional costs, you must first have a better organization, A better organization reduces unnecessary communication and reduces the amount of communication and collaboration, which improves work efficiency. "Communication, communication, or communication ." Every mature programmer or software project manager will repeatedly emphasize this problem. What are the forms of communication? General forms include informal and regular project meetings, briefing technical presentations, shared formal project work manuals, and e-mails. I think the project work manual is the most important, especially in large-scale project development, the project work manual enables communication to be carried out in a tangible way among each project developer. The project work manual records all development-related content and ensures smooth and orderly development of the project. For communication, I think there is another form that is the most easily overlooked, namely training. When it comes to training, it is generally considered as training for new employees, I think training can be defined more broadly: a kind of learning communication. A development team also has a running-in process. One way to promote running-in is to conduct regular training (exchange and learning ), for example, the exchange of development experience, understanding of new technologies, and discussion of working methods should make training a two-way interactive approach, rather than a full-blown approach, which should benefit everyone, everyone can make progress in training. During the communication process, be careful not to get into a situation where each other is arrogant. An effective communication should make the development goal clearer and the collaboration between developers more effective. Finally, let's take a look at the problem solving behind schedule and add new players. As more communication is required, the efficiency problem arises. Therefore, in the face of such problems, we need to timely consider the re-arrangement of the progress, and do not pin our hopes on more manpower. The most important question after increasing manpower is how to improve the communication efficiency, in particular, communication should be listed as the most critical issue at the beginning, and the negative effects caused by increased manpower should be minimized, I think if you have fully considered and put it into practice, you can achieve the effect of 1 plus 1 plus 2 or greater. In fact, in many cases, it is good to be greater than 1.
