The white rabbit jumped to the bakery and asked, "Do you have one hundred breads, boss ?"
Boss: "Ah, sorry, there are not so many"
"That's it ..." The white rabbit left with frustration.
The next day, the white rabbit jumped to the bakery. "Boss, are there one hundred breads ?"
Boss: "Sorry, no"
"That's it ..." The White Rabbit went down again.
On the third day, the white rabbit jumped to the bakery. "Boss, are there one hundred breads ?"
The boss was happy to say, "Yes, yes. Today we have one hundred buns !!"
The White Rabbit took out the money: "That's great. I want to buy two !"
In the trap of yesterday's demand, we did not consider what kind of school the naughty pupils should go to, but the importance of demand research has aroused everyone's idea. However, after we need to do a good job of requirement research to avoid the trap of falling into the demand, we need to do a good job of requirement either in one sentence or in one article. Article It can be clearly explained that, after all, too many people are considering this topic. Today, we still need to consider how to make our needs meet the development requirements as much as possible and meet the real needs of our customers. It is a little far-fetched to use the story of the White Rabbit to buy bread. However, in actual development, if the problem is not well handled, the simple problem will be complicated and the complicated problem will be turned into a new one, there will be no white rabbit between the client and the developer.
1: simple
What is simplicity? How is it simple? Many people may say that primary school students are not suitable for cooperative research, because they complicate the simple problem. If such a person is in the team, it is a nightmare for the project team. In fact, when we were working on a project, we all wanted to simplify complicated problems. I believe that simple methods will become the first choice among the many methods that can also solve the customer's problems. Therefore, the simplification of the problem is not a fault, but a good method. However, there must be a premise for this simple practice, that is, it must meet the customer's functional and usage requirements, this may be very prone to errors. Many people have similar problems when defining requirements:
1) if you do not understand the customer's business, simply take it for granted.
2) The features proposed by the customer are simplified by stealing work
3) The questions raised by the customer are relatively mentally retarded and do not need to be simplified.
4) Simplification of details
For the simplicity of these aspects, I want to directly develop a program as a type of evil root. It is inevitable to repeatedly ask for noise during subsequent development.
So how should we choose a simple method? The old method is that the problem confirmation method should be simple, so that the customer can intuitively see what you want to do, whether that method is used, such as the interface speech, you can use all the methods to advance the demo in Agile development. The customer's advantage is that they are very clear about their work content, but do not expect them to clearly describe these problems in a very professional computing technology language. Do not let customers imagine what the system is like? All of this is not practical. It is difficult for two people to understand the same thing. For the same moon, one may imagine how bright the moon cakes are, and the other is how nice the moon cakes are. Therefore, if you use an intuitive way to describe the problem and put aside so many profound modeling tools, it may be easier for customers to understand. Of course, if the customer's capabilities are comparable to yours, those tools may be the best choice, so remember everything, both parties should determine to communicate at the same level in a corresponding manner.
2: Means
In simple communication, there must be means and skills to avoid the customer's dislike and get the best cooperation from the customer. This requires a strong EQ, but in these interactions, some common methods can greatly improve your communication performance.
1) Selective problems always work better than narrative Problems
When conducting a Demand Survey, if we use "Why...", what should we do ...?" In this way, ask the customer if this is the case: 1 ).... 2 )...." This method is much worse, and the customer's response speed is also quite different. Let the customer choose one of them. On the one hand, the customer feels that you have done a lot of work and thought, on the other hand, it saves a lot of time for customers.
2) visual descriptions
Writing documents may be difficult for developers. For customers, it is difficult to write a huge article, and many problems are difficult to describe, in addition to the incisive Characteristics of the Chinese text, the content of the description is sometimes ambiguous. Therefore, we recommend that you use a diagram to describe the problem in many cases, for example, the interface action description and some other logic methods can be used to intuitively describe the problem, so that the customer can reduce the reading time and understand it easily.
3) Avoid poetic Growth
Sometimes, when we write documents, we often see long sentences. A single sentence may have been dumped in three or four lines, totaling over 100 words. It is more difficult for customers to read books than they do. Some of the descriptions are too concise and profound, as described in the martial arts novels: "Knife, cool-air, falling with the moonlight, a Red Shadow slide, people will fall to the ground ." Poetry and stories focus on an artistic conception and give an imagination. But as a technical document, it is necessary to avoid providing such an imaginary space. The problems should be clear, intuitive, and clear. When describing a problem, we can divide the long sentence into short sentences and mark the serial number to describe the problem by point to improve readability.
3: not simple
In fact, the demand research work is not simple, because as the basis of project development, it bears a heavy burden and involves communication with customers and other issues. Therefore, it is not easy for developers to collect data clearly. How to Understand the customer's needs and how to communicate professional content through non-professional communication is not that easy. If we leave the national characteristics and the force majeure factors aside, this part of work can be said to be the starting role of the entire project. Whether it is a tiger head or a mouse head is a key part of the project.
