Interesting introduction/preface about solving the gap among different actors of agile world.
One of the big doubt (imho) is about the gap of enterprise architects into agile, many times I've seen they are not necessary anymore (because we're agile now), or only seeing as Software/infrastructure Architect, but not agile.
Germán, that is a great observation. You are right, many Agile teams say that they deserve special treatment or that things that were once necessary can now be dismantled because "We're Agile!"
We even have a term for this in our book. It is called "Agile Illth." Illth is the opposite of wealth. Agile teams can cause good things to happen (wealth), but they can also cause a lot of bad (illth) if they are not careful.
For us, enterprise architects will always be necessary. However, as we mentioned in another thread, architects need to be true coders. They should play guest roles on teams every so often, living inside the decisions they've made as architects. "PowerPoint Architects" are not very useful. We have several recommendations for how Agile teams can "play nice" with enterprise architecture groups, and also how the enterprise architects can themselves become more Agile.
You can tell this is an important topic for us. Thank you for the question.
permaculture is a more symbiotic relationship with nature so I can be even lazier. Read tiny ad:
Devious Experiments for a Truly Passive Greenhouse!