The other day I suddenly realized why I dislike software processes so much. It's because how you build a system and what the system is depend on each other. Eac

The other day I suddenly realized why I dislike software processes so much. It's because how you build a system and what the system is depend on each other. Each needs to evolve as you learn more (and as the team changes). Software processes, by definition, predefine the how. That kills the feedback loop and hinders projects from evolving. The same reason why waterfall is a mistake -- because it treats as fixed things that need to change -- applies to software processes in general. Software process is just waterfall at the project level. Software projects are no less unique than software systems, but we would laugh out the door anyone who claimed to have a metadesign for all programs.