Week five assignment-2013551623

What problems do you generally encounter during the software development process? I have summed up the following questions:

1. Not good understanding of user needs, lack of communication with users.
2. The size and ease of the wrong estimate item.
3. Start coding hastily without a plan.
4. Did not start testing at the beginning of the project, dragged it to the end of the project, or did not do any testing at all.
5. Choosing the most cool technology at the moment or having been used by the team to be more mature is often not the right choice.
6. No software processes or methodologies are used.
7. Without a real project manager, let the developer have no planned lead projects.
8. Delay the plan and keep the pressure on the schedule late.
9. No versioning, confusing code base and development environment.
10. Change the development tools and environment at will during the project.
11. Any demand from customers is agreed and demand is endless.
12. There is only one big plan that does not divide the plan into smaller tasks, knowing that big plans are difficult to implement and implement if they are not divided into tasks.
13. Insufficient management of the development team.
14. It is often counterproductive to add more people to speed up development later in the project.
15. Developers do not do unit tests.
16. Once a problem is encountered in the project, put the pressure on the developer.
17. Not concerned about the actual operating environment and hardware conditions of the software.
18. There are no naming conventions and code specifications.
19. Global variables are used everywhere.
20. Encounter problems often do not consult others, but a person to engage in, to the end or not to be solved by others.
21. There is no habit of writing code comments.
22. No validation is done on the input and output data.
23. Without stress testing, there are often more environmental and performance-related problems in the real world.
24. The project internal communication is not smooth, each member just buries oneself to do the thing.
25. There is no good bug management specification and system, often with Word, email, Excel and other text way to track bugs, will lead to the whole project bug management into chaos.

Week five assignment-2013551623