Enterprise architects usually have the same opinion about that question: TOGAF is probably the most important and renown enterprise architecture concept. However, many people without IT or architecture experience hear “TOGAF” for the first time and struggle with understanding the concept as it inhibits quite some different aspects from which not all are very intuitive. Today’s article is for those who want to grasp a high-level understanding of “TOGAF” to understand if it is something that they should know about, can use, and hence should learn more about.
Establishing an enterprise architecture management (EAM) practice within an organization is challenging due to a couple of reasons: Benefits can only be seen in the long-term, the scope of activities is usually quite comprehensive and needs to involve many different stakeholders, and business and IT have to not only talk, but also listen to each other. In order to overcome such challenges, I have listed my top 10 success factors for an enterprise architecture management practice in this post.
As most of today’s architecture frameworks are quite old (from the 80s and 90s), many companies ask for adaptions to it or even do not believe in the benefit of such frameworks at all. In this post, I will suggest a modernized framework that takes into account what today’s companies need to consider and that better fits to today’s business environment.
The Open Group Architecture Framework (TOGAF) has recently published an updated version of its framework. After the last version 9.1 from 2011, the update 9.2 in April 2018 has been the first update in the last seven years. In the context of IT, Digital, and the increased pace of change that we face today, seven years is for sure a long time. I will therefore use todays post to analyze, how TOGAF has actually reacted to the Digital Transformation and how the framework has been impacted by the changes in the last seven years.