What is the difference between software project management and general project management

Software project management refers to the management of the software development process, the source of which is the project's project report and development mission statement, and the result is a deployable software system.

Software engineering is a general guide for software development to follow, and is mandatory for project managers and developers, and is generally taught as a course, with ISO 9002 and CMM being the guides we often use specifically.

IT project management is more extensive, not only to consider the software system, but also involves network infrastructure design, hardware and software platforms, operation and maintenance management.

The commandments of software estimation

(1) Don't strive for perfection: just as no one can predict the future, don't attempt a perfect result if it hasn't already been done. What's more, estimating too accurately, on the contrary, will lose the space of flexibility.

(2) Don't estimate to meet the budget: If the budget for this project simply can't accomplish 100% of the task, then don't let your team compromise. Correctly reflecting the objective status quo is not only a way to fight for what you deserve, but it's also a prerequisite for getting things done.

(3) Don't arbitrarily cut estimates: There are many bosses who like to take the estimate submitted by the project manager and cut a part of it without thinking about it. This is an irresponsible practice, if you want to cut must have a reason.

(4) Objective estimation, not greedy, not steal: just as the boss can not just cut your estimate, you also can not be in the estimate, greedy or steal. Being greedy will inevitably lead to waste, and cutting will inevitably lead to shortage. I'm afraid that neither of these results is the work of a competent project manager.

(5) Objective use of past experience: the experience of past estimates is of course a valuable asset, but if the wealth is used in the wrong place will become garbage. When using experience, pay attention to the difference between present and reference experience. Don't forget that many concepts change over time as

technology in the computer field is updated.

(6) Don't use the customer's goal as the result of the estimation: the customer is God, and the software company must try to realize the customer's needs. But we want to achieve is a reasonable goal, and moreover can not be in order to accomplish the goal to pile up the numbers, so is not the cause and effect reversed.

(7) do not hide the uncertain cost: software development in the existence of potential risks, is a very normal thing. Now the risk comes with a potential cost, e.g., suddenly a programmer leaves, causing the work progress road behind. It is impossible to estimate any of the possible scenarios, but it is our responsibility to list some of the key aspects that may occur.