Let me begin with a brief content page of a few next posts on Enterprise Architecture roadblocks, a theme I proposed a while ago.
I. Vague EA definition and scope
II. Uncertain Return Of Investment
III. Diversity and verbosity of EA frameworks, lack of consensus
IV. Design outcomes not fit for purpose
V. Ambiguity and competition with other technologies, SOA, ITIL ERP
VI. Effort governed by IT alone
VII. EA politics
VIII. Flawed Enterprise transformation planning and execution
IX. Improper EA maintenance and failure to employ proper tools
And here is a refresh of my definition of an Enterprise Architecture. EA is the Enterprise structure and operation blueprint of its business processes, technology, people and organisation. It is associated with a development process and Business as Usual activity. EA outlines an Enterprise strategic roadmap and transformation plan.
But it is also about financial and Business Continuity views, non-IT technologies, facilities/real estate, fleet...
EA is more than the sum of its parts: it is about the governance (mind) and the culture (soul) of the Enterprise (body).
I. Vague EA definition and scope
The scope dispute always hit the balance between the tactical and strategic thinking a dilemma as old as human mankind.
Nevertheless, benefits diminish at the same rate with the scope reduction. Dangerously so, the touted benefits are seldom realized because of the narrow scope, alienating important stakeholders.
EA architecture is often narrowed to IT solely. Why ? Because the concept was invented in IT. It is often seen as
– an Enterprise Wide IT Architecture (EWITA)or
– the IT department operation (ITSM ITIL)
but it seldom covers
- other IT architecture views - apart from the main product delivery process and applications view
- Knowledge or Content Management, Data Warehouse, Business Intelligence views...
– email, printing, voice, network, SOE (Standard Operating Environment), Helpdesk… architecture views
– Information architecture
- ...
But reduced to IT, the EA fails to involve business and management
and live to expectations.
EA should represent more than IT Architecture. It needs a wider scope to include other architecture views to provide motivation for all IT teams.
Enterprise IT Architecture is more than Applications and Infrastructure.
Till next time.
Schrijf als eerste een reactie
Alleen geregistreerde gebruikers kunnen reacties geven. Log in of registreer.
Via Nova Architectura is not responsible for the content of blogs, but authors and readers are asked to adhere the following guidelines. Authors are strongly encouraged to check facts, cite sources, present
balanced views, acknowledge and correct errors. Respect copyright, fair use and financial disclosure laws. Please do not disparage organizations, or individuals. Being critical of someone's practice is acceptable, when it is done in a professional manner. Prevent usage of marketing statements. Comments should be relevant to the specific post they are attached to. Spam, flaming, personal attacks, and off-topic comments are not
permitted. Readers are requested to notify
Dit e-mail adres is beschermd door spambots, u heeft Javascript nodig om dit onderdeel te kunnen bekijken
of any violations. The editor holds the right to remove any statements that, in the editors opinion, infringe the above guideline(s). The author receives a notification of this action.
