Aggregated enterprise architecture wisdom
Adrian Grigoriu Here is a LinkedIn discussion on “What would make TOGAF more usable?” that prompted my post here. A framework, according to whatis.com, is “a real or conceptual structure intended to serve as a support or guide for the building of something…
…the difference between functions, capabilities, processes, value streams, value chains… should be sufficiently clarified before even attempting to integrate them in the EA framework and whole
To me, a core EA problem is the apparent contentment with the state of EA art. It looks like we prefer the status quo to rocking the boat. Why so though? Since the EA body of knowledge is not…
While the customers and stakeholders are not complaining, little can be done. This is the main reason for the lethargy of EA.
Not unexpectedly, one of the key business stakeholders from finance asked – while I was in the process of “selling” him the EA – “why do we need EA, since you, in IT, surely have an architecture, don’t you, otherwise…
cnt’d.
There is much hype, few visible results and a great number of professionals who still ask what EA is and what is it for, even if they already “practice” it.
The state of frameworks is dire. Too many that do too little.
Frameworks like TOG…
In this post, I will show how architecture visualisation methods used by architects for centuries (see Drew Skau’s post Visualization Architect at Visual.ly) are relevant to an EA. I’ll exemplify the procedures on the FFLV-GODS, a full EA …
In this post, I will show how architecture visualisation methods used by architects for centuries (see Drew Skau’s post Visualization Architect at Visual.ly) are relevant to an EA. I’ll exemplify the procedures on the FFLV-GODS, a full EA f…
Nick Malik, in this post discusses the business architecture definition of the BizBOK 2.1. For completion, the BizBOK 2.1 definition cited is: “A blueprint of the enterprise that provides a common understanding of the organization and is used to…
It’s like the EA prefix is added to any other IT profession we know. In reality, the demand is for a multitude of roles housed selfishly under the EA banner.
After all, it is still the case today that the “company is the people” as EA describes, rather than “the company is the IT” as in EITA. But EITA delivers now, while the EA still promises.
It is often assumed the enterprise architecture function includes planning and strategy. While this may be the case in practice, given the specifics of a job description, in theory, at least, they are separate disciplines. The delinea…