TOGAF 9.2 Body of Knowledge
The TOGAF 9.2 Body of Knowledge focuses on two uses of the standard
The TOGAF 9.2 Body of Knowledge covers the transition from universal to unique. Different documents cover the spectrum, from universal concepts to emerging ideas. Within the formal TOGAF Standard, TOGAF Fundamental documents provide the essential scaffolding, and TOGAF Series Guides that provide stable best-practice guidance on common application. Outside the formal documents of the standard, the TOGAF Library holds leading edge method, approach, and technique.
Beyond The Open Group's TOGAF Library, Conexiam Navigate and other specialized guidance. In our enterprise architecture consulting, we liberally adopt methods, approaches, and techniques from other professions. We vociferously suggest that you liberate everything useful to your unique circumstances.
The Open Group Standard Process
The upside of Open Group standards is confidence that they represent stable best practice. The process ensures a formal consensus of The Open Group Architecture Forum 300 member companies. Every member has a voice and an opportunity to contribute.
The downside, formal standards publications like TOGAF Fundamentals and the TOGAF Series Guides take time. They need to be proven, stable practice.
The TOGAF Library and private publications, like Conexiam Navigate provide emerging ideas. point support to specialist, new, or emerging aspects of enterprise architecture.
TOGAF 9.2 Body of Knowledge
They maintain the TOGAF Body of Knowledge documents at different life cycles. Fundamental documents are enduring, stable, universal concepts. They change rarely. TOGAF Series Guides provide proven, stable, and enduring best-practice change slowly.
Emerging practice documents in the TOGAF Library will appear and disappear. If they last, they will migrate into becoming more formal guides. Material that The Open Group does not curate, like Conexiam Navigate, are published, supported and maintained by their organization.
By configuring the TOGAF standard, we have developed high functioning EA Teams in Finance organizations, Manufacturing firms, Professional Services companies, Academic institutions, Government Agencies, Telecommunications conglomerates, Defense Departments, and Digital Platform.
TOGAF 9.2 Body of Knowledge Supports Enterprise Architects
Every enterprise architect faces the challenges of developing useful enterprise architecture. Only then do they face the problem of how to document the architecture.
Guidance on Developing Useful Enterprise Architecture
The bulk of the TOGAF Body of Knowledge is supports developing useful enterprise architecture.
The foundation of all guidance is the Enterprise Architect Practitioners' Guide to Developing Enterprise Architecture. Chapter 3 and Chapter 6 set the stage.
Chapter 3 covers the Purpose of Enterprise Architecture. Sections explain Why you would develop an Enterprise Architecture, What is an Enterprise Architecture, and How to Use an Enterprise Architecture.
Chapter 6 is the Approach to the Architecture Development Method (ADM). Sections cover Key Architecture Development Activity:
- Stakeholder Engagement and Requirements Management,
- Trade-Off Decisions,
- Phases B, C, and D—Developing the Architecture
The Integrating Risk & Security guide is the next most important document. Every enterprise architect has an accountability for Risk and security. We are accountable to reduce the uncertainty of reaching our objectives and improving security.
Documenting the Enterprise Architecture
Today The Open Group's TOGAF Library is thin for documenting your Enterprise Architecture.
We maintain Conexiam Navigate, and a set of Navigate Atlas covering specialized purposes, like project and portfolio management (PPM), road mapping, governance, risk and compliance (GRC), business process improvement, service architecture, information architecture, and integration architecture.
TOGAF 9.2 Knowledge Base Supports Developing Enterprise Architecture Teams
Developing your enterprise architecture team is one of the key steps of delivering useful enterprise architecture to guide change. The Leader’s Guide to Establishing & Enhancing an EA Team sets the stage.
Always start with the purpose of your EA Team (Section 3.3), and the boundary of your enterprise (section 4.1 & 4.2). Section 3.3 discusses the patterns of architecture you will optimize your EA Team to support. Our EA Capability Consulting has identified four pairs which provide natural resting places.
- Portfolio and strategy
- Portfolio and solution delivery
- Project and strategy
- Solution Delivery and failure or frustration
Portfolio and Strategy EA Team Purpose
An architecture team that has a primary focus on portfolio and a secondary focus on strategy succeeds very well. In fact, this is probably the single most stable resting place for an effective enterprise architecture team.
We design this team to support the central problem facing all stakeholders what to fund.
Portfolio and Solution Delivery EA Team Purpose
An architecture team that has a primary focus supporting portfolio and a secondary focus on solution delivery has one challenge. They cannot take solution delivery issues into the portfolio support. They must ruthlessly focus on portfolio concerns and drive them into solution delivery. They also must carefully manage time.
Project and Strategy EA Team Purpose
A very common pattern is to have an architecture team with a primary focus supporting project in the secondary supporting strategy. We will focus their strategy work on major change initiatives - switching between the strategy and the execution. These teams must be very nimble in their work effort.
Organizations with high enterprise agility will have EA Teams focused on Project and strategy.
Solution Delivery and Failure
Probably half of all EA Teams have a primary focus supporting solution delivery. These teams have the shortest lifespans in the highest degree of personal frustration. This is not a natural resting place. As is a failure pattern. This is an unstable element. Like all unstable elements, eventually it will break down. It is impossible to provide meaningful value as an architect when your engagement starts at solution delivery.
We provide scalable additions to the TOGAF Body of Knowledge from DIY tools to Predictable EA Engagements.
Curated TOGAF 9.2 Body of Knowledge
Download Integrating Risk and Security with TOGAF® Standard Integrating Risk and Security with the TOGAF standard by aligning TOGAF’s essential scaffolding with security architecture’s best practices. This guide assists security architects and enterprise architects in …
Download the EA Team Leader’s Guide Download the Enterprise Architecture Team Leader’s Guide. Without deliberate configuration, you are hoping random action will build an optimized complex business capability. Start building an effective EA Team! Download …
Download the Enterprise Architecture Practitioner’s Guide Download the Enterprise Architecture Practitioner’s Guide. TOGAF provides stable guidance for enterprise architects. The Enterprise Architecture Practitioner’s Guide takes illuminates how to stable best practice and deliver useful enterprise …
TOGAF® Standard, 10th Edition We are excited to announce the new version of the TOGAF® Standard, 10th Edition is released. I know we’ll all call it TOGAF 10. We had a major hand updating the …
Download the SOA Practiocal Guide The SOA Practical Guide supports optimizing an EA Team’s method to support an architecture based on services, which mirror real-world business activities, comprising the enterprise business processes. Building an enterprise …
Download Introduction to the TOGAF® Standard, 10th Edition The TOGAF Standard, 10th Edition makes adoption of enterprise architecture best practices easier. It separates the universal concepts from proven best practice. The standard underscore where to …