In honour of the 20 year anniversary of the Agile Manifesto, each monthly blog this year will focus on one of the twelve principles.
"The best architectures, requirements, and designs emerge from self-organizing teams."
In order for self-organizing teams to flourish, there needs to be TRUST.
Twenty years ago, teams just didn't work that way. Someone (possibly an enterprise architect) in an ivory tower determined the entire architecture, whether or not they had knowledge of the technology stack or the code base.
It seems there has been a dramatic shift (which is good). But one of the biggest issues today is finding the balance. When are the architects doing too much architecting and when are the developers doing too much architecting? That's not an easy question to answer, but typically more/better collaboration helps.