And then the clients aren't usually changing half of the project as you go.
Or ask you to start "tailoring" before they know whether they want a leather bomber jacket or historical ball dress.
Of course, there are other issues at play. The software development project may blow up when unexpected issues pop up with the design or implementation. That is where the ideas behind software engineering come into the picture. You don't build a bridge or a dam without having a clear specification and you don't create that specification without doing considerable research first. (You also don't throw a team of junior engineers at the problem, expecting them to know every facet of what has to be studied and how to design it.)