Establishing EA teams

Establishing EA teams

Yogish Pai

Bl

htt //

t

h bl

t

Blog:

http://entarch.blogspot.com

© Copyright 2007 – Yogish Pai

The author grants a non-exclusive license to everyone to publish this document in full or part by acknowledging the source Any other usage is prohibited without the express source. Any other usage is prohibited without the express permission of the authors.

IT Organization Patterns

Organized by IT Functions

Organized by IT functions

eBusiness

CRM + ERP

Each team directly interfaces

with the business

Typical for IT organization with

Typical for IT organization with

large packaged application

implementations

Each team is headed by the

Business

Intelligence +

Analytics

Infrastructure

Each team is headed by the

delivery chief (reports to the

CIO) and has the following

structure

Analytics

IT Organization Patterns

LOB Aligned with centralized delivery

Chief

Information

Information

Officer

Divisional

Centralized

Divisional

CIO

Project

Business

Delivery

Centralized

functions

Program

Application

Divisional CIO focused on delivering solutions for a single

Line-Project

Managers

Business

Analysts

Delivery

teams

og a

Management

Office

Infrastructure

Application

Support

Divisional CIO focused on delivering solutions for a single Line

Of-Business

Centralized teams provide common capabilities such as Program

Management Office, shared services, network management, data

centers and application support

centers and application support

Typical organization for centralized IT where there isn’t a large

packaged application implementation

IT Organization Patterns

LOB Aligned with different delivery models

Chief

Information

Information

Officer

Di i i

l CIO

Di i i

CIO

Divisional CIO

(Widget

Manufacturer)

Division CIO

(Gadget

Manufacturer)

Centralized

Governance

Organized by IT

Function

LOB Aligned

with centralized

delivery

Autonomous Divisional CIOs responsible for all aspects of delivery for

the Line-Of-Business

Global/Centralized CIO responsible for strategy and governance –

limited say in the operations of Divisional CIOs

limited say in the operations of Divisional CIOs

Typical for very large organizations

Enterprise Architects brings consistency across the

enterprise

independent of the IT Organization model

enterprise – independent of the IT Organization model

Typically only the CIO gets the enterprise

perspective

EA Teams

perspective

CIO could dramatically increase IT efficiency by

establishing EA teams that directly report to

him/her

EA teams would work on behalf of the CIO to

provide consistency and flexibility across the

enterprise

Enterprise Architecture Evolution Pattern

Phased approach to establishing EA teams

Technology Architecture • Establish IT Business Architecture • Business Alignment • Service Portfolio Management • Program Project Architecture • Design solutions • Identify reuse • Develop standards • Design and develop shared services • Integration and Data Governance Program Management Office

Project Architecture: Provide visibility and demonstrate value of the

team; limit involvement to strategic projects

• Develop Frameworks

Technology Architecture: Leverage standards to demonstrate business

value based on ROI, shared services delivery part of EA team, engage

business for managing Integration and Data Governance process

Business Architecture: Challenge business silos to align their priorities

based on enterprise objectives, program management office now part of

EA teams

Strategic Roles of the Enterprise Architecture

T

Team

A periodic process to establish the IT

Business Strategy &

Priorities

p

p

Strategy and Action Plan

Enterprise Architecture Review Process to

keep the plan current

Priorities

Enterprise Blueprinting

IT St t

d A ti

p

p

IT Strategy and Action

Plan

Business Architecture

Enterprise

Transformation of Enterprise Architecture

to include Business Architecture

Technology

Enterprise

Architecture

to include Business Architecture

Business Architecture is the primary focus

gy Architecture

Enterprise Blueprinting Benefits

Overall view of IT needs and priorities across business areas

Eff t

ithi

b

i

h ll b

i ibl

d h

d

ith ll

f

Efforts within one business area shall be visible and shared with all

other business areas

f

Leverage common components, reducing cost

B tt

t f

d

i i

ki

j

t

i iti

d

Better support for decision making on project priorities and

budget spending

Raise awareness of additional needs across business areas

f

Infrastructure efforts

f

Common data

needs

D i

t

d

t

i

l ti

i

f

d

Drive towards enterprise solutions going forward

Enterprise Blueprinting Guidelines

Map overall process definition and underlying applications,

t

d t

h

l

systems and technology

Determining priorities lies with business

E h

li

t b t

th

i

b

i

it t

Enhance alignment between the various business units to

deliver one end to end business process

Organize gap assessment / solutions in functionally related

g

g p

y

stages

f

Similar tasks grouped in same package

Map IT budget spend and IT Enterprise Roadmap onto the

Map IT budget spend and IT Enterprise Roadmap onto the

completed business process

Enterprise Architecture Review Process

Objectives

Guarantee adherence to enterprise architecture standards

p

by ensuring involvement from the Architecture team from

the beginning

Ensure better synchronization between the business and

the Enterprise Architecture teams on business priorities

on all areas of architecture

on all areas of architecture

Provide more support to the architects assigned to each

f th

j

t

one of the projects

Enterprise Architecture Review Process

Groups

Groups

Goals

Inputs

Outputs

Executives

and needs IT Business Objectives Enterprise Architecture Direction

Architecture

Steering

Guide Enterprise / Project Architecture based on business objectives

Determine product organization /

Business objectives

As-Is Architecture and systems Project Proposals

Architecture Standards (approval)

Architecture initiative definitions

Steering

Committee

Determine product organization / funding structure in line with architecture direction

Ensure Governance

Architecture assignment to specific projects Project Proposals Architecture Process Data Models SLAs KPIs, etc.

Architecture initiative definitions Project definitions and funding Project Architecture

assignments

Architecture

Review Board

Determine Architecture standards Ensure project compliance with existing standards

Exception approval

Business objectives Architecture standards Project deliverables Network and Infrastructure Design and estimates

Project Architecture approval Corrective actions

New requirements for architecture components

Enterprise

Working

Groups

Execute a specific architecture design / deployment task over a limited time span

Business needs and environment changes Architecture component / standard need identification

Project plan including funding requirements

Architecture components design and development Architecture standards (definition)

Participants of the Enterprise Architecture

Review Process

Groups

p

Participants

p

Executives

CIO – Interfaces with the Executives

Enterprise Architecture team to provide input for decision making

Architecture Steering

Committee

Chair: CIO or Head of EA team

Architecture: A small group of core EA team

Committee

Members: Business Operations, LOB-IT and IT Operations leaders

Project Architecture will provide members with supporting information

for decisions on specific projects

Architecture Review Board

Chair: Head of EA team

Core Members: Enterprise Architects

Optional Invitees: IT Operations

Project teams responsible for presenting to the ARB

Enterprise Working Groups

Staffed on a case-by-case basis

Enterprise Architecture Domain Model

Business Architecture

Ali i B i d IT

EA Management

EA O i ti M d l • Aligning Business and IT • Aligning Application Portfolio to EA • Key Metrics • EA Organization Model • EA Funding • EA Operation Technology Architecture • Sub-domains: Data, Application, Infrastructure & Security

• Reference Architectures

Governance

• Sub-domains: Data, Services, Business Process, Technology & Project

• Standards • SDLC

Delivery, Operations & Project Alignment Delivery, Operations &

Measurements

• Project Rollout • EA Metrics Collection

Project Alignment

• Enterprise Architect, Project Management & Project Architect alignment • Engaging EA at each of the

projects

• Aligning Project Portfolio management to EA

Thank You

Yogish Pai

© Copyright 2007 Yogish Pai © Copyright 2007 – Yogish Pai

The author grants a non-exclusive license to everyone to publish this document in full or part by acknowledging the source. Any other usage is prohibited without the express permission of the authors.