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 IT Organization
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.
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?
Read this blog to understanding the benefits from TOGAF for different types of stakeholder: The Business User
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.
A video guide outlining the contents of TOGAF 9.1 and how it can benefit you and your organization.
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?
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!
This blog covers how in the rapidly evolving digital market a Solution Architect builds a solution to face new challenges faced by your organization.
In this case study we examine the three types of gaps in enterprise architecture and how to manage transition from Current to target Architectures.