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?
A video guide outlining the contents of TOGAF 9.1 and how it can benefit you and your organization.
Read the latest blog from our series explaining the benefits from of TOGAF and Enterprise Architecture for the various types of stakeholder. This week: The Business Managers
In this TOGAF blog we discuss the 7 habits of any highly successful Enterprise Architects
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.
Quite frequently I get asked about the scope of Enterprise Architecture. Sometimes the question is a simple one: what is included in a typical EA initiative? But sometimes there’s a bit more to the question, with an implied: why is that included in EA? This question came up a couple of times this week, so it seemed a good time to go over some of the key points in this blog, and explain what TOGAF has to say about scope.
Without a strong architectural voice at the governance table, the EA contribution and value will always be compromised. Unless you have effective EA governance, then you will suffer the following outcomes:
TOGAF describes three types of architecture role. Two of these types - Enterprise and Solution - are often used in the job title for architects, but it is rare to find someone called a Segment Architect. If you are confused about this missing role... read on, and all will be revealed.
Well it turns out that some of the billboard headlines for TOGAF are the same: TOGAF is billed as the cure for all enterprise woes, as the silver bullet for IT development, or the one-stop solution for cutting costs and simplifying infrastructures. But when you get a bit more inquisitive it turns out that although it could be the answer everyone’s been looking for, it is actually just one of many new management ideas that require a lot of effort if they are to be successful.
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.