Ten Causes of software project evaluation failure (excerpt)

1. the boundary of the project scope is not determined.

How do you estimate the time required for a project if you do not know the project? It is difficult to find out how a customer can accurately say how their system should run.

 

Almost all of the large projects I participate in require the system to be "flexible". In other words, the customer wants the system to handle everything that needs to be done in the future, however, they cannot tell exactly what functions are needed. Therefore, "flexibility" is not a system requirement because it is a vague concept.

 

2. Development time from non-ProgramEmployee Estimation

If you are not a programmer, do not guess the time required for development. If the project manager makes a fictitious estimation like a novel, the project is doomed to lose control. The estimation of the development time should listen to the opinions of the programmer.

 

3. developers' estimation is too optimistic

Developers generally only consider the coding time. In addition, the development speed and efficiency of each person are different. Many developers are too optimistic about how to estimate the development time, they often ignore factors such as project management, requirement sorting, discussion, absence, and computer problems.

 

 

4. Inadequate anatomy

For an independent feature, you need to be careful if the estimated development time exceeds one week. Such features should be further subdivided so that developers can analyze more complex problems in more detail.

 

5. estimate the time to use.

If a programmer is given five days to complete a task, it will take five days for him to complete software development.CodeCan be improved. If the developer completes the task in only three days, they will use the remaining time to adjust the code or simply do other things.

Unfortunately, this will cause the estimated time to be the minimum time required for development, and the actual delivery time can only be further postponed.

 

6. Many developers! = Fast development

A project that takes 100 days cannot be completed by 100 developers in one day. The more developers, the exponential increase in project complexity.

 

7. Change Project Scope

This may be the biggest headache for every developer. Sometimes it is the rise of the CEO to modify or add features at the customer's requirement, if you think a function is cool, you need to add or modify it.

 

8. Fixed Estimation

Estimation should be a continuous process, which should be constantly updated with the development progress of the system. programmers often think that they can make up for the elapsed time, but few really do it.

 

9. Forget the test time

It is unrealistic for developers to test their own code. They know how code works, so they subconsciously use a special test method, testing and debugging take up to 50% of the development time.

 

10. The estimation is too dead.

Non-programmers rarely understand the complexity of software development, so few projects are not forced to delay, there are many factors that affect the progress of the project. If some maneuver time is not reserved during estimation, in the end, it will only be an estimation of failure.

Development delay will lead to a high-cost chain reaction. Unfortunately, if something goes wrong, everyone would like to blame the programmers at the bottom, which will be detrimental to future projects, because programmers will take a long journey of wisdom, the next time they either refuse to provide estimation time, or they will exaggerate the development time.