Harmony in software development

The project is becoming more and more enriched, and the development team is also growing. Although the progress is barely keeping up, there are still some established or potential problems in the collaboration between the team and the team, these problems also affect the quality and progress of the project, and when talking about these problems, there will often be mutual complaints. Such problems are common even in a large, well-regulated company. A friend of the top 500 multinational companies once complained to me about how difficult the company was to coordinate. The seriousness of the problem is self-evident for enterprises in domestic similar workshops. How to solve these problems is what every project administrator should think and do.
During project development and testing, the main factors for disharmony include: within the development team, the development team and the test team, between the development team and the sales team, these discord can be solved or mitigated in the following aspects.
First, we look for the root cause of the problem from our own perspective. I found that developers have a common problem and do not like to communicate with people. In some companies, such as outsourcing companies, software Requirement documents are relatively complete and fixed. At this time, developers only need to develop according to the document, which is no problem, but in some companies that develop their own products, the demand for products is always changing. The development documentation will not be too timely. Some of our developers like to implement vague requirements and will not actively communicate with product departments and test departments, it is often because we have spent a lot of effort to make a function, show it to the product department, but people shake their heads and say that this is not what they want, the greatest pain in life is this. We were very angry because we had paid for our work, but we were not recognized. Our products were also angry, and their products could not be completed on time. To solve this problem, I think our developers are too passive to understand or fuzzy. In most cases, we do not ask product designers, instead, we closed doors to build cars based on our preferences, resulting in both human and material resources losses. If the product designers and R & D engineers are far away from each other in the region, it is not easy to communicate with each other, but sitting in an office, why can't we talk about it in advance. Do you dare not, disdain, or never think about the importance of communication? My current work style is something I don't understand. I'm sure I want to contact related product designers for effective communication. I never worried that he will get bored, he should write the design documents clearly early. Products developed through communication are more likely to be recognized by people, which I have learned at present.
The cause is that the product and testing departments share the same unshirkable responsibility. First, some product designers wrote ambiguous documents, which are not very standard, in the process of changing requirements, the product department cannot update the requirement documents and submit them to developers in a timely manner. This also leads to a gap between what developers can do and their needs. This leads to differences between the product department and the Development Department. To solve this problem, the product department should try to standardize the documentation. We should also supervise and track the development process. When we find that the products and requirements developed by developers are inconsistent, we have the right and obligation to remind them in a timely manner. Everyone has a single purpose. They all work well to create greater value for the company. Instead, we should not blindly talk about each other and blame each other.
Coordination with the test team is even more important. Sometimes, some developers cannot understand the work of the test team and think that the test staff is too picky and pick bones in the eggs, both the test team and the development team play an indispensable role. Developers often do not know the true nature of the development team. Because of this, some bug developers cannot find it, developers all think positively. Some problems are the blind spots of developers. In addition, some developers do not pay much attention to details, and the character function can be implemented, it is not worth the effort on the interface. This idea is definitely wrong. As you can see from Microsoft's products, Microsoft is always able to popularize existing products with proven prospects, for example, in office, windows, Aja, and IE, our developers need to ideologically recognize that "Details determine everything". A commercial software should not only have sufficient functions, there must also be a user-friendly interface. Therefore, when the tester raises issues related to the UI, such as color and font, We must patiently solve them, instead of holding the hostility.
One sentence: design and programming are all human activities. If you forget this, you will lose everything! During our work, we need to communicate more, understand more, complain less, and strive to get on with the harmony of software development as soon as possible.