ea2009 Enterprise Architecture keynote Final

  • 3,083 views
Uploaded on

Key note presentation around Pragmatic Enterprise Architecture delivered at CAUDIT ea2009 Auckland New Zealand 24 Nov 2009

Key note presentation around Pragmatic Enterprise Architecture delivered at CAUDIT ea2009 Auckland New Zealand 24 Nov 2009

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • can you pls send me your slide? it quite interesting slide
    Are you sure you want to
    Your message goes here
  • Hello Marc,

    This presentation is useful to me. Can you allow me to download it or send a copy of it?

    Thanks in advance,
    Atul
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
3,083
On Slideshare
0
From Embeds
0
Number of Embeds
2

Actions

Shares
Downloads
0
Comments
2
Likes
15

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Speaking Notes:Ask the audience to throw out words and phrases of what they think (and others think) of when they hear the term “Enterprise Architecture”. The association can be definitional (what it is) and/or positive and negative connotations about the business value EA offers (what problem is it trying to solve). Repeat and accept all answers and encourage the audience to have fun with this.

Transcript

  • 1. Pragmatic Enterprise ArchitectureThe Modern Enterprise Architect
    Marc Caltabiano
    Director, Enterprise Architecture
  • 2. Pragmatic Enterprise ArchitectureAgenda
    What is Enterprise Architecture
    Guiding Principles
    Enterprise Architecture Process
    Framework
    Approaches
    Recommendations
    © 2009 Oracle Corporation – Proprietary and Confidential
  • 3. © 2009 Oracle Corporation – Proprietary and Confidential
    The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.
  • 4. CAUDIT ea2009Birds of a feather
    © 2009 Oracle Corporation – Proprietary and Confidential
    EA Governance
    TOGAF
    2-10 year planning
    BPM and EA
    Back to Basics
    Value of Architecture for the un-architects
    Communication
    Data Warehouse and BI
    BUSINESS FOCUS
    Business Adoption
    IT Governance
    IT Strategic Plan
    Capabilities
    Implementing EA
    Repository
    What is EA?
  • 5. CAUDIT ea2009Birds of a feather
    © 2009 Oracle Corporation – Proprietary and Confidential
    Immature market adoption of EA
    Collaboration
    Practical Artefacts
    EA Governance
    TOGAF
    2-10 year planning
    BPM and EA
    Regionalise Assets
    Back to Basics
    Value of Architecture for the un-architects
    Communication
    Data Warehouse and BI
    BUSINESS FOCUS
    Business Adoption
    Differences between Frameworks/methods
    IT Governance
    IT Strategic Plan
    Capabilities
    Knowledge Re-use
    Implementing EA
    Repository
    What is EA?
    Practical application of the framework
    not dot to dot
    Certification
    Sharing Artefacts
  • 6. Enterprise ArchitectureAsk the expert !
    © 2009 Oracle Corporation – Proprietary and Confidential
  • 7. Enterprise ArchitectureDriving Strategy…
    © 2009 Oracle Corporation – Proprietary and Confidential
    “Today’s IT architectures, arcane as they may be, are the biggest roadblocks most companies face when making strategic moves.”
    –McKinsey Flexible IT, Better Strategy”
  • 8. Pragmatic Enterprise ArchitectureWhat problem are we REALLY trying to solve?
    Reduce Costs
    Faster to Market
    Innovate
    Globalize
    Business Goals
    Technology Challenges
    Delivering Real Business Value
    Increasing System Complexity
    Enterprise Architecture
    Business Integration
    Infrastructure
    Intelligence & Analysis
    Enterprise Mgmt
    Business
    IT Alignment
    Data & Content
    Applications & Services
    Security & Compliance
    Application Development
    and so on
    © 2009 Oracle Corporation – Proprietary and Confidential
  • 9. Pragmatic Enterprise ArchitectureWhat problem are we REALLY trying to solve?
    © 2009 Oracle Corporation – Proprietary and Confidential
    Why is
    Enterprise Architecture
    so hard?
  • 10. Pragmatic Enterprise ArchitectureArchitect Roles…
    Enterprise Architect
    Business Architect
    Solutions Architect
    Applications Architect
    Infrastructure Architect
    Database Architect
    Security Architect
    Differing Priorities and Focus
    © 2009 Oracle Corporation – Proprietary and Confidential
  • 11. Pragmatic Enterprise ArchitectureFrameworks, Frameworks, Frameworks
    Zachman Framework - IBM framework from 1980s
    TOGAF - The Open Group Architecture Framework
    FEA - OMB Federal Enterprise Architecture
    The Gartner Methodology - (formerly the Meta Framework)
    DoDAF - DoD Architecture Framework
    MoDAF - UK Ministry of Defense Architecture Framework
    AGATE - The France DGA Architecture Framework
    MDA - OMGs Model Driven Architecture
    SOMF - Service Oriented Modeling Framework (Methodologies Corporation)
    SABSA - Sherwood Applied Business Security Architecture
    © 2009 Oracle Corporation – Proprietary and Confidential
    No standard approach
  • 12. Pragmatic Enterprise Architecture Frameworks: Foundation for developing EAs
    © 2009 Oracle Corporation – Proprietary and Confidential
    EA Framework Benefits:
    • Common vocabulary, models, taxonomy
    • 13. Processes
    • 14. Reference Models
    • 15. Prescriptive Guidance (EA processes, architecture content, implementation roadmap, governance)
    • 16. Catalog of EA deliverables and artifacts
    • 17. Tools
    • 18. Principals and Strategies
    • 19. Reference Architectures
    • 20. Recommended set of products and configurations (EA processes, architecture content, implementation roadmap, governance)
    How do you pragmatically apply these?
    Zachman Framework
    • John Zachman (IBM, 1980’s)
    • 21. Start of it all
    The Open Group Arch Framework
    (TOGAF)
    • Since 1995
    • 22. Widely Adopted in the Commercial Sector
    Federal Enterprise Architecture (FEA)
    • Since 1999
    • 23. Federal agencies map investment requests to their FEA reference models
  • Pragmatic Enterprise ArchitectureJust in Time - Enterprise Architecture
    “Just-enough models should be created just in time to address specific [business-driven requirements].”
    Gartner EA Process: Evolution 2005
  • 24. Pragmatic Enterprise ArchitectureEA Guiding Principals - Guidance
    © 2009 Oracle Corporation – Proprietary and Confidential
    Business focused approach
    • Driven downwards by Business Strategy addressing new markets and innovation and advantage
    • 25. Driven upwards from Business Execution addressing Operational Issues and Remediation
    Simplify & re-use
    • Standardise & Simplify the technical architecture
    • 26. Just enough for enterprise solutioning efforts
    • 27. Reuse best practice Business Models and Reference Architectures from industry and commercial vendors
    Deliver & measure
    • Focused on speed-of-delivery for high level guidance
    • 28. Mature iteratively & evolutionary for breadth & depth
    • 29. Can be enforced and governed and success measured
  • © 2009 Oracle Corporation – Proprietary and Confidential
    1
    Identify the Business Strategy
    Establish an EA Program
    2
    3
    Define “Future State” Architecture
    4
    Define EA Roadmap
    5
    Establish EA Governance
    Establishes 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.
    Pragmatic Enterprise ArchitectureEA Guiding Principals
  • 30. Pragmatic Enterprise ArchitectureUnnecessary EA Steps
    © 2009 Oracle Corporation – Proprietary and Confidential
    • If 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” Architecture
    Exhaustively define “Future State” Architecture
    • Business strategies, vendor products and technologies change, therefore you need to “architect for change” and keep your options open.
    • 31. 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
  • 32. Pragmatic Enterprise ArchitectureBusiness Strategy Lead
    © 2009 Oracle Corporation – Proprietary and Confidential
    1
    Identify the Business Strategy
    Establish an EA Program
    2
    3
    Define “Future State” Architecture
    4
    Define EA Roadmap
    5
    Establish EA Governance
    Business Goals
    Reduce Costs
    Faster to Market
    Innovate
    Globalize
  • 33. Pragmatic Enterprise ArchitectureEstablish the Program
    © 2009 Oracle Corporation – Proprietary and Confidential
    1
    Identify the Business Strategy
    Establish an EA Program
    2
    3
    Define “Future State” Architecture
    4
    Define EA Roadmap
    5
    Establish EA Governance
    TASKS
    • Establish goals, leadership and resources
    • 34. Define scope and the next iteration of work product.
    • 35. Business Executive sponsorship and support.
    • 36. Conduct Stakeholder analysis.
    • 37. Establish plan for an EA Governance Board.
    • 38. Develop a communication plan.
    PEOPLE
    • Executive Sponsors
    • 39. Stakeholders
    • 40. Chief Enterprise Architect
    • 41. Program Manager
    • 42. Business Architects & Industry Experts
    • 43. Information Analysts
    • 44. Solution Architects
    • 45. Specialty Architects
  • Pragmatic Enterprise ArchitectureOracle Enterprise Architecture Framework
    © 2009 Oracle Corporation – Proprietary and Confidential
    Oracle Enterprise Architecture Framework (OEAF)
    Oracle Architecture Development Process (OADP)
  • 46. Applying Enterprise Architecture
    A Solution Blueprint
    spans all the
    layers of the OEAF
    (e.g. Modernisation)
    A Customer EA is a configuration of the OEAF for a given Customer
    An Industry Blueprint is a configuration of the OEAF for a given industry (e.g. Retail)
  • 47. Pragmatic Enterprise ArchitectureFuture State – Prescriptive Guidance
    © 2009 Oracle Corporation – Proprietary and Confidential
    1
    Identify the Business Strategy
    Establish an EA Program
    2
    3
    Define “Future State” Architecture
    4
    Define EA Roadmap
    5
    Establish EA Governance
    How do you…
    • Stay current with technology and applications,
    • 48. Implementing best practice business models,
    • 49. Yet be able to integrate these business processes
    • 50. To improve business visibility, agility and efficiency?
  • Pragmatic Enterprise ArchitectureFuture State – Prescriptive Guidance
    © 2009 Oracle Corporation – Proprietary and Confidential
    1
    Identify the Business Strategy
    Establish an EA Program
    2
    3
    Define “Future State” Architecture
    4
    Define EA Roadmap
    5
    Establish EA Governance
    EA Transformation Focus:Management Excellence
    Enterprise Solutioning: Business-Driven Initiatives
    EA Continuous improvement: Business Remediation
    EA Transformation Focus:Operational Excellence(Business, IT)
    EA “Future State”: Infrastructure
  • 51. Pragmatic Enterprise ArchitectureFuture State – Prescriptive Guidance
    © 2009 Oracle Corporation – Proprietary and Confidential
    1
    Identify the Business Strategy
    Establish an EA Program
    2
    3
    Define “Future State” Architecture
    4
    Define EA Roadmap
    5
    Establish EA Governance
    RESPONSIBILITIES
    • Establish an EA Governance model and an Architecture Review Board
    • 52. Promote the EA agenda and adherence to “Future State” EA Prescriptive Guidance:
    • 53. Review IT project designs
    • 54. Review proposed enterprise solution architectures and major initiatives
    • 55. Provide assistance…
    BOARD MEMBERS
    • Chief Information Officer
    • 56. Chief Enterprise Architect
    • 57. At least one Executive Sponsor
    • 58. At least one major Business Executive
    • 59. At least one Business Architect
    • 60. Lead Specialty Architects pulled in on an as-needed basis
  • Pragmatic Enterprise ArchitectureThe role of the Enterprise Architect…
    © 2009 Oracle Corporation – Proprietary and Confidential
    “The role of the Enterprise Architect is to intervene for the benefits of others”
    Peter Idoine – NZ MD
    Driven by outcome based success
    Articulate, Conversant, Respectful
    Product and Solution Line Breadth & Depth
    Trusted Advisor
    Sells products & services via selling the Enterprise Solution
    Experienced Architect;
    Track Record: Badges of Honor
    Cross Domain
    Apps + Tech
    Leader of Architects
    Identifies “wedge opportunities” in deep, technical discovery sessions
    Aligns customer goals to Product Line via Architecture Roadmaps
    Value Selling Skills
    Credible & Published
    Committed to add value with every activity
    Just as comfortable white-boarding as presenting PowerPoint
    The Enterprise Architect
  • 61. Pragmatic Enterprise ArchitectureRecommendations and Summary
    © 2009 Oracle Corporation – Proprietary and Confidential
    1
    Identify the Business Strategy
    Establish an EA Program
    2
    3
    Define “Future State” Architecture
    4
    Define EA Roadmap
    5
    Establish EA Governance
    Stay practical!
    Always align EA to Business Strategy (Top Down) and Remediation (Bottom Up)
    Get the right mix of Business/IT/EA people involved with Exec Sponsorship
    Adopt a simplified EA process and framework
    Don’t re-invent the wheel: Get best practices business models and reference architectures from others
    Establish “Future State” EA Architecture Prescriptive Guidance with EA Governance
    Focus on Operational Excellence first for sound Technical Architecture
    Is not static: “Architect for change”
    Requires thought leadership and a practical approach: just enough; just in time
    Build iteratively based on business priorities and alignment
  • 62.
  • 63. For More Information
    © 2009 Oracle Corporation – Proprietary and Confidential
    E: marc.caltabiano@oracle.com
    B: http://lightbulbeffect.blogspot.com
    http://blogs.oracle.com/enterprisearchitecture
    W: http://www.oracle.com/technology/architect/entarch
  • 64. 28