togaf

A Scrapbook of Past Projects

by

Enterprise Architecture has a reputation problem. Not because it lacks rigor or structure — quite the opposite. But because too often, architecture feels like something that exists next to the organization rather than within it. Diagrams live in tools, standards sit in documents, and architectural knowledge slowly fragments across folders, platforms, and people’s heads. It’s kind of like an intangible scrapbook of past projects.
The Architecture Repository, as described in the TOGAF® Standard, is an attempt to fix that. Not by introducing yet another tool or database, but by introducing a way of thinking. A way of treating architecture as a coherent, evolving body of knowledge — one that can be reused, governed, and continuously refined.

The post A Scrapbook of Past Projects appeared first on EAWheel.

Starting Your Career in EA

by

Embarking on a career in Enterprise Architecture can feel a bit like being handed a map of a city you’ve never visited, and being told that every street, alley, and café is critical. You’re then asked to solve a mystery. To put it in simple terms: starting your career in EA can be a challenge!
There’s a lot to take in: frameworks, models, technologies, stakeholders, business strategies, and a universe of acronyms that seem to multiply when you’re not looking. If you’re just starting out in EA—or thinking about it—you’re probably asking yourself, “Where do I even begin?” The good news is, you’re not alone, and the journey, while complex, is also incredibly rewarding.

The post Starting Your Career in EA appeared first on EAWheel.

Architecture Beyond Domains

by

Enterprise Architecture has been around for decades. The discipline has profoundly shaped how organizations plan, align, and structure their strategies, systems, and operations.
Frameworks such as the TOGAF Standard define four architecture domains and link them to specific architectural roles. While this approach has helped organizations organize work, it has also unintentionally reinforced rigid silos and limited the true potential of architecture as a holistic organizational capability.

The post Architecture Beyond Domains appeared first on EAWheel.

Risk Management (2/2)

by

The Architecture Development Method (ADM) of the TOGAF Standard describes a number of techniques a practitioner has at his disposal. Risk Management is the second-to-last technique that is described. Since it is addressed in several phases (Phase A and Phases E through H), it can be seen as an integral part of architecture development. Applying Risk Management techniques ensures that risks are identified, assessed, and mitigated as part of the architecture development process.

The post Risk Management (2/2) appeared first on EAWheel.

Risk Management (1/2)

by

The Architecture Development Method (ADM) of the TOGAF Standard describes a number of techniques a practitioner has at his disposal. Risk Management is the second-to-last technique that is described. Since it is addressed in several phases (Phase A and Phases E through H), it can be seen as an integral part of architecture development. Applying Risk Management techniques ensures that risks are identified, assessed, and mitigated as part of the architecture development process.

The post Risk Management (1/2) appeared first on EAWheel.