TOGAF is described as an Open Group Standard. But what do we mean by a “standard”, and what happens when there is more than one competing standard?
When we focus on teaching and learning TOGAF we sometimes forget that TOGAF is just one aspect of enterprise architecture in general. This blog explains why we need to remember that TOGAF is part of EA, but EA is more than TOGAF.
In this series of blogs we're going to examine the benefits from TOGAF for different types of stakeholders, starting with: Executive Sponsor, Executive Management & Board Members
Each profession has its unique way of doing things, and that when applying TOGAF the key thing is to “think” like an architect! The first step is to think holistically, and to do this you need to take into account the views and viewpoints of all stakeholders. But what other steps can you take to think as an architect?
Read this TOGAF blog: 'TOGAF: What's the Difference Between Scope and Partition?' to better understand the criteria of both scope and partion in the TOGAF framework.
Is there a future for TOGAF? Whether you are a large organization deciding to invest heavily in the use of TOGAF - or an individual thinking about getting trained and certified in TOGAF - you will want to know that TOGAF is not just a passing fad!
Architecture Frameworks have an undeserved reputation for being theoretical and passive. In this article we argue that the popular frameworks, such as TOGAF or Zachman, need to be tailored and adapted to create a set of active and useful frameworks – called Multiple Integrated Architecture Frameworks (MIAF).
Architects sometimes see the ADM as reactive, but EA should never be passive - it needs to respond to concerns, but add architectural thinking and then make a unique contribution to stakeholder needs. This blog explains some of the proactive aspects of ADM that are not so obvious.
TOGAF certification has become a de facto baseline for endorsing the skills of an enterprise architect. But how does it really help you?
I frequently get asked whether it’s practical to use TOGAF “out-of-the-box” – without any customization. Architects and clients are looking for a turnkey approach that they can easily plug into their enterprise with the hope of quick results – they don’t want something that requires too much effort.