By Eva Johnson
Several recent articles by Jason Bloomberg on Forbes have put the spotlight on the division between Enterprise Architects and the Agile Movement and have highlighted the necessity of bringing these two sides together. Towards the close of his article entitled Scaling Agile Software Development for Digital Transformation, 
Jason urges digital transformation professionals to choose their tools with care, the following article is for those Enterprise Architects that wish to go Agile and become Agile Enterprise Architects (Agile EA) and practice a new type of Architecture, Agile Architecture.
One of the biggest causes of aggravation between Enterprise Architects and Software Development teams is caused by the legacy of other, older software development models where the design is always up front vs the design as you go of Agile development. This typical idea of Enterprise Architecture would provide the Enterprise architect a command and control position, a incompatible role within an Agile Development team, and therefore a role that must alter radically to become part of an Agile team (will come back to this at later).
For Agile Developers reading this, lets be clear, – you can’t Scale Agile effectively without an Enterprise Architect, your business needs one. Many of you might be wondering why at this point considering the various frameworks for Scaling Agile such as the Scaled Agile Framework, designed for scaling Agile with developers working in SAFe teams, – this provides your business with architecture right? Wrong!
Read the entire article at http://intland.com/blog/agile/enterprise-architecture/a-scaled-agile-approach-to-enterprise-architecture/.
