Feelings of the mere formality of communication

Communication enables the developer to understand the needs of the user and to achieve the purpose of the project. The project is also the development of communication with customers, the project after the completion of communication and communication is of course more conducive to better exchanges between the two companies and cooperation. Good communication makes a career and achieves the goal of winning. However, there is also a formality of communication, in the project review, you should recognize the mere formality of communication, which may be the most direct cause of your project being constantly overturned and constantly delayed.

Customers do not understand the C language program does not know how to express themselves to the programmer to the requirements of the detailed requirements of the project, we can not ask the customer must understand the computer requirements, after all, the customer is to communicate with us, we do will be communication with the computer, so that it to do something for us. Then the role of the project manager or the demand research has arisen, and the position is required to be well versed in the business involved in the project, but this is often not possible because we are a software company, not a company that does these customer businesses. So the consulting company appeared, they used a modeling idea with our customers business needs, with some identifiers to convey ideas, they use the model language of Esperanto, but customers do not understand the C language, they will be on the UML have a good understanding of it.

The use cases of UML are made up of use-case diagrams and use-case protocols, and there is a set of methods to illustrate how to do it, which is similar to the specification and has more details, and the diagram uses several graphical symbols to describe system boundaries and role relationships. as a way of communicating with customers, UML facilitates communication. However, it is important to note that the accuracy of the pattern itself is not what we are trying to achieve. What we need is effective communication, the model is just a means. If possible, can satisfy the limit programming that is also the method ah, need to notice is the method is not unique.

UML is indeed one of the best ways to solve communication problems. Just one project will not give the team a deep understanding of what he means. And not every project has to be used. The customer understands and supports UML, the project will have a good UML usage environment. However, the fundamental problem with not using UMLis the choice of communication methods. As long as it is effective, it is a good way to communicate among the various project roles.

Communication needs to be based on the customer's time and effort to determine the timing. The completion of a project needs to be based on the actual understanding of customer demand information points, determine the target and direction, design items. Every communication should not just be eating and drinking to talk about feelings, it is important to adjust the direction of the implementation of the project in time according to the customer's meaning. It should be clear that ensuring the effectiveness of every communication is the most important thing.

China has a history of 5,000 years of civilization, and only 3,000 years of history can be traced. It is the subjective reason of the ancients or the destruction of books by Qin Shihuang and other people, which eventually caused a period of history, we can now only speculate according to fossils,C14 and so on. This is also the case, if there is no historical record in the project, it can only be takes, or it will cost a great deal of manpower and resources. So do the history of each stage and write down your name, and those people can find the source of the problem through you. Leaving communication channels for non-existent roles is an effective way of communicating.

Feelings of the mere formality of communication