This article is transferred
Project Manager Alliance (PMU)
Any project executive person who has done a domestic project may have experienced this situation: the company's sales personnel hit the contract to give you a contract with the customer, claiming that this project is set, but when you Take the contract (or the mission attorney), on the point of view, there are only a few rows of instructions, or some high-hittings, or only the project contains what modules, but the specific business is just one or two The sentence is finished, if it is a manager who is in a hundred war and is familiar with the specific business of the project, if not what should I start this project? There is also a situation, customers continue to modify their opinions in the project process, more infusively, some questions begin to make changes, one day, the customer suddenly discovered that the situation is not right, ask you to change it, see The needs of customers are always endless, and how do you respond to this frustrating situation as a responsibility?
First, why the customer needs transition expansion
As the responsibility of maintaining the project, the launch of the project is guaranteed to complete the project, so that the company and the end customers are satisfied with the sacred duties of the project group. But do you have to satisfy your customers all your needs? Will it lead to failure of the project failure? In order to figure out these reasons, you should first find the root causes of these problems.
1. When signing a contract, the project scope is unclear. This is one of the most common problems, and it is also the early these issues that have not attracted enough attention from the project team, leading to endless modifications of postpartum projects.
2. Customer and project groups are inconsistent with demand written as a paper file. This situation is also more common, although the customer has confirmed the project scope manual submitted by the project group, the project team is also done in accordance with the content specified in this file, but the customer also requires the change, when the project group is holding the paper and the customer When the quality, it was found that the customer also recognized this demand, but the same thing, the customer's cognition and the awareness of the project team were completely different. For a simple example: Customers require the system to e-sign, the members of the project group simulates one, automatically generate customer signs in the system, but when handing over to customers, it will actually think that the electronic signature required by the customer is actually thinking. Turn the original handwritten signature to the electronic system, allowing the leaders to produce a handwritten signature in the way of drawing, should be signed in the document! Sometimes it is a little negligence, leading to a lot of modifications and even project extensions in the later period of the project.
3. Customers have always done everything before the knots. Generally speaking, customers will try to force all the ideas as much as possible before the project knots, because the general customer's psychology will be considered: Once the knot is, I want to find a project team member to modify the business system. Because IT is characterized by strong liquidity, even if the contractor can be found in the future, members of the project team doing projects are not necessarily there, or many companies have been with busy business, they have already paid their customers.
4. The project team personnel always have no conditional movement, and the customer is necessary. The starting point of this approach is good, the purpose is to be completely satisfied, but this practice does not necessarily achieve the purpose. The general customer needs have no bottom, which often has many negative impact on the entire project. Of course, if the customer's needs are over-controlled, the customer will definitely not satisfy.
Second, the solution
In response to the above project issues, the reason for the occurrence of the previous project, I feel that I can effectively block the problem of transition expansion in the customer needs through the following points, so that the project is more beautiful.
Precaution:
In the early stages of the project, you must formulate clear goals and project scope, and let the project main people (the most important of course is the final customer) confirm. Regardless of the approach obtained by the project, as the project supervisor, in the previous period of the project, you can walk three steps. The first question should be "why", that is, what is the purpose of the customer, knowing these, in order to more think about the customer thinking in the future work, not in the project direction error, and finally fight to achieve a double win situation .
After I know "Why", I will know very clearly "What to do", there is a better way to generalize the entire project with one or two very simple words, and can override the project in this way. Each sub-task, and enable the front desk business personnel and the background R & D personnel to be able to lead God, then the project supervisor has been very well grasped in the world.
In the end, I have to understand "how to do". For more strange projects, this stage work is also very important. At this stage, there is absolutely worth it. Of course, according to the specific situation, it can be This demand research phase simplifies some unnecessary work, which requires the project supervisor to balance the ability of those projects that are conflicting. In actual work, this requires a process, it is worth noting that after the demand finishing is completed, it is best to let the project team will pay more detailed and talk about the needs of our own summary, in the actual operation, This approach can not only reduce the number of the ambiguity of project staff and customers in the business level, but also pose a potential problem, and master some communication skills, which will make customers feel more about the contractor. They pay attention. In addition, if the project's pre-demand personnel do not understand the technology, it is best to communicate with the R & D staff before the actual situation is submitted to customers, to avoid unnecessary commitments to customers, more accurately define the workload. In summary, effective calculation of the project will occupy a certain amount of time, but there will be resource, funds, and the problem of resolution projects, such as demand (range).
Another worthless question is: After several confirmation, the demand for the project will make it clearly confirmed that there is a written signature, and this convincing document will play when the customer needs changes in the future. Very good role, it is clear, because the customer has signed confirmation, always refuse, even if the business changes have to be greatly adjusted to the project, this situation will also be in an advantageous position of the project group. It is not very dissatisfied with your company, and can even ask customers to reconsider project funding. Of course, for customers, through these very well-understood demands, it will also use this as a basis for delivery of products in the future. It is necessary to have no need to doubt, this is the same binding force for both parties, very benefit.
Flexible strain: encounter changes to communicate with customers
There is often this situation, the project has been implemented in the final stage, and the customer suddenly puts forward new requirements or requires changes to the existing needs, which will make the project supervisor very difficult: On the one hand, it is necessary to meet the needs of customers, on the other hand It is also impossible to do too much changes to the system, affect the progress plan. This situation occurs except for the demand phase, while notation is not closely related to the customer during the implementation process, lacking communication.
Analysis from the psychology of customers. Due to the particularity of the software, customers are often very concerned about the later service, especially those who do it in China, most of them are closely connected to the actual business. As a project manager, it is very taboo that the customer is ignored during the process of doing the project. When the last delivery is, it suddenly occurs a lot of contact with the customer. The possibility of problems in the later implementation process has the greatest possible, and it is more distraction with customers. It is likely to cause very risks. A more secure approach is to keep the project team to maintain contact with customers, understand each other, establish a more harmonious communication atmosphere, which may be prepared to conflict with customers in the future implementation transfer phase. It is worth mentioning that in the project process, it is a more direct progress of the project in the project process, so that the customer has a more direct visual understanding, and it is better to find the problem to solve the problem. After the constant communication It should be aware of the customer's perspective when you recognize the project team, so that the main person in charge of our customers can also feel that they are an important part of the project team, honor and disgrace, and the project group can provide customers with improved continuous Follow-up, this can effectively avoid the customer's brain juice to finish all things before the first knot. Even if the previous work is better, in many cases, demand changes are inevitable. The project supervisors have passed the good communication mechanism to master the changes and possible changes. Once change, the project group must calm down these issues, which can generally be analyzed -> cost / gain analysis -> Option-> expert Judging these four steps to first assess demand changes, and form a written instructions in writing as soon as possible, it is the basis of future project decision-making, of course, a relatively robust way to make customers a determination of the obvious changes (choose the best signature Especially after evaluating the increase in workloads, it is clear that customers understand that too much change will apparently cause the project extension, and customers should also be responsible.
When the customer is changed, you must master a certain communication skill, you must always have a customer. Generally speaking that customers are not familiar with IT, they think that very simple things, may cost a lot of uncomfortable energy, so don't think that the customer said, it must be what he wants! Most customers are the sparks who have emerged in the mind in the first time, so the project team should calm analysis: what is the purpose of the customer wants to achieve the problem. Generally speaking, there are many ways to achieve the essential demand of customers. Among the communication with our customers, you must avoid positive conflicts with our customers. In the early days, we will listen to the customer's opinion. If you have any questions like "What do you have any idea", wait for customers to express his ideas clearly, the members of the project team is best to quickly assess the customer's suggestion, if it is real Too difficult, you can give customers some more pertinent proposals, and ask more "Do you think this way? It can actually reach the same purpose." The problem, and finally there is an important process to confirm this communication with customers. Conclusion.
In short, the overall management of the project is a power to balance those projects that conflict with each other. It looks simple, but actually is very complicated, the project supervisor must learn how to control the common changes in the project process, control the severity of customer needs, and ensure that the project is healthy and stable.
1. When the project is started, the company will approve the beginning of a new project phase.
2. During the process of planning, a manual will be developed to describe what will be done in the project.
3. In the range definition, the main part of the project is divided into smaller parts.
4. When reviewing the scope, you need to accept the scope of the project.
5. In the range change control, over time, the project is required to be supervised.
