This is a forum's post (http://www.mypm.net/bbs/Article.asp?titleid=492&ntypeid=5005), I feel very good, very touching, sorting. Post Topic * How to avoid software project on-site development?
Question: Our company has a lot of software projects, but how to avoid on-site development there is no good treatment, even though everyone knows how many drawments in the scene. Is there any good way to ask you?
Papachong: In the XP limit programming, the development is a good thing, of course, customers need customers to communicate well, in addition, suitable for the development of 2-10 people in the small team. ENJOHNY: Industry software, because of the issue of version control and reasonable use of human resources, you should maximize on-site development. But how to avoid it? Jennie: This depends on your specific customer requirements.
The method I usually use is to tell customers: Our development needs XXXX development environment, can you have? We encounter technical issues to organize the company's technical committee to discuss, we can't do our relatively closed test environments at the scene, all kinds of test equipment and use cases Are you here? ......
Listing a lot of customers cannot meet, but affect the development, let customers choose their own
If the customer is too persistent, it is not good.
This method is better than 80% of the stage of development. If it goes to the last line, it has not been used in Zhjohny: Jennie said that it is very correct if the customer explanation is very correct. On-site development is mainly caused by two factors, and there is a customer reasons. What I want to know is that there is no good management approach to solve on-site development due to your own causes, is the main problem only in the management of project management? Cabbage: Avoid on-site development, then the requirements for research on demand will be high, and the changes in user demand cannot be followed in time. ZHJOHNY: Can I summarize two aspects: 1. Client's question: The customer always feels that the developer is not present, the successful confidence of the project is insufficient. 2, software developer's question: Bluestone: The customer's demand is always changed, which is always not finished, so the on-site development is an error. Our project was developed in June. It plans to end in July. Now it is still in development, most of the functions have been different from demand. Zhjohny: If we can develop, we feel we feel around them. (For example, a regular weekly report, a complete plan, plan step by step, and submit a milestone or phase document on time), then the customer will not be strongly demanding on-site development; if our project management level and software development level High, we won't not complete the high quality software as planned, and you don't need to bring the source code to the scene. I am doing a project, I am going online, it is doing this. We are basically satisfied, and we have no on-site development. Focuser: On-site development is the original practice of software development :) The main reason for the on-site development is: unfamiliar with the business of the software project to be developed, can't get a clear demand. Generally, it is a new field of the company. Only to the customer's progressive demand and make custom development. Measures: General customers don't care, you are on-site development or development in the company. Convincing customers do not develop easy in-site development, strengthen system analysts to investigate the needs of customers, and do a familiar industry is a way to resolve on-site development. Our company is rarely not familiar with the order of the industry. ZXK91: Our company projects have taken a version, a project group to the customer's on-site customization, integration test, online. I also think "(such as a regular weekly report, a complete plan, planning step by step, and submitting a milestone or phase document on time)" Our company's project management is still in the comparative primitive stage. If the project management is good, it is the visualization of the project. It is really beneficial to manage and standardizes BJYR: feeling, the more good business is, when talking about the single word, in addition to talking about the company's industry solutions, it is necessary to do it. A lot of second development in order to highlight costs and prevent customers from overburning the price. During the implementation, try to reduce secondary development, even if the development is also trying not to go to the customer company. CAMER: XP method emphasizes site customers, in fact, it can also be understood as on-site development. If there is a good organization, the site development is not bad, but the XP general practice is to bring customers to the company, cooperate with the development team, because in customers In the environment, there is no support for the company's development environment. .
LOOKMEZH: If you find the customer's representative, you can guide him on-site. However, general customers only express some demand for functions. The development process is still better by RD itself. After all, customers are too many participation, will result Endless demand. In addition, be sure to know which customers have the right to decide, which customers have payment rights. Yxqselect: I think if the on-site development is not the key to the success or failure of the project, whether the overall project group is stronger thanks to this project! As long as you can get the needs, the development site is determined according to the project, and if the customer can provide excellent on-site development conditions, it can also be solved on site. Wuzh: Customer demand design and information design should be carried out synchronously; the profile must be communicated and communicated on site. Need mature customers, smooth communication, reasonable software development mode Mkopen: Software is trying to do, strive to configure software on site, not developing software. This is the key to success. Zhjohny: Agree to the point of view upstairs. For mature industries, you can use it as much as possible; it is important to be unfamiliar with industry, design model thinking. Based on our national conditions, on-site development, the success rate of projects can be used to participate in the project, and they can get their identity and support ... Camer: On-site development is more common, but on-site development It is not easy to control the rhythm, but also lacks the seriousness of change judgment, after all, the internal R & D environment is much more developed. . . I still want to avoid the development rate of the scene :) Talk about your own opinion: On-site development has its own irreplaceable side, especially in some special enterprises (such as this industry is very small, not comparability) Everyone is not very familiar with its business; or the company has recently involved in experience in this industry. If the previous business research, the details of demand analysis can be developed in the company, but the actual situation is often the preliminary demand, and it is generally impossible to do very fine, and very close to the user's demand: In the beginning of the stage, customers can not be able to Describe the things you want, at this time, you must confirm the business scope of your business to complete the version, give you a priority to each business needs, determine which aspects are the most concerned. Now some companies have themselves. Information center, if you want to get real needs from them, huh, you can be miserable: P, I have lesson, and they are not very clear about the actual business, and it is in the enterprise. Cannot require actual users to complete their business in their designated procedures, so they must talk to actual users (must). There is a simple but very useful approach to verify that the current design does not deviate from the expectations of the customer: do the interface original map, attached to the system detailed design manual, and the user discusses the business process and the interfaces in each process. The advantage of this is to give the user an intuitive understanding of the system (although the system is still not existed), helping the client discovers the problem in the system, and the advantage of doing this is a kind of customer, the customer, Demand restrictions are within a certain range, will not mention some messy requirements. You can send the project's development plan to the customer, regularly report the progress, such as available version (even if only some simple features) can be trial. In the process of development, if there is a significant problem (such as the previously designed business processes or any abnormal occlusion can cause the system to not perform properly, how to do special processing for exceptions and exceptions) must be Communicate, make a successful prevention or remedy or limit. No matter what you do, you will have such a thing in the scene, remember a sentence: the customer's needs are always changing, and the demand will end.
