Microsoft projects are designed to build office buildings, not to develop software. Microsoft Project's fault is that it determines that you want to spend a lot of time focusing on dependencies, so that it is not worthwhile to formally sum up their efforts. Another problem with Microsoft Project is that he determines that you will want to "re-adjust" the Schedule by clicking a small button in the future. This means that he has to reschedule the task and hand it over to different people for completion. This is meaningless for the software. ProgramPersonnel are not interchangeable. If you try to let the UI programmer solve a problem similar to WinSock, he will stay in the same position and waste a week to achieve the speed of WinSock program design. --- From Joel on Software
---This article does not fully represent my point of view, but from the perspective of agile development, the efficiency and convenience of using Microsoft Excel is better than that of Project
