The software project is developed to the later, especially the system architecture is basically stable. If the customer puts forward new needs, it will often give a big risk to the project. In the eyes of the customer, it may be just a small small requirement to bring a serious impact on the system (it is possible to be a system design, but at this time, I don't care about it.). In order to make the project on time, you need to analyze comparison of customers' new needs, extract those who must modify unavoidable, talk about a little small view: For the functionality in the system, even if it is very special, Also have been revised, otherwise the customer can't go. One project in production management involves the problem of formula, and never said that there can be the same material (but different), and there are many places in the back, although this phenomenon is very small. It happened, but even if you have any customers who can't complete your system, you can only modify the re-test. Also, if the process control must be considered, some problems can make it don't have the head. Management of the production plan to the production plan: First, you can create new, modify, cancel these very common functions, a plan to have a lot of sub-tasks, all from plan to decompose. Later, additional cancellation features: that is, a subscription below can be canceled separately (starting the sub-task of starting production is unable to cancel), this task even if the part is canceled, and the tasks that are not canceled are also completed. Calculate, but its basic information and the tasks that are the initial settles are different. The customer's request is met, and the customer is still very satisfying (including end users). When I want to start the test run, I don't know which genius user thinks about a good demand: the task of starting can be suspended, modify the task information and continue to produce. At this time, we resolutely disagree with modifications, and this system is not unfinished: it can completely part of the task, to create a newly needed task to meet the needs of customers. Of course, the communication is still very technically, usually sing black face, and there must be. The manufacturer generally has a lot about the development of the report. If the customer has the best reference at the time of the previous report, but in many cases, the user does not know what he wants is a stuff, can only say a probably Style and requirements. hair. For those who affect business process reports, they need to be developed and confirmed, and those reports used to statistically analyze can be placed later, and the project teams and customers have re-investive the needed things, and can reduce repetitive modifications. And even if the modification is only the style problem of the report, it will not affect the business.
