| Fair enough. Agile was a response to heavy process. And systems where people's jobs were all about adding more process to the already heavy process. Process hell. In the couple of decades since little "a" agile really got adoption: 1. many people have not seen v-model or spiral model and their attendant process wonks 2. agile was turned into Agile and became a way to micromanage, first micromanagement with no rules, then later, more and more "Agile rules" So now we have SAFe, which is sort of the worst of both worlds: micromanagement plus a smothering blanket of process. But back to the point . . . the intention was never to create the ultimate system that was totally amazing but only when staffed with complete experts who were also psychically connected. The intention was to ditch process hell. |
What has changed is that the business expects to be able to push new features through quickly with faster releases. In the past, it took a long time for the business to get changes made.
Part of that I think was that highly technical departments had more control over their output and schedule. It was all mysterious to everyone else. If the business wanted to do something, there would be meetings and documents and analysis and approval decisions. It was hard, it was complex.
As technology has become commoditised and less mysterious I think the power of the techical wizards has waned. So the business likes the idea they can just ask for stuff and it gets released fairly quickly and with much less ceremony and negotiation from their perspective.