“Enterprise Architecture (EA) is an immature discipline and possibly getting even more immature. As the scope of EA extends beyond the areas that IT-centric efforts are prepared for (data, app, infrastructure), the competency, credibility and effectiveness of an EA team may decrease. However, there are a variety of ways to increase these characteristics for EA teams, regardless of the stage of maturity in which you may find yourself. “
That is the theme of a presentation, entitled “EA Profession: What’s Changing and What’s Not?”, I will deliver at the upcoming IASA ITARC event in Austin on Thursday, February 4. The discussion will feature a lively discussion about my assessment on the state of the EA profession, what I see going on in the industry that helps and hinders the evolution of the EA profession, and what else to expect in the future.
If you are in Austin and plan to attend, please let me know. I’m always interested in talking with other enterprise architects, those that aspire to the role, and IT Leaders interested in having an EA function in their organization. There will be plenty of opportunities for discussion and Q&A, including at an evening reception.
The International Association of Software Architects (IASA) is the premier association focused on the architecture profession through the advancement of best practices and education while delivering programs and services to IT architects of all levels around the world. The IT Architect Regional Conference is the first event in Minnesota to address the pressing needs of IT architects today. There are 12 seminars and two tracks separated by specialty: Enterprise and Fundamentals. Architects of all levels can take their skills to the next level.
Posted by George S. Paras 

Top-Performing EA Teams – A Panel Discussion
March 30, 2011I had the opportunity last week to moderate two panels at the Troux Worldwide Conference. The first panel included EAdirections’ Tim Westbrock along with Mike Walker from Microsoft, Aleks Buterman from SenseAgility and Paul Preiss from IASA. The theme of the panel was a general discussion on characteristics of top-performing EA Teams. To begin the conversation, I asked each panelist to describe what a top-performing EA team meant to them. What I had originally believed to be a softball question that would show the breadth of issues and perspectives on EA turned out to be more controversial than I had expected.
The panel became caught up in the role of EA and the role of IT architects. Unfortunately, the conversations became focused on the differences in the roles instead of how they work together, diving too far into a differentiation of the “primary” roles and skills of each. It revealed some of the confusion around EA and shone a light on many of the issues that practicing enterprise architects must deal with on a daily basis. What I had hoped would be a conversation addressing how the EA function must be multi-purposed, strategic and tactical, business and IT-oriented, and with an eye to both short and long-term value delivery became overly focused on narrower perspectives. We had a few rough spots as we worked our way through the session, but luckily we ended well. We landed at the recognition that while the roles are different they share some common skills and, after all, they should be collectively working to achieve positive results for their organizations. Individuals in both of these roles will inevitably be working closely with each other.
Personally, I believe that the biggest part of being a top-performing EA team is learning to strike the right balance across the perspectives listed above. It isn’t about doing just one thing or having a “primary” concern as much as it is about how well the EA leaders cover the bases, shifting emphasis from strategic, business-oriented concerns, to helping certain initiatives head down the right path, and then back again as dictated by the situation. It is about breadth, and reach, and longevity.
In future posts Tim or I will examine several of the questions asked by the audience, some answered by the panel and others that we didn’t have time to address.