A lingua franca is the language, adopted as common, between speakers whose native languages are different but how useful is TOGAF as an Esperanto go-between language for enterprise architects from different backgrounds?
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?
As technology advances the pressure increases drastically on business infrastructure. This blog covers how Infrastructure Architecture is structured approach to help your organization run efficiently in the digital landscape.
At the end of August 2013, The Open Group announced that the number of TOGAF 9 certified individuals had passed the 25,000 mark. An increase of nearly 8,500 new certifications in the 12 months prior!
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.
Sometimes people find it difficult to see the unique contribution of EA. So what is it that makes EA distinctive? Here are five things that the best enterprise architects do, and some tips from TOGAF on how you can follow their example.
You started out using TOGAF, you’ve completed an iteration of the ADM for your first EA project and things went well, do you really need to revisit the Preliminary Phase again or can you save time by getting on straightaway with Phases A to H?
TOGAF makes a big point of the need for good stakeholder management, devoting the whole of Chapter 24 to the subject, while Step 2 in Phase A: Architecture Vision describes the process to Identify Stakeholders, Concerns, and Business Requirements.
There are some things in TOGAF that confuse practitioners over and over. The difference between scope and partition is one of those confusions that comes up as a regular question. In this blog we explain the key differences, and explain why TOGAF can be confusing.
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.