Demand changes from the technical implementation party in the software project
Demand changes from the technical implementation party in the software project
The software project will always have a demand change. At the same time, this change is to be the same as the meaning of the sky. This is the most headache of the developer; the demand needs to change, that is, the software's soft word. There is a predecessor's most representative: "Software project is like construction projects, in large-scale construction projects, like building a bridge, and requires the need for bridge 90 degrees after the almost completion, it will neither happen in practice, also Will not be considered reasonable; the original demand is that the road bridge, changes to the railway bridge, will also be seen as two different projects. But in the software, although the work to be done is the same, However, the demand change of the bridge is required, or the demand change of the Scholar Bridge into the Golden Gate Bridge is not uncommon. The user does not understand that it is impossible to achieve such changes in the established project time and investment. " There is also a representative of another textbook: "In most cases, users don't know what they need. They just know that some things are novelty, but they don't know if they really need it; until he sees What you need is, you can quickly get your mind. "
These two sentences can be said to be the most representative description in the software project. Project management in the item, actually developing technical engineering management despite complexity, but truly related to the overall situation, it is the management of demand; it means whether the entire software project work is substantial. I don't understand what is claiming that it is not necessary to manage in XP programming. If there is no detailed description and reliable extensive project success certificate; I think it is just an exaggerated head, it does not explain it. Measures of variation and adaptive movement, and the impact of changes in time / manpower / money budget after changing, it is equivalent to an empty talk.
From the summary of project experience, it can be found that changes in demand are not completely from the service party, and some extent is from the technical implementation. The appearance of the latter is due to the fact that the technical implementation has to bear the responsibility of the success or failure of the business in many cases. In China, the business is fully responsible for the success or failure of the business, and the clear and clear product demand is very small; the reason is that the Chinese software industry is still in a very primitive stage, lacks a third-party software project consulting company / professionals , The market mechanism is not perfect, and the standard product research and development - "technology implementation -" market sales process is difficult to honor. In the launch of large companies like Microsoft (United States), the product planned department is mainly planned, Microsoft also realizes the money of the first user, and then develops sales mechanisms that use products with users; in this environment, The company's sales link is very powerful, and the technical department is just a department that can be achieved by an outcomes (icon to the Indian company).
In China, market mechanisms and actual sales markets have caused either technical departments to complete technical development for the company's business order, like many government e-government projects, this is the whispering project, the most important thing is to let the contract I can't find a flaw, let the parties don't even have a rebate, the more simple and better, the more simple and better, this time, the responsibility of the technical personnel is also relatively light, because the people who have received the money will be topped for you, this It is the implementation of most software projects in China, and therefore, China has existed China's existence of the mainstream of the mainstream. Another possibility is the same as those of the technician and business personnel, and the business is sold by the business. In this environment, due to the lack of necessary technical understanding of pure business people, it is impossible to implement, but the business person seems to have this product demand for sales; (放 放 高 放 高 放 高Movies, remote high-definition-specific medical images to complete the surgery); either pure technicians create products that are completely with the market. For this project, if it is not a masterpiece of the market, it is a probability that the project is dominated by the technician who is sold by selling sales technicians. Whether it is the one, people who host this project have their own tendency to change demand from the perspective, because he is responsible for it. Another possibility of proposing demand changes is a future consideration. Software implementation is in the field of human intelligence factors. Each software person's brain is a supercomputer capable of completing high-speed virtual real simulation. This will make software designers will be more in consideration of current demand implementations. Many foresee conflicts with future work. If these work is probably completed by others, the software people don't have to think too much in the current current, (this is the development of demand factors priority, money? Personnel? Maintenance workload?), But if it is expected in the future These jobs still do not consider themselves with their own departments. If you pay more than double energy, you can reduce two-thirds, usually much more, all software engineers will be achieved more well, and will not die in XP programming It is said that the simplest method is implemented, there is no detail, it is an empty talk.
Another situation in which the technical implementation proposes demand changes is to pay attention to the basic implementation, the so-called focus on the underlying and components. This is exactly the same as XP programming, which reflects a quality concept, as well as high quality foundations that can greatly reduce maintenance costs. Maintenance costs are not necessarily the maintenance of the user's use, and the joint project work is also a maintenance of the previous period. Most software projects actually have an important reason for the final completion of the final completion. It is not good. The achievement of subsequent projects has unlimited extension. This control follow-up project cost, so that the entire project can be controlled, it is also a function method, development object, development of layered technology, and discovers the forward power of the component packaging. Therefore, when the technical side finds that the previous implementation method is not properly realized, the temporary implementation of the zero code is used in the process suitable for component implementation (which requires a wide reuse), in general, it will be placed back to the previous step. So returning to XP programming, if the previous is implemented in a simple method, usually means that the rear refurbishment is greatly increased, which means the cost of retesting and regression testing, because the assembly coupling changes. And if the start is implemented in the form of a component, it does not have the need for regression test. Wherever you are suitable for reusable components, you can achieve simultaneous control time and cost, which is an important aspect of the system analyst and ordinary engineer's work level. It is to know that the development cost of reusable components is two to three times the simple implementation of the unusable use of code. Finally, since the software person in charge in this project is actually the developer of the shutter to make the car, it is a market-oriented product creator, with the further understanding of the product market, generally accompanied by self-product The level of mass grade level is improved, which also constitutes a change in the implementation of software project requirements. Moreover, it is a very important form of variation. Because the technology realization is for market demand, not the face shines. But for a project, the time and budget are always hit by the strong request of the business; as mentioned above, the business side does not understand the Wooden Bridge and the Golden Bridge, anyway, the bridge; Xiaoping House and Jinmao What is the difference in Daxia, anyway, it is a room; don't know what the photo (model) of Jinmao Building and Jinmao Building is different. Anyway, it seems to be a part. In this way, it becomes a technical implementation of the entire project, and if the control of the demand is unresolved, the estimated item will ultimately end in failure.
Resolutely control the project needs, travel a little time and risk cost implementation, which is an effective project measure in the technical implementation. For this project, the actual situation is that the pure business side is proposed, and the demand recommendations are required. They don't have to be responsible for this demand, responsible for the technical implementation, so if the failure is failed, it cannot be blamed on the business side demand unreasonable, they It will also be reasonable to be self-reliant (don't understand, I don't want to understand, but I can only be a suggestion), but it should be considered that the technical implementation is not reasonable for demand. Therefore, it is stupid, which is stupid, which is stupid, is also a performance of project management capabilities.
