https://training-course-material.com/index.php?action=history&feed=atom&title=Enterprise_Architecture_TeamEnterprise Architecture Team - Revision history2026-05-02T19:28:27ZRevision history for this page on the wikiMediaWiki 1.45.1https://training-course-material.com/index.php?title=Enterprise_Architecture_Team&diff=29008&oldid=prevAhnboyoung at 16:43, 7 February 20162016-02-07T16:43:15Z<p></p>
<p><b>New page</b></p><div>{{Cat|Enterprise Architecture|29}}<br />
<br />
<slideshow style="nobleprog" headingmark="⌘" incmark="…" scaled="false" font="Trebuchet MS" ><br />
;title: Enterprise Architecture Team<br />
;author: Bernard Szlachta (bs@NobleProg.co.uk)<br />
</slideshow><br />
<br />
== Enterprise Architecture Team Members⌘==<br />
* EA Architect<br />
* Chief Architect<br />
* Technical Architect<br />
* Solution Architect<br />
* SME (Subject Matter Expert)<br />
<br />
== Technical Architect⌘ ==<br />
* Research and present current and emerging technologies<br />
* Discussing the best products and systems with the rest of the theme <br />
* Technology forecasting<br />
* Plan for technology upgrades<br />
* Dealing with technology problems as they arise<br />
<br />
== Solution Architect ⌘==<br />
* Predict how bunch of technologies will work together<br />
* Contains Information System aspects as well as Application System aspects<br />
* Document the structure and behaviour of a solution to a problem<br />
* Creates plan and processes for solution implementation<br />
<br />
== Subject Matter Expert (SME)⌘ ==<br />
* AKA domain expert (the domain usually refers to non-IT domain, like finance, production ,etc...)<br />
* An expert in a particular area<br />
<br />
== Enterprise Architect⌘ ==<br />
* Describe the current state of the architecture<br />
* Plans for future changes in the architecture<br />
* Deal with the IT-business alignment<br />
* Talk to the management, project managers, SMEs and other architects<br />
* Deals with finances and "selling" changes in the architecture to other people within the organization <br />
<br />
== Enterprise Architecture changes and Project Managers ⌘==<br />
* If the changes in the architecture not only restrict or recommend solutions but require substantial work on its own (e.g. analysis of current architecture requires 12 people) there might be a need in a Project Manager within the Enterprise Architecture team<br />
* Those Project Managers should not be involved in any "fire fighting" or day to day activity as it would distract them from long term strategic importance of the architecture<br />
<br />
== Chief Architect⌘ ==<br />
* Establish and communicate the technology roadmap for IT-Business alignment<br />
* Still technical role<br />
* Usually reports to CIO or CEO<br />
* In the past they reported to CFO<br />
<br />
== Quiz⌘ ==<br />
<br />
'''EA should not report to any operation related entities (Project Management, Product Management, etc...). Why?'''<br />
<br />
{{Show Answer|Because they are rewarded for fire-fighting, not long term goals}}<br />
<br />
== Other possible roles ⌘==<br />
* Business Liaison<br />
** PR or marketing person for EA department<br />
** communicates the importance of the architecture to the management<br />
** Passes the management feedback to the EA team<br />
* Chief Innovation Officers<br />
** Makes decision about introduction of new way of doing things</div>Ahnboyoung