Successful principles of software project management Ren Yelin (reprinted from China System Analyst) 1 Balance Principles can list a lot of reasons when we discuss software projects fail, there are a lot of answers, such as management issues, technical issues, personnel issues, etc. However, there is a fundamental ideological issue is the easiest to ignore, but also the user, software developer, sales agent, the most demand, resource, construction period, quality four elements balance relationship problem. Demand defines "what to do", define the scope and size of the system, and resources determine the project's input (people, money, things), defined the delivery date of the project, and the quality definition of the system is good, These four elements are have a balanced relationship. If the demand is very large, it is necessary to complete a project under a short resource investment, high quality requirements, which is unrealistic, or need to increase investment or engineering; if the demand is defined Clearly, the resource is fixed, and the quality requirements for the system are high, and may be extended during the demand. One error is the most important error between the balance between the above four elements is to advocate "How fast and good provinces", "how fast, good provinces", how ideal realm? The more demand, the shorter the construction period, the better the quality, the better, the better the investment, which is the most common slogan of users. Many: Does demand, better? The basic principle of software system is "global planning, step-by-step implementation, step by step", more demand, but demand must be priority, to distinguish the main contradictions in the company and the secondary contradiction, according to Pareto's 80-20 In principle, 80% of the issues in the enterprise can be solved with 20% of investment. If you have to be big, sorry, your 20% secondary problem is to invest 80% investment! This is precisely a lot of software users can't endure. Fast: Can you get up? "Fast" is the user, software developers are hoped. Traditional enterprises emphasize the turnover of funds, and the software companies emphasize the turnover of people. Developers should finish a project as soon as possible to do another project. By fast startup project, end the project to undertake more projects, come Profit. But "fast" is not subjective, and the system can be done based on the situation of resources, how much demand is required for demand. After all, it is necessary to write a line of code. His workload is objective, it is not? Quot; people have more bold, there are many big production spirit to complete the short-term completion. Good: What is good software? The "good" word of the software system is the most difficult definition, the most difficult measure. "Let the user satisfied" is the highest goal, you can do, but the investment of funds and the time of investment in the user can bear it? Production in hardware In the enterprise, the demand for products is clear. It is tangible, the quality goal is clear, which can be broken down into various jobs, and software production does not have this characteristic. In hardware production, production capacity is fundamentally stable The impact of the person's degree of dependence and quality requirements are not different, and the quality of the quality in software production may have a huge impact on the work, and the user does not clearly define it. Quality requirements, so software production is the production of quality sensitive models. Save the province: What extent? "One penny and one stock", this is a common saying in China, he is in line with value law.
Party A hopes to invest less, Party B wants to reduce his production cost, and then the time to Baishibei can only save this, and Party B will lose money. The balance between these four elements is the performance of software users, developers, and agents, otherwise the success of the system has lost a solid foundation. The primary goal of enterprises to implement IT systems is to succeed, not fail, business can tolerate small success, but not necessarily tolerate small failures, so it is necessary to truly understand the balance between the above four elements to ensure the success of the project. 2 Efficient principles In the four elements of demand, resources, construction, quality, many project decision makers are the first place, and now the competition in the market is increasingly fierce. "The product has earned a day, and earn a day. It is better to earn more than flowers, so I must make more ", based on such a concept, software development is increasingly pursuing development efficiency, everyone seeks more better solutions from technology, tools and management. Based on efficient principles, the management needs of the project will consider from several aspects: to choose the elite member objectives to be clear, the scope must be clearly communicated, and the principle of incentive members will be integrated, and all breaks. "It is a non-legal door that solves complex problems since ancient times. For software projects, you can divide a large project into several small items, and divide the processization of the cycle into several clear stages. The higher the project, the higher the management personnel of the project group, the more people involved, the more people need to coordinate communication, the longer the cycle, the developer is also easy to fatigue, and the big project is split into several small The project can reduce the requirements of the project management personnel, reduce the management risk of the project, and can fully deceive the power of the project management, fully mobilize the enthusiasm, the goal is more specific, easy to obtain the results of the stage, so that developers A sense of accomplishment. A product development project code for the author's supervisor is SB. The previous period has put into 5 people to do demand. After more than 3 months, after entering the development stage, 15 people have been invested, and time is 10 months. 3 closed development, in the process experienced the demand cutting, the development personnel change, the technical route adjustment, the pressure on the project team is great, everyone is exhausted, the product is available for time to go to 4 months. A very deadly lesson summed up after the completion of the project is that the project should be demolished into three small projects to do, stage version release, to alleviate the pressure on the market, reduce the frustration of project team members, and improve everyone Morary. 4 Real-time control principles In a large software company, there is a very personal project manager. The project manager rarely talks about what management theory, and has not seen any obvious management measures, but he continuously makes multiple A large software project, and it is very good. The author has been very strange why he can do such success, after careful observation, finally discovered that his management can be summarized with "tightening", you must carefully check the work of each member of the project group, from the software demo To internal processing logic, data structure, etc., meticulous, if there is a problem, can not be resting. It is under this simple measures, supporting him to complete a lot of projects, of course, he is also quite hard, usually in the early morning to rest. We don't have to promote this practice, this measure has his problem, but this practice shows a very simple truth: if you don't have a better way, you have to work hard, the progress of the real-time control project, Place the progress of the project is completely under your control.
