from architecture to execution with togaf...

PRESENTED BY:

ROBERT WEISMANCEO, BUILD THE VISION INCORPORATED

OTTAWA, CANADA(613)841-5118

[email protected]

From Architecture to Execution with TOGAF 9

Introduction

• The acid test for an Enterprise Architecture is transforming the architecture definitions into reality.

• The real challenge is to align business planning, portfolio management, operations service management, system design and enterprise architecture frameworks together through corporate governance to ensure success.

• TOGAF 9 provides very useful guidance to ensure that this takes place in a coherent manner based upon global lessons learned.

Agenda

• Architecture Transformation and Fit in the Organization• Capability Based Planning• Tiered Architecture• Architecture Impact and Framework Integration• Applying the ADM at different Enterprise Levels• Business Transformation Support• Interoperability• Risk Management & Governance• Migration Planning Techniques• Concluding Comments

Where Architecture Transformation Fits

ArchitectureTransformation

Supporting Material• Chapter 28 - Migration Planning Techniques• Chapter 29 - Interoperability• Chapter 30 - Business Transformation Readiness Assessment• Chapter 31 - Capability Based Planning• Chapter 32 - Risk Management

Stakeholders - The Management Frameworks

Slide 5

EnterpriseArchitectureDevelopment

Method

SystemDevelopment

Method

OperationsManagement

Portfolio/Project

Management

BusinessCapability

Management

GOVERNANCE

© Robert Weisman / Build The Vision 2009

Coordinating the Management Frameworks

© Robert Weisman / Build The Vision 2009 Slide 6

BusinessPlanning

EnterpriseArchitecture

Business Direction

PortfolioManagement

StructuredDirection


Delivers

Runs TheEnterprise

The OldWay

ProjectManagement

Capability Based Business Planning


Operations Management - Corporate IT Infrastructure

IM/ITPortfolio

CorporatePortfolio

(e.g. HR, Fin, …)

Line ofBusinessPortfolio

ProjectProject

Corporate Governance(Including Corporate IM/IT)

Capability 1 – (e.g. Electronic Service Delivery)

Capability 2 – (e.g. Sarbanes Oxley Compliance)Capability

Management(Horizontal)

FunctionalManagement

(Vertical)

Capability Concept


People DimensionIndividual TrainingCollective training

Professional Development

Process DimensionConcepts

Business ProcessesInformation Mgt

Materiel Dimension

InfrastructureInformation Technology

Equipment

CapabilityCapabilityCapability Increment

Capability

Capability “Radar” Diagram

© Robert Weisman / Build The Vision 2009 Slide <#>

Outline Capability Management


CapabilityManagement

Building Blocks(Deliverables)

Designates

Horizontal Management AcrossPortfolios

•Strategic Business Leadership

Possible Capability Dimensions•Personnel•R&D•Infrastructure/facilities•Concepts/Processes•Information Management•Materiel

CorporateStrategic Plan

Business TransformationGoals and Objectives

5 – 10years

Capability(OutcomeOriented)

Manages & Creates

3 – 5years

CapabilityIncrement

Contains

.25 – 1.5years

TOGAF 9 - TIERED ARCHITECTURE

11© Robert Weisman / Build The Vision 2009

Architecture Intent – Lessen Burden on Projects


ProjectArchitecture

Scope

EA SupportEnterprise

Architecture

ProjectArchitecture

Scope

Enable Projects to FocusOn Delivery

not Complex Design

• Agile Architecture• Strategic• Tactical• Transition• Operational

• Reusable Patterns,Solutions & Standards

Portfolio/Project Management



Business TransformationGoals and Objectives

5 – 10years

FunctionalPortfolios(e.g. IT, HR)

Identifies

.5 – 1.5years

Project/Initiative

Increment

Contains

ProjectProjectProject/

Initiative

3 – 5years

Consists of

Strategic Not Business

TOGAF 9 - Architecture Relationships


ArchRealization

ArchRealizationArch

RealizationArch

RealizationArchRealization(e.g. Projects)

ArchRealization

Time

Scope

Depth(Content)

Strategic Enterprise ArchitectureArchitecture Vision

Enterprise Architecture Definition #2 (Reference Arch)Enterprise Architecture

Definition #1 (Reference Arch)

~12 Months

~5 Years

~10Years

BaselineEnterprise

Architecture

TargetEnterprise

Architecture

Business Planning Relationships


Slide 15

~12 Months

~5 Years

~10Years

SegmentBusiness

Plans

SegmentBusiness

PlansSegmentBusiness

Plans

SegmentBusiness

PlansSegmentBusiness

Plans

SegmentBusiness

Plans

Strategic Enterprise Plan

TargetEnterprise

Vision

BaselineEnterprise

Status

Time

Scope

Depth(Content)

Zachman & TOGAF – Architecture Depth


WhatData

HowProcess

WhereNetwork

WhoPeople

WhenTime

WhyMotivation

Detailed Description(Programmers/IT)

Technology Model(Builder/Arch)

Description of IS(Designer/Section Head)

Model of Business(DG/Dir)

Scope/Objectives(ADM)

Implemented System(System Maintainers)

Architecture Vision (Strategic)

Architecture Definition(a.k.a. Reference)

Transition Architecture

Architecture Realization

Operational Architecture

Architecture Evolution/Transformation Plan Cycle


Transition Plan 1-2

Transition Plan 1-1

Transition Plan 1-3

Tactical Plan 1

Strategic Plan 1 PlanDesign

Execute

PlanDesign

Execute

PlanDesign

ExecutePlan

DesignExecute

PlanDesign

Execute

Transition Plan 2-2

Transition Plan 2-1

Transition Plan 2-3

Tactical Plan 2Plan

DesignExecute

PlanDesign

ExecutePlan

DesignExecute

PlanDesign

Execute

Updates

Transformation Plan Cycle

5-10 Years

3-5 Years

.5 to 1.5 Years

.5 to 1.5 Years

.5 to 1.5 Years

.5 to 1.5 Years

.5 to 1.5 Years

.5 to 1.5 Years

3-5 Years

Time

ARCHITECTURE IMPLICATIONS & FRAMEWORK INTEGRATION


Architecture Definition & Service Reference ModelThe Implications are not Trivial !!!


ServicesDomains

(Service Taxonomy)

ServiceStandards

Models

Requirements & Capabilities

IM/ITPlanningStructure

Management Accountability

Framework

CIOOrganization

Resources & Funding

Repository Structure

IM/IT Skills /ASD

(Outsourcing)

Products / Service Delivery

Service Reference Model

Enterprise Architecture Definition (Logical)

Architects Stakeholders

Specify InnovativeIntent Using

To Identify

OrganizedIn

SupportedBy

Basis For Basis For

SatisfiedThrough

Management Framework Relationships

Slide 20© Robert Weisman / Build The

Vision 2009ArchitectureManagement

CapabilityManagement

Portfolio/ProjectManagement


Business TransformationGoals, Objectives and Capabilities

5 – 10years

3 – 5years

1 – 1.5years

Structures

StrategicEnterprise

ArchitectureVision & Plan

Capability(OutcomeOriented)

FunctionalPortfolios(e.g. IT, HR)

Identifies Directs

Manages & Creates

Business PlanCapabilityIncrement

Contains


CorporateInfrastructure

ProjectProjectProject/

Initiative

Approves

Consists of

ArchitectureDefinition

& Plan

Identifies, And Technical

Direction

Directs

Consists of

TransformationArchitectureTransformation

ArchitectureTransitionArchitecture

Coordinates& Funds

Directs

Integrates

Project/Initiative

Increment

Contains Contains

Designs

Building Blocks(Deliverables)

Delivers

Designates



Another View of the Concepts

Slide 21

CorporateStrategicDirection

StrategicCapability

StrategicArchitecture

VisionPortfolio

Business LineStrategic Plan Capability

ReferenceArchitecture(Definition)

Project

CorporateBusiness

Plan

CapabilityIncrement

TransitionArchitecture

ProjectIncrement

PerformanceManagement

Identifies1..n

ArchitectedIn

Identifies1..n

Targetsn..n

ArchitectedIn

Derives2..n

IdentifiesResources

Delivered &Designed In

ProvidesContext For

Critical SuccessMeasures

Critical SuccessIndicators

Critical SuccessFactors

MeasuresSuccess of

1..nOperations

Management

DeliversCapability


Slide 22

5-10 YearFocus

3-5 YearFocus

One YearFocus

1-3 YearFocus

BaselineArchitecture

(TOGAF 8)

BaselineInfrastructure

(Recommended)

Implementation& Migration Plan

(TOGAF 8)

Modifies

Modifies

StrategicCapabilities

(TOGAF 9/XXX)

TargetCapabilities

(TOGAF 9/XXX)

CapabilityIncrements(TOGAF 9)Contain 1..nSpecify

Requirements

Business&

IT Arch

Reference(Defined)

Architecture(TOGAF 8)

TransitionSolution Target


Basis For1..n

StrategicArchitecture Vision

(TOGAF 9) Basis For1..n

Reflected In Addressed In Structured In

SegmentArch

PortfolioCharters

(TOGAF 9)

ProjectCharters

(TOGAF 9)

ProjectIncrement


Contain1..n

Contain 1..n

Initiative Groupings Logical Activity Grouping Integrated SolutionArchitecture Direction

Delivery

Operations

Strategic Plan(XXX)

Business Plan(XXX)Drives 3..n

Outputs(XXX)

Sub-Outputs(XXX)

Sub-OutputActivities

(XXX)

StrategicOutcomes

(XXX)

CapabilityFocus Area

(XXX)

SpecifySpecifyOutput

Objectives

Requirements

Business

BusinessAccountability

ArchitectureAccountability

DeliveryAccountability

OperationsAccountability

Legend

APPLYING THE ADM AT DIFFERENT ENTERPRISE LEVELS


Partitioning

• In most organizations one architecture will not work

• Need to partition and collaborate


EnterpriseLevel

Initiatives


Technology

Enterprise Architecture - Integration

CapabilityVision &

ArchDefinition

CapabilityVision &

ArchDefinition

CapabilityVision &

ArchDefinition

EnterpriseLevel

Initiatives


Applications

EnterpriseLevel

Initiatives


Data

EnterpriseLevel

Initiatives


Business

SegmentLevel

Initiatives

Segment Vision &Architecture Definition

EnterpriseOrganizationalDepth

ArchitectureDomains

Scope

Partitioning in a Single ADM Cycle

• good when a number of architectures are being developed within a similar time period by a single team.


BUSINESS TRANSFORMATION


Business Transformation Readiness Assessment

• Used for evaluating and quantifying an organization’s readiness to undergo change

• A joint effort between corporate (especially human resources) staff, lines of business, and IT planners.

• Recommended activities (Canadian Government Business Transformation Enablement Program) are:1. Determine the readiness factors that will impact the

organization2. Present the readiness factors using maturity models3. Assess the readiness factors, including determination of

readiness factor ratings4. Assess the risks for each readiness factor and identify

improvement actions to mitigate the risk5. Work these actions into Phase E and F Implementation and

Migration Plan© Robert Weisman / Build The Vision 2009Slide 28

Determine Readiness Factors• Determine factors that will impact on the business transformation associated

with the migration from the Baseline to Target Architectures.• Use a facilitated workshop with all stakeholders• Sample Factors (From Canadian Government) include:

– Vision– Desire , Willingness, and Resolve– Need– Business Case– Funding– Sponsorship and Leadership– Governance– Accountability– Workable Approach and Execution Model– IT Capacity to Execute– Enterprise Capacity to Execute– Enterprise Ability to Implement and Operate


Present Readiness Factors


Assess Readiness Factors 2


Readiness and Migration Planning

• Assessment provides a realistic assessment of the organization

• Key input into the strategic migration planning that will be initiated in Phase E and completed in Phase F.

• If business transformation actions are on architecture vision’s critical path and, if so, determine how they will impact implementation.

– No point deploying new capability without employees trained to use it and support staff ready to sustain it.

• Readiness factors will have to be continuously monitored (Phase G)

• Readiness factors assessment will be a living document and during the migration planning and execution of the Transition Architectures

© Robert Weisman / Build The Vision 2009Slide 32

INTEROPERABILITY


Definitions of Interoperability


INFORMATION INTEROPERABILITYKnowledge management

Business intelligenceInformation management

Trusted identity

BUSINESS INTEROPERABILITYDelivery Networks

eDemocracyeBusiness

Enterprise resource managementRelationship and case management

TECHNICAL INTEROPERABILITYIT infrastructure

CROSS-CUTTING REQUIREMENTS

DOMAINS: accessibility,

privacy, security

Core Enablers and Key Requirements Domains

Refining Interoperability - ExampleDegrees of Interoperability • Degree 1: Unstructured Data Exchange• Degree 2: Structured Data Exchange• Degree 3: Seamless Sharing of Data• Degree 4: Seamless Sharing of InformationThese degrees should be further refined e.g.

refinement of degree 3 follows:• 3A: Formal Message Exchange• 3B: Common Data Exchange• 3C: Complete Data Exchange• 3D: Real-time Data Exchange


Determining Interoperability Requirements

Stakeholders

InformationSystems


TOGAF 9RISK MANAGEMENT


Risk – TOGAF 9 Support• Always be risk• Need to Identify, Address and track • EA may identify the risks and mitigate certain ones• There are two levels of risk that should be considered

namely: – Initial Level of Risk– Residual Level of Risk

• The process for risk management is described in the following sections and consists of the following activities:– Risk Classification– Risk Identification– Initial Risk Assessment– Risk Mitigation and Residual Risk Assessment– Risk Monitoring

© Robert Weisman / Build The Vision 2009 38

Risk Impact Assessment


Corporate Risk Impact Assessment

EffectFrequency

Frequent Likely Occasional Seldom Unlikely

Catastrophic E E H H M

Critical E H H M L

Marginal H M M L L

Negligible M L L L L

Risk Identification and MitigationAssessment Worksheet

Slide 40

RiskID Risk

Preliminary Risk

Mitigation

Residual Risk

Effect Freq Impact Effect Freq Impact


Migration Planning - Business Value Assessment Technique

Capability Based Planning Based on Capability Increments

i.e. Business ValueValue criteria such as

1. compliance to principles, 2. financial contribution, 3. strategic alignment, and4. competitive position.

Risk criteria such as 1. size and complexity,2. technology,3. organizational capacity,

and 4. impact of a failure.

Each criterion should weighted.



Managing the Transformation Portfolio

Value

Risk

ProjectF

Project B

Project D

ProjectC

Project G

Project E

On target

At Risk

In Trouble

Project H

ProjectA

TOGAF 9 - MIGRATION PLANNING TECHNIQUES


Migration Planning - Implementation Factor Assessment and Deduction Matrix

The deductions are the basis for detailed design and planning requirements !!!


Migration Planning - Consolidated Gaps, Solutions, and Dependencies Matrix

Integrates all of the Gap Analysis and Potential Solutions

Migration Planning - Architecture Definition Increments Table

Allows the architect to plan a series of Transition Architectures outlining the status of the project objectives at specified times.

Describing the Architectural State usingthe Technical/Service Reference Model


Architectural State Using the Service Reference Model

Sub-Domain Service Transition Arch 1

Transition Arch 2

Transition Arch 3

Infrastructure Applications

Information Exchange Services

Solution System A

Solution System B-1

Solution B-2 (Complete)

Data Management Services

Solution System D

Solution System D

Solution System D

… …

Summary

• Realizing Architecture is difficult BUT crucial for credibility– 10 years developing a Framework is not effective

• Enterprise Architects have to work in context– Implementation is a collaborative effort

• TOGAF 9 provides some solid advice and best practices to realize the architecture– Addresses small, medium and large companies– Pragmatic approach– Requirement of “soft” skills

from architecture to execution with togaf...

Documents