Aggregated enterprise architecture wisdom
Enterprise architecture artifacts are powerful tools for educating and engaging your stakeholders in your enterprise architecture efforts. Let’s explore the basics of building artifacts with real impact.
Investigating the Practical Application of Enterprise Architecture Artifacts as an…
TOGAF uses a very specific language to describe the outputs that architects produce. This poster highlights the key things you need to know. Download this free poster from Good e-Learning now!
Free Registration Required. This is an example set of templates for TOGAF 9. It includes example artifacts for all catalogs, matrices and diagrams, and template deliverables. http://ow.ly/5IS6T Example artifacts are as follows: Catalogs: Application Architecture: Applications Portfolio Catalog, Interface Catalog…
Quite often as an Enterprise Architects we are asked to show what the deliverables of an Enterprise Architecture program are.
TOGAF provides a methodology for analyzing your specific situation and turning that analysis into deliverables and actionable artifacts. Artifacts may have different shapes as defined in TOGAF 9. They may be: Catalogs, matrices or diagrams. EA artifacts may also help to define a standard set of document types such as education, strategy, decision, policy, standard, guideline, etc. It is also recommended that you set up a simple online discussion thread or wiki for each artifact to solicit feedback from artifact consumers.
If we consider the various architecture domains, they may have different forms.
These are very basic example of what artifacts may look like. They may rapidly be created and are definitely a way to explain to the EA stakeholders how the first deliverables of our baseline architecture looks like.
“You can think of an enterprise as a physical algorithm for creating value.”
The question of how well you understand your own enterprise has always mattered. But it has never mattered more than now. As organizations race to embed AI acro…
by Dorene Dickman Enterprise Architecture Soft Skills: Why Great Architects…
In complex portfolio environments, strong prioritization decisions are only as effective as the organization’s ability to sustain alignment during execution. Even when initiatives are evaluated rigorously, ranked objectively, and aligned to capacity targets, execution can drift if priorities, plans, dependencies, and risks are not consistently visible across teams and leadership. This blog post concludes the…
Why some enterprise architecture practices create activity without impact—and how to recognize when architecture work does not influence real decisions.
Enterprise Architecture frameworks are rarely questioned at the conceptual level. Most architects accept their value. Many organizations reference them explicitly. Certifications remain popular, methods are well known, and the language of architecture has become increasingly standardized across the profession. Yet something interesting happens when these frameworks enter daily practice: the translation becomes challenging, resulting in difficulty gaining stakeholder buy-in. However, stakeholder buy-in is not the issue.
The post More Practicality, Less Theory appeared first on EAWheel.
Why many enterprise architecture deliverables go unused and how to make architecture artifacts actually support real decisions and create measurable impact.
Enterprise architecture often creates value indirectly. This article explains how distance to value creation affects visibility, influence, and compensation in architecture expert roles.