Reading Sumtec's continuing thinking, feeling a lot, just write something. Sumtec talked about a problem in his Post, software development should be customer-oriented, not technical-oriented; in other words, it is to do a customer-oriented software development. The customer is a person who pays a single product or project, our hard work, and finally revert to how much RMB, the key is the customer. Development of customers, can maintain good relationships with customers, reduce rework, reduce risks, and ultimately increase development efficiency, and ensure on time. So how do you do your customers' software development? I think it is necessary to grasp these points: 1. Meet the needs of customers as a team common, and those who have different division of labor within the project team define their own jobs as their own success. The success of the demand person is to capture the needs of customers as wide as possible; the success of the system architecture designer is to design a stable adaptive architecture; the success of the development engineer is to prepare code to meet the requirements of the system design document; test engineers success It is guaranteed that there is no known bug ... These goals together, this consisters, but not guarantee that there is a common goal over the group. However, when the demand for customers is accepted and agreed with all the members of the team, the disputes on many small issues will disappear, because everyone knows that everyone is working together for a common goal; This can also build cooperation and trust, which is much larger than the sum of everyone's skills. 2. Selecting the customer controllable software life model SUMTEC talked about the waterfall model brought various problems in the development. In this way, the waterfall model is not suitable for customer development. Because in front of the waterfall model, only the whole model is finished, the customer can see what he wants; in other words, the customer is not visible to the project throughout the project cycle. Unacceptable project cycle gives customers a feeling of losing control of the project, which will cause many problems, such as progress plans, such as demand changes, and so on. The stage delivery is usually a popular model. In this way, the client has an intuitive understanding of the progress of the entire project. Many changes to progress plans or further demand will be discarded by customers, because the customer knows, what consequences will be brought to the project. At the same time, after each delivery, you can overkill and maximize customer needs. 3. It is very important to figure out who is very important! Typically, customers will send representatives to make a demand, monitoring items. However, in many times, this representative cannot make decisive decisions on the project! After him, there is a bigger leader in the command. This is also in the project, and the customer delegation proposes a lot of unreasonable requirements. In the project launch phase, it is necessary to pass a variety of means, in depth, then in the project, do a good job in the report of the behind-the-scenes report (even if it is just the macro problem "is not more a lot of). 4. Accurate capture customer demand customers' demand is often very vague, even if it is proposed, even a draft, it is not a draft. However, when customers see what is developed, usually thinking will become active and will put forward a lot of further needs. The developer's demand personnel should be good at using this, use the interface prototype, induce customers to make more demand. 5, control the needs of customers' needs scope customers on the ceiling, and our products are underground.
