Wow, I would love to work somewhere with waterfall requirements-gathering processes and change-control documents. Across several employers, I've seen a lot of m

Wow, I would love to work somewhere with waterfall requirements-gathering processes and change-control documents. Across several employers, I've seen a lot of misdirected work that just makes future work harder. Now of course the response is, why would I want to put up with that bureaucracy - won't it backfire on me? But it shouldn't be bureaucracy, it should be something driven by the engineers with the goal of shipping better products. Which is the problem with advertising agile. When a company says they follow agile, what they often mean is that there are people whose job it is to make sure the agile process is followed, effectively making their own agile bureaucracy. That's what scares people. I want to know that the company is going to get out of the way of practitioners and let us do big-design-up-front if we in our judgment as practitioners determine that a specific situation calls for it.