Software development management and control
PS: This article is summarized by the semiconductive combination of foreign materials and its own experience.
Please ask all netizens to criticize
Semicon
Software development is a complex work, and the management and control of software development.
Exhibition a special discipline: software engineering. There are many national standards and
International standards. But the software engineering is more from the perspective of technology to standardize software development.
Management and control, this article tries to explain some software development from the perspective of managers and practices.
The basic principles of management and control should follow.
Two extremes often appear in the software development project: one is created new
Productivity and quality record; one is completely disaster, not canceled is dragging
Extension long. By refining these successful and failed examples, software projects success or loss
The root cause of defeat may be clearer.
Before discussing these reasons, let's first define something can be called lost
Losing software project.
1. Terminate due to the cost overhead or plan to perform timeout.
2. Complete the scheduled time or cost exceeds 50% of the original plan.
3. Due to quality or performance causes and customer disputes.
Below we will arrange five wrong practices in order of its influence size.
Error 1: Historical data without software development
Historical data lacking software development is the key to the failure of most software projects,
This conclusion may make many people feel surprised, but the fact is the case. No one can
The historical data developed by software will make project managers, programmers, and customers for software development.
The process lacks a clear understanding.
Suppose now you are managing a software project, and this project has no one
Companies are completed within 36 months. As a responsible manager, you have made a relatively fine
Responding to the estimate, then tell your customers and your hand, say you think this project
It takes 36-38 months to complete. However, there is often such a situation: your customer and
The prequarter requires time to compress the time to 18 months. On the one hand, I hope that the software is put into use as soon as possible.
In the air, on the one hand, I want to compress the project time as a bargaining.
Code; and programmers may be too confident, on the one hand, ending the project as soon as possible can make them
Earn more money. At this time, there is no rider of reliable software development on your hand.
According to their pressures, you agree with the 18-month plan, so a disaster begins.
At the beginning of the project you found that the plan was delayed, so started to the programmer
Stress, ask them to speed up the progress, the programmer has to put other indicators for the pursuit of progress
On one side, these problems continue to accumulate and the project manager is in the drum. In the item
These quality problems will continue to expose, and they are related to each other and difficult to solve.
Even some are the problem of system design. At this time, I found a lot of modules to push down, 18 months.
Complete the plan to become a heaven. Although it is just a virtual example, it is actually
This situation is all. The key to the problem is that the historical data developed by software is reflected.
The scale of the software development team, there is no such ruler, it is unable to develop software
Cheng has a clear understanding.
Error 2: Do not pay attention to the use of software cost valuation tool software and plan tool software
Most of the domestic software companies are in the "more than a dozen guns, a hand workshop"
At the level, after the project is undergoing the project development, it is often a few backbone.
Take a general estimate of the cost and progress, and then start entering the implementation of the project. This party
The law has a significant subjectivity. Estimation and make a comparison in making precise software costs
Many factors need to be considered when a real project development plan. For a large software project, use hands
Work fees are estimated and planned to work. About 50 companies now
Industry software cost estimation kit and approximately 100 commercial project plan kits, use them
Accurate estimates more likely to succeed more than manual estimates. Common software cost estimation tool
The software has Checkpoint, Colomo, Estimacs, Price_S, Slim. Common project tube
The software has MS Project, Primavera, Project Manager * s Workbench,
Timeline. Combine these two tools software can be supplemented with each other, help managers to dismiss
Customers and programmers are unreasonable and can accurately control the implementation of the project.
Error 3: Ignore changes in the user's needs
Although the initial user needs are included in the demand manual while signing the development contract,
However, it is unlikely that users' demand for users throughout the development cycle is not very possible.
There is no mature experience for how to apply computer software for users. Proceed
The demand for users will continue to grow, and the needs of users will increase at the rate of 1% per month.
Add, if a project is completed within 12 months, there will eventually be more than 10% of the changes, and if the project lasts for 36 months, it will eventually increase 1/3 of the function. 1% per month is just an experience data, one
Users who lack computer application experience will change more frequently and increase his requirements. therefore
Be sure to consider changes in user needs during the cost and time estimation of the project. A comparison
Wise method is to hook the changes and economic interests of users in the development contract, such as
If the user increases or changes the needs, the delivery date of the software can be postponed, and the cost should also be increased.
Error 4: Ignore the progress of the supervisory project
So far, the software industry has no standard test standards for project progress. One
A relatively clear scale is the progress of the project with the software features that have been implemented. But this part
Whether the law is the most scientific measurement, it is still not convicted, after all in a software project
Software features are just a major rather than all tasks. So a project manager is monitoring project
Do not only pay attention to implementation software features, but also care about document, test, technical support.
factor. In actual work we often hear the manager or programmer saying this: "The project has
It has been completed 90%. This conclusion has obvious subjective, and an excellent project manager should not be
The judgment under the hand is confused, but should be in-depth inspections in accordance with a more objective standard.
Error 5: ignoring design review and code review
Many programmers are used to working in such a way: do not want to do. They are more concerned about every day
How many lines of code can be written, complete a few modules. In this attitude, they are very unwilling to review
I am used to correcting hidden errors in the software test phase. But design
Check and code review has been 30 years of application history in large software projects, and has been certified
The review of the design and code preparation phase is more effective than software testing, some
The test data indicates that the error found when the design and code review is in the same workload software test
Twelfance of the mistakes found.
in conclusion:
Software development is a work with certain risks, in order to minimize risks, in the project
The implementation of the project manager must strictly supervise the progress of the project, and the trainee who is unwilling to review programmers
It is used to correct. Project managers must provide historical data and auxiliary tools developed from software
Accurate estimates in the data, which should be considered for changing users
Ask to leave a wealth.
Excerpt from: bbs.net.tsinghua.edu.cn
