1 balance principle
When we discuss why software projects fail, you can list a lot of reasons, there are a lot of answers, such as management issues, technical issues, personnel issues, etc., but there is a fundamental ideological issue is the most easily ignored, and the software system Users, software developers, sales agents don't want to face, that is: balance between demand, resources, construction, and four elements of quality.
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 natural mental motility, which can be short-term.
Ok: 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 it, but can the investment of funds and time bears the user? In hardware manufacturers, the demand for products is clear. It is tangible, and the quality goal is clear, which can be broken down into various jobs, while software production does not have this feature. In hardware production, production capacity is basically stable, and the impact of the person's dependence and quality requirements are not very different, and the quality of quality in software production may increase or decrease may be on time, input Produce a huge impact, although users do not clearly define quality requirements, software production is the production of quality sensitive types.
Province: What extent?
"One penalty", this is a common saying in China, and he is in line with the 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 high efficiency principle
In four elements of demand, resources, construction, quality, quality, the project decision maker is the first place, and now the competition in the market is increasingly fierce. "The product has earned a day, earning it. More than flowering, so be sure to earn 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 requires a few aspects: Choosing the elite member objectives should be clear, and the scope must be clearly communicated in time, and it is necessary to organize members to upstairs.
3 Decomposition principle
"It is simple, and all breaks" is a non-fancy door that solves complex problems since ancient times. For software projects, you can divide a large project into several small items, divide the process of lengthal projects into several Clear stage.
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 principle
Among a large software company, there is a very personal project manager. The project manager rarely talked about what management theory, and did not see any obvious management measures, but he continued to make a lot of scale. Software projects, and the application 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. In the above method, the personal ability of the project manager is very high, and we need to have a mechanism for real-time control project progress, relying on a set of specifications to ensure the progress of the real-time monitoring project. Such as the Microsoft's management strategy is strong? Quot; daily build ", this is indeed a good method, that is, a system compiled link will be performed, check the progress, check the interface, discovery progress through compile links. Question, everyone encourages each other to supervise each other.
Real-time control ensures that the project manager can find problems, solve problems, and ensure that the project has high visibility and guarantee the normal progress of the project.
5 classification management principles
For different software projects, its project goals are very different, the scale is different, the application field is different, the technology route adopted is also very different, and thus, for the different characteristics of each project, the method, management of its management The focus should be different. Just like the ancients, "teaching", "symptomatic medicine". For small projects, you must not be able to do like management big projects. For item development, you can't do it like a project of management system integration, the project manager needs to develop different project management according to the characteristics of the project. policy. For example, the following table is the principal of project management for an application company:
In this case, the project is divided into order class items and non-order class items. The non-order class item is a standard product project by the company to develop a standard product according to the needs of the market, and the order class refers to a specific customer customization software. The project, the order of the order class is divided into three categories of the company, department-level, personal level, and non-orders based on the size of the estimated workload according to the estimated amount of work, according to the estimated workload. The estimated workload is more than 720 people, with more than 360 days of days of Class B, 360 people below the Class C. The focus of different types of project management is different. From the completeness of the procedures, the planned strict layers, the complete layer of the week, the strict layers of the standard, and the real-time performance of the tracking, whether the stage summary is performed, whether the project Cost, whether it is strictly for phase review and other aspects to ensure the feasibility of management.
6 Simple and effective principles
In the process of project management, the project manager often has to complain about developers "too much trouble, waste time, no use", this is a very common phenomenon. Of course, such complaints should be analyzed from the two aspects. On the one hand, there may be no understanding, or inverse anti-psychological conditions, on the other hand, on the other hand, the project manager also refers to: Is the management measures I have been simple and effective? It is not to engage in academic research, there is no perfect management, only effective management, and project managers often try to block all loopholes, solve all problems, which is this ideal, which will cause the management of the project into a misunderstanding, make self-binding, Finally, valid management cannot be implemented, causing the failure of the project. 7-scale control principle
The principle is used in conjunction with other principles mentioned above, that is, the size of the project group is to control the size of the project group, there are too many people, the number of people is more, and there is more channels for communicating. The complexity of management is high. The manager's requirements are also high. In Microsoft's MSF, there is a clear principle that the number of people to control the project group should not exceed 10 people. Of course, this is not absolute, and it is also a big relationship with the level of the project manager. But the personnel "Guise is not expensive", this is a basic principle, this is the efficient principle mentioned above, the decomposition principle is complementary.
