How to face the urgent needs of customers

This article was reproduced from: http://blog.csdn.net/ioswyl88219/article/details/19167821

-------------------------------------------------Split Line Start-------------------------------------------------------------

Today to see a piece of the garden inside the article, just have encountered such a lot of things, recently there is a project encountered such a situation, feelings, wrote an article is an exchange of it.

Customers often have a lot of urgent needs, many customers are not software development professional, often take their usual software and our products or projects to compare, think such or such a function in the imagination should be a day or a short time to complete, but in writing code is short, but understand the needs, Version management and communication confirmation time is to be fully guaranteed, otherwise there is only one consequence, the chance of rework greatly increased, hard-written code into waste. At this time, who can experience our hearts in the blood of the feeling, so many overtime and painstaking efforts have not.

Therefore, the communication is confirmed in order to let customers understand that the needs must be clear and meticulous, understand the real requirements of customers, the two sides reached a consensus, and then in writing to confirm the form, the customer may think the trouble, but this trouble is necessary, on the one hand to ensure that demand is available, on the other hand the customer will be through this earnest Know our professionalism.

Let me give you a recent example.

A customer is famous for the rapid implementation of the main, a lot of recent needs, from the group of human resources, from the molecular company, from all levels like raindrops from the rushing, how to do, we take the approach is to record, with the standard document, inside the picture plus text plus the format of the prototype design to explain the needs of each, The unification is confirmed by the management of the group Human Resources department. Confirm after we do, and then urgent demand must also have records, even for the customer does not deduct money and rush to rush to work, afterwards also to confirm with the customer. The customer's attitude also slowly from the original immediately on the demand to the present thinking and then to mention the demand. The experience and lessons learned from the middle are:

1, need to be detailed description, must be standing in the customer's perspective, to avoid the text description, can have pictures as far as possible, there are new features to be supplemented with the prototype interface, this time is absolutely worth the cost

2, some small change is not a big change no new features, does not affect the general applicability of the product, but also related to customer work evaluation, such as changing the sort of query view, in the scope of requirements, can speed solve the speed, do not need to back and forth to confirm that the customer will understand. Not every job needs to be confirmed by the customer, so it loses the meaning of the need to confirm, we do need to confirm the meaning of the two sides to express the same, and the results are expected (image, prototype) consistent, not to engage so many documents trouble each other

3, document writing is a meticulous work, must stand in the customer's point of view to write, do not worry about trouble, the more clearly the need to confirm, the following brothers write code easier, the more will not appear rework phenomenon.

4, the requirements of the document must have a deep understanding of the product to write, a person if only responsible for their own modules of these functions, it is likely to consider not comprehensive

5, and then cross the customer also understand the meaning of the normative work, to master the balance, the need to fight first confirmed, even if the verbal communication began to do a very urgent function, but also in writing code immediately after the need to fill the document to confirm the customer, because then the code has just begun to write, if the understanding is wrong, still time to correct

--------------------------------------------------Split Line End-------------------------------------------------------------

How do I estimate project time? In the blog park to see this discussion and the text is very exciting article, hereby joins this link to record:

Http://www.cnblogs.com/baochuan/archive/2012/05/14/2499005.html

How to face the urgent needs of customers