Demand or demand

All software development isBuilt on demand,Development that is out of demand and out of line with actual needs has no commercial significance. Many mature software development processes place great importance on requirements. Traditional development models, such as the waterfall model, require the compilation of very standardized software requirements instructions; in the agile development process, for example, XP, it is more important to establish a virtuous circle of information between customers and developers through high-quality communication during the development process, and view the needs from a progressive development perspective. Different development modes may have different ways to deal with requirements, but all of them are based on the same attitude: demand is the primary focus of software development, and all development that deviates from the demand is nonsense. The process of software development is the process of constantly building a system to meet customer needs, and the process of constantly using information technology to solve user problems. The degree to which the system meets customer needs is an important standard for measuring system quality. Our goal is to solve practical problems for users.

It is difficult for an organization to find an effective way to adjust the attitude of members through regulations and regulations. Attitude is precisely an important factor to exert the potential of a person. An organization can ensure project quality through development models and business processes, but it is difficult to maintain a positive attitude towards members through management channels. attitude is an important cornerstone of project quality. Many people do not realize that they may not treat their needs correctly.

People who believe in technology are easily lost in the vast technological ocean.The use of various architectures, cool promotion of their own programs with strong scalability and robustness. Actually, what the customer needs is a simple-and-easy-to-use cow knife. You have a cool-and-die cow knife. What the customer needs is a wall clock that can accurately indicate the time, you made a golden watch. What customers need is a chair that can sit comfortably asleep. You made a massage chair that can automatically rotate 360 degrees, massage and massage around the clock. It is correct to attach importance to the technology itself, but it is necessary to pull out the target if we despise the demand. The technology is used to solve the problem.

People are changing, and the market is changingOur service industry is also changing. What the philosopher said is that the only thing that remains unchanged in the world is change. How can we not add dynamic configuration to the permission system if we require low prices for ending goods in the vegetable market? We asked iron Xia 3 to add more Chinese faces. How can people not request that the reimbursement form with less than yuan be automatically approved? Many changes are caused by changes in the customer's understanding of the system, changes in developers' understanding of the business, or changes in the industry's big environment after the system is improved. If you stick to your opinions, how can we keep up with the times when we are unwilling to accept changes in demand? There are indeed many unreasonable demands. If you know where the unreasonable is, you should make it clear to the customer and tell him that this is impossible and where changes will lead to increased costs, why are you saying that the customer has no reason to keep it difficult for you? I always think that software is a service industry. Do you dare not take international service attitude? Complaints do not help, so we are better off solving the problem.

A cook can get the favor of the masses, not because he is more skillful, but because he can make dishes that suit the tastes of the masses. A programmer is able to live, not because of his strong technical capabilities, but what he makes can solve user problems. To put it bluntly, the goal of software development is not how you design the architecture, but how complicated the design model is, but whether the things you develop have solved practical problems for users; it's not how nice you are to develop, but how nice users are to use! Do not define the target incorrectly. Do not lose your way in the process of growth.