Upload
vukhuong
View
243
Download
4
Embed Size (px)
Citation preview
Establishing EA teams
Yogish PaiBl htt // t h bl tBlog: http://entarch.blogspot.com© Copyright 2007 – Yogish PaiThe 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 expresssource. Any other usage is prohibited without the express permission of the authors.
© Copyright 2007 – Yogish Pai
IT Organization PatternsOrganized by IT Functions
Organized by IT functions
eBusiness CRM + ERP
Each team directly interfaces with the business
Typical for IT organization withTypical for IT organization with large packaged application implementations
Each team is headed by the
Business Intelligence +
AnalyticsInfrastructure
Each team is headed by the delivery chief (reports to the CIO) and has the following structure
AnalyticsFunction
Head
Project Managers
Business Analysts
Specialized delivery teams
Support g y teams
© Copyright 2007 – Yogish Pai
IT Organization PatternsLOB Aligned with centralized delivery
Chief InformationInformation
Officer
Divisional CentralizedDivisional 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 aManagement
OfficeInfrastructure Application
Support
Divisional CIO focused on delivering solutions for a single LineOf-Business
Centralized teams provide common capabilities such as Program Management Office, shared services, network management, data centers and application supportcenters and application support
Typical organization for centralized IT where there isn’t a large packaged application implementation
© Copyright 2007 – Yogish Pai
IT Organization PatternsLOB Aligned with different delivery models
Chief InformationInformation
Officer
Di i i l CIO Di i i CIODivisional 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 CIOslimited say in the operations of Divisional CIOs
Typical for very large organizations
© Copyright 2007 – Yogish Pai
Enterprise Architects brings consistency across the enterprise independent of the IT Organization modelenterprise – 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
EA Teams EA Teams
© Copyright 2007 – Yogish Pai
Enterprise Architecture Evolution PatternPhased 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
© Copyright 2007 – Yogish Pai
Strategic Roles of the Enterprise Architecture TTeam
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 tip p
IT Strategy and Action Plan
Business Architecture
EnterpriseTransformation of Enterprise Architecture to include Business Architecture
Technology
Enterprise Architecture
to include Business Architecture
Business Architecture is the primary focus
gyArchitecture
© Copyright 2007 – Yogish Pai
Enterprise Blueprinting Benefits
Overall view of IT needs and priorities across business areasEff t ithi b i h ll b i ibl d h d ith llEfforts within one business area shall be visible and shared with all other business areasLeverage common components, reducing cost
B tt t f d i i ki j t i iti dBetter support for decision making on project priorities and budget spending
Raise awareness of additional needs across business areasInfrastructure effortsCommon data needs
D i t d t i l ti i f dDrive towards enterprise solutions going forward
© Copyright 2007 – Yogish Pai
Enterprise Blueprinting Guidelines
Map overall process definition and underlying applications, t d t h lsystems and technology
Determining priorities lies with business
E h li t b t th i b i it tEnhance alignment between the various business units to deliver one end to end business process
Organize gap assessment / solutions in functionally related g g p ystages
Similar tasks grouped in same package
Map IT budget spend and IT Enterprise Roadmap onto theMap IT budget spend and IT Enterprise Roadmap onto the completed business processIdentify systems for sun setting
© Copyright 2007 – Yogish Pai
Enterprise Architecture Review ProcessObjectivesGuarantee adherence to enterprise architecture standards pby 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 architectureon all areas of architecture
Provide more support to the architects assigned to each f th j tone of the projects
© Copyright 2007 – Yogish Pai
Enterprise Architecture Review Process Groups
Groups Goals Inputs OutputsExecutives Review and approve architecture
investments based on business goalsEnterprise Business ObjectivesEnterprise Architecture trends and needs
IT Business ObjectivesEnterprise Architecture Direction
Architecture Steering
Guide Enterprise / Project Architecture based on business objectivesDetermine product organization /
Business objectivesAs-Is Architecture and systemsProject Proposals
Architecture Standards(approval)Architecture initiative definitionsSteering
CommitteeDetermine product organization / funding structure in line with architecture directionEnsure GovernanceArchitecture assignment to specific projects
Project ProposalsArchitectureProcessData ModelsSLAsKPIs, etc.
Architecture initiative definitionsProject definitions and fundingProject Architecture assignments
Architecture Review Board
Determine Architecture standardsEnsure project compliance with existing standardsException approval
Business objectivesArchitecture standardsProject deliverablesNetwork and InfrastructureDesign and estimates
Project Architecture approvalCorrective actionsNew requirements for architecture components
Enterprise Working Groups
Execute a specific architecture design / deployment task over a limited time span
Business needs and environment changesArchitecture component / standard need identification
Project plan including funding requirementsArchitecture components design and developmentArchitecture standards (definition)( )
© Copyright 2007 – Yogish Pai
Participants of the Enterprise Architecture Review Process
Groups Participantsp pExecutives CIO – Interfaces with the Executives
Enterprise Architecture team to provide input for decision making
Architecture Steering Committee
Chair: CIO or Head of EA teamArchitecture: A small group of core EA team
Committee Members: Business Operations, LOB-IT and IT Operations leadersProject Architecture will provide members with supporting information for decisions on specific projects
Architecture Review Board Chair: Head of EA teamCore Members: Enterprise ArchitectsOptional Invitees: IT OperationsProject teams responsible for presenting to the ARB
Enterprise Working Groups Staffed on a case-by-case basis
© Copyright 2007 – Yogish Pai
Enterprise Architecture Domain Model
Business ArchitectureAli i B i d IT
EA ManagementEA 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
© Copyright – 2007 Source: SOA Consortium
Thank You
Yogish Pai© Copyright 2007 Yogish Pai© Copyright 2007 – Yogish PaiThe 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.