Print Page   |   Contact Us   |   Sign In   |   Join
AEA Search
AEA Blog
Blog Home All Blogs
Search all posts for:   


View all (13) posts »

An Evangelist Architect’s Journey between EA and SA

Posted By Azhar Zeeshan, Wednesday, May 3, 2017
My first post.... so please go easy on me :) (Tried to see if there is a rule for repost as the following was my post on linkedin) Following are some passages. Throughout my carrier, I’ve been changing hats within general IT Architectural domains, sometimes because of a need or necessity and sometimes because of my own motivational drive. Within Enterprise Architecture and Solutions Architecture with some more specialized roles as Integration Architect and Mobility/Digital and SOA Architect. In today’s landscape, on one end we see EA departments being considered as slow paced difficult to move Elephant, fueled by Agile and DevOps movements and on the other hand we see pains deeply rooted in not understanding the complete Enterprise picture failing to understand long term strategic drivers, and Architecture capabilities reduced to be able to react only for an incremental change. If the Enterprise is big, there often is a miss alignment between Enterprise Architecture and Solution Architecture, and hence just like there is a need for IT to be aligned with business, there is also a need to align Product/Solution Architecture to the Enterprise Architecture. This alignment is also required to increase the Maturity level of the overall Enterprise. I am neither against agile product development nor against traditional EA, I love both. I see a strong need for smart tailoring of the EA process where you adapt to lean and agile principles in addition to a strong need to add a new classification in Architect roles, which I am calling “Evangelist Architect” How do you walk on a think line between agility and stability? Is there a prescriptive path for adoption? Perhaps there is…. And its in smart governance (neither rigid nor too lean). Things that you have not defined yet are open to interpretation so define flexible principles to draw some boundaries, and govern around those boundaries. If an EA is too hands-on as coder then they can be lost in the implementation, if he is too high level they might be just building ivory towers without concrete products. Therefore, and Evangelist Architect is someone who cross the boundaries between a traditional Enterprise Architecture organization, solution and product organization and operational organization, not just as a ceremonial role but actually getting his hands dirty in all organizations on rotation. Some times getting on ground and rollup the sleeves and work with the delivery team and at the operational chains and some time climb up the tower and look at the panoramic picture. An Evangelist Architect understanding all domains of Architecture and rotating around different organizations would be a key maturity enabler in propagation of Enterprise in higher maturity levels of all domains and hence driving the Enterprise as a whole to the higher levels of maturity. I've discussed some possible roles and how this is different than traditional thinking... To read full Article (

Tags:  Evangelist Architect 

Share |
Permalink | Comments (1)

Comments on this post...

Mohan Krishnamoorthy says...
Posted Tuesday, June 6, 2017
I like the way you build on concept of the “Evangelist.” I think the key is to show it in action and to stay engaged with business and business transformations.
Permalink to this Comment }

Sign In
Login with LinkedIn
Sign In securely
Latest News
AEA Events

9/25/2017 » 9/27/2017
IRM UK - Business Analysis Conference, Europe 2017

WSO2 Summit, New York 2017

AEA Atlanta Chapter - September meeting

10/3/2017 » 10/5/2017
IRM UK 3-Day Workshop | Information Management Fundamentals

10/5/2017 » 10/6/2017
IRM UK | Designing, Operating and Managing an Enterprise Data Lake


Join our AEA LinkedIn Group!