The document discusses pragmatic enterprise architecture, focusing on aligning business strategies with IT solutions to deliver value amidst increasing complexity. It outlines steps to establish an enterprise architecture program, including identifying business strategies, defining future states, and establishing governance. Key themes include the importance of practical frameworks, adapting to change, and engaging the right mix of stakeholders.

1. Pragmatic Enterprise ArchitectureThe Modern Enterprise ArchitectMarc CaltabianoDirector, Enterprise ArchitectureTim RubinEnterprise Architecture

2. Enterprise ArchitectureAgenda2 © 2009 Oracle Corporation – Proprietary and ConfidentialPragmatic Enterprise ArchitectureWhat is Enterprise ArchitectureOpen Space Workshop:Major TrendsWorking in the new business environmentHot Topics in Enterprise Architecture

3. Pragmatic Enterprise ArchitectureWhat Problem are you trying to solve?3 © 2009 Oracle Corporation – Proprietary and ConfidentialReduce CostsFaster to MarketInnovateGlobalizeBusiness GoalsTechnology ChallengesDelivering Real Business ValueIncreasing System ComplexityEnterprise ArchitectureBusiness IntegrationInfrastructureIntelligence & AnalysisEnterprise MgmtBusinessIT AlignmentData & ContentApplications & ServicesSecurity & ComplianceApplication Developmentand so on

4. Pragmatic Enterprise ArchitectureWhere do you start?4 © 2009 Oracle Corporation – Proprietary and ConfidentialBUSINESS GOALS AND INNOVATIONUnderstand Key Business Drivers/Strategy

5. Document Current Business Model/Process

6. New Goals for Business Processes

7. Information RequirementsTop DownEnterprise ArchitectureENTERPRISE ARCHITECTUREBuild the IT inventory and as-is architecture

8. Create to-be architecture

9. Determine the capability gap

10. Create the RoadmapBusiness - IT AlignmentTECHNOLOGYStarts from technology & infrastructure architecture

11. Establish standards and best practices and define the reference architecture

12. Review project architecture

13. Move up to business problemsBottom Up

14. Enterprise ArchitectureOverviewLinking Business to Technology5 © 2009 Oracle Corporation – Proprietary and ConfidentialArchitecture at many levelsTechnology SpecialistDeep Specialised Leadership

15. Best Practices and real world skillsSolution/Domain ArchitectureSubject Matter expertise eg. Industry (FSI, CMU), ITIL etcorDomain Specialisationeg. CRM, SOA, Govenance and Security etc…Enterprise ArchitectureBusiness and IT alignment

16. IT Strategy

17. X-Product, X-Domain focus

18. Potentially x-industry focusEnterprise ArchitectureBusinessSolution ArchitectureEnterprise ArchitectureValueTechnology SpecialistProduct/Domain ArchitectureITIT/BusinessITBusinessCustomer Liaison

19. Pragmatic Enterprise ArchitectureJust in Time - Enterprise Architecture6 © 2009 Oracle Corporation – Proprietary and Confidential“Just-enough models should be created just in time to address specific [business-driven requirements].”Gartner EA Process: Evolution 2005

20. Pragmatic Enterprise ArchitectureWhat is Enterprise Architecture7 © 2009 Oracle Corporation – Proprietary and Confidential1Identify the Business StrategyEstablish an EA Program23Define “Future State” Architecture4Define EA Roadmap5Establish EA GovernanceEstablishes the vision for business and information technology.Involves the right mix of people for success.Establishes objectives, “future state” and roadmap.Provides prescriptive guidance, process and standards for Business and Information Technology.Documents current state and path to future state.Promotes adherence to EA guidance and plans while architecting business-driven, enterprise solutions.

21. Pragmatic Enterprise ArchitectureUnneccesary EA Steps8 © 2009 Oracle Corporation – Proprietary and ConfidentialIf you want to build a new addition to your house or even scrap your house and build a new one on the old foundation, you don’t need a complete blueprint of the existing house.Exhaustively define “Current State” ArchitectureExhaustively define “Future State” ArchitectureBusiness strategies, vendor products and technologies change, therefore you need to “architect for change” and keep your options open.

22. Create roadmaps on a “just in time” basis as you launch specific EA initiatives and architect enterprise solutions. Define “just enough” of the current and future states to implement your transformations and solutions.Exhaustively define Roadmap to “Future State” Architecture

23. Pragmatic Enterprise ArchitectureRecommendations9 © 2009 Oracle Corporation – Proprietary and Confidential1Identify the Business StrategyEstablish an EA Program23Define “Future State” Architecture4Define EA Roadmap5Establish EA GovernanceAdoption of a Framework, does not give you Architecture - Stay practical!Always align EA to Business StrategyGet the right mix of Business/IT/EA people involved with Exec SponsorshipAdopt a simplified EA processDon’t re-invent the wheel: Get best practices business models and reference architectures from othersEstablish “Future State” EA Architecture Prescriptive Guidance Reuse best practice Business Models & Reference Architecture from industry and commercial vendorsFocus on Operational Excellence first for sound Technical ArchitectureBuild iteratively based on business priorities and alignment

24. Open Space WorkshopThe Laws of Open SpaceRespect for othersWhoever comes is the right peopleWhatever happens is the only thing that could haveWhenever it starts is the right timeWhen it's over it's overThe law of two feet

25. Open Space WorkshopPragmatic Architecture - Key ThemesMajor Trends in EAWorking in the new business climateHot Topics in Enterprise Architecture11 © 2009 Oracle Corporation – Proprietary and Confidentialhttp://lightbulbeffect.blogspot.com

26. Open Space Workshop1. Major Trends in EAThe role of Enterprise Architecture as related to Business StrategyThe role of Architecture Governance and FrameworksTrends in:Enterprise SystemsInfrastructureSoftware/HardwareNetworking and Telecommunications12 © 2009 Oracle Corporation – Proprietary and Confidential

27. 13