Research on the demand of Project Management

Whether or not the Demand Survey in a project is sufficient is one of the key factors for project success or failure in the future. Which of the following project managers do not agree with this? However, the demand research I mentioned is not just about memorizing what the customer said. As the name suggests, it is about investigating and researching the customer's ideas. I feel that we should start with the following steps:

What do customers want?

What are you doing here?

Why?

Will there be other ideas?

Here we also talk about the most basic thing. We only talk about projects and don't talk about money. We can say that we need to go back and analyze your needs in detail to provide you with an overall solution, you can rest assured that the price is reasonable and will not exceed your budget ). Because if you talk about money, you have to cut down your price first, cut down your time, and finally add some features. You need to make a kickback. One knife on the left and one knife on the right, cut off the project, vomit blood, and drag your final payment. The customer manager and project manager here should be careful.

Through the above four steps, our goal is to find out the customer's requirements, the logic of the requirements, the results the customer wants, eliminate the development risks, and explore and control potential requirements. Let's discuss it one by one.

Step 1: What do customers want

This step is the easiest. Take out our notebook. What? Do you have a project manager? It was a big failure. I went to the boss to apply for one. If I didn't give it to IBM or DELL, I should at least have a soft-skinned notebook, (I am using a 32-core soft leather notebook). A good notebook can make the customer feel that you pay attention to this project. It is also easy for us to query past records in a fixed notebook in the future, this is important. In this case, let the customer start to talk about the following points: OK, OK, ah. If you are not addicted, why? When talking about the customer, he mostly thinks about what he wants at the same time, does not interrupt his ideas, respects the power of expression of the other party, and allows him to systematically present all his ideas, let's record the problem and mark it later. This is one of them. Second, he said that you also said that the more you say, the more you get off work in a short time. Finally, we found that the result of today is that we will continue to talk about it next time. Now we are in the investigation stage. We haven't studied it yet. At least we don't know what people think. So remember more and speak less.

Okay, he finished speaking. Now we can repeat it one by one. At the same time, we can make suggestions. After reading it, It's a suggestion, not an opinion, therefore, we need to grasp our attitude. We are here to help them do things. We need to rationalize and simplify the customer's needs. To put it bluntly, the procedures should not be too complicated, and risks should be eliminated, do not create something that is logical, complex, or practical. In this process, we enter the second step.

Step 2 What do customers want to do this?

After hearing all the requirements, we should be able to analyze the customer's key points and start to study and repeat the customer's needs. Don't think that what he says, you will understand what you hear, let alone "I thought". I thought it was easy to ask, so I explained it again with my own understanding. Then the customer began to listen to you, he began to understand what he was talking about right and what he was talking about. If he was not correct, he would add something wrong, write it down, and repeat the explanation. Don't worry about the trouble. Now we have to say it a few times, and we are more polite than people who have disputes over requirements in the future. I can explain it to you today. If you sign the letter in the future, don't say that's not the case. Step 3 is enabled when you encounter complex or weird problems in your needs.

Step 3: Why does he think so?

Most of the customers are not IT experts, and of course they are self-righteous. These people will save their faces and they will give them their faces in the future. Since IT experts may not think about some problems in terms of program implementation, most of them are industry experts who are at least clear about their own industry processes, all we need to figure out their industry processes or business logic to see what they want us to implement for them using programs and what they want to do? For example, what do you want to do if you want to analyze the product shipments? I want to know how many goods are delivered every day. I just need to summarize them by class. When the customer talks about the demand, some people are used to talking about the function as big, nice, and elegant, there is a face, the most often heard "Come, let's make an ERP", "I want to analyze statistics", "I want to make a comprehensive query of that piece", what system, what platform, actually, as it said, the function is not so big, so we need to analyze it. However, if you say it is big, it means that if you agree it is big, it will be very expensive, haha! Therefore, customers say big is not a bad thing. In addition, many key problems can be easily solved by understanding what they want to do.

Now he has finished speaking, and you have finished speaking. If time is too rich, repeat it again, chat, and chat. If it's okay, pack up and leave. Don't forget to set a time to deliver the solution with others when you leave, if he doesn't decide with you, it means he doesn't pay attention to it, at least not in a hurry. If you don't decide with him, it means you're not serious. So let's talk about it later.

Are there any other steps? Yes. The company wants to do this step because it is complicated.

Step 4, will he have any other ideas?

After the requirement is collected, we have to think about it. What does he need? What are you doing here? Why? Again, tired> _ <. Finally, let's think about whether he has other ideas. Why is this complicated? Some people have said that they have to explore potential needs and think of unexpected things from customers. Yes, that's right. But this is not the key. The key lies in the fact that some ideas can be dug and some cannot be dug. If you have used mine clearance, I like to call it mine clearance. Some of the requirements are beneficial to the project, some are not beneficial to the project, or even destroy our project. For example, if they want to record personnel information, you should not manage the analysis adult affairs system. There are several possibilities for this analysis. If the customer accepts this analysis, it will be done according to the original budget. After the analysis, the customer will lose the money! If the customer says yes, why didn't I think about it? I think about it again. Well, there's no trust in the project! Therefore, potential mining needs must be implemented within a certain range. This demand has certain project experience and support, otherwise it will be totally lost. There are also complicated functions to be implemented. Naturally, we do not need to dig them. At least we will not explore them during the current development period. When the customer asks them, they will try to find a solution for the second phase.

In addition, mine clearance is also related to the company's project strategy, to see if we want to hold customers to long-term customers through a certain requirement, rather than through any function to trigger their second-phase development, this requires communication with the boss, so this step is more complicated. It is good to play more with mine clearance.

All right, the four steps are complete. To sum up, we should focus on the customer's thoughts during the survey. Why? Instead of what you want to do? Because what he thinks is not necessarily true, we need to analyze what he finally wants and is the most concise solution. Of course, this analysis is of course, we can eliminate some of our own risks. It is important to understand why customers think so. At the same time, mining potential needs must be within a certain scope. The customer's development projects are budgeted and will not be appended due to the addition of functions, except for some of the projects that make money.

After all the analyses are completed, a detailed document should be formed. I feel that it is best to provide a function description first and then a UI design.

Function Description: for example, the contract management module provides the add, delete, modify, and query functions, including the fields involved in the ADD and modify operations, the logical relationship of the fields, and whether the delete operation supports batch operations, query the fields that can be queried. Finally, it shows whether there is a logical relationship with other modules. In short, you can write more details (of course, it is also related to the scale of the project, but there are fixed document specifications that are actually not difficult to write), this thing has been stamped, we have a certain degree of initiative, so that we can at least have it. It is better than nothing. If it is not, it will be totally unreasonable.

Interface Description: click a sketch on the page, and use Word, VS, and DW to display information and place fields on the page. This interface mainly describes the buttons, what is the output and what functions are available on the page. The last one is the same as the signature and seal, why did the customer sign and seal again? Be careful when the customer's owner leaves the company during the project, and the customer will not accept the account.

The development of these two documents is much more stable, but the project is not unchanged. The Ancients cloud, the project is always changing.