In my experience the ever growing fascination with processes comes from the fact that most teams and companies are so young that they have no real experience. They hope to compensate for it by trusting processes to make them smarter as a group.
But that is a fallacy. No amount of process will replace experience. No process will make your group smarter (I suspect the opposite — think teenage mob). and as only experience understands the value of experience, they are doomed to repeat the same mistakes over and over again — often expelling critical thinkers, the only persons who could end that circle of ineffectiveness.
But we also must start thinking not only of our processes and teams of being agile — but our codes and products as-well. Or: "How do we expect to be agile (as in experience «Agility» — the ability to respond to changes rapidly), when we are stuck in huge amounts of code, often described as «Spaghetti-Code»?"
In Swift my answer for this question is «Khipu» — an architecture crafted around minimalism — yet allows for rich DSLs — including spoken English `request(loader, to:.load(.all(.stations)))`.
