Scribd Logo
Upload

Welcome to Scribd!

  • 122 views

    4 Togaf 9 1 Enterprise Architecture Framework Overview m4 Slides

    Uploaded by

    Mounir Ben Mohamed
    This document outlines the initial approach for establishing an enterprise architecture capability at WFBC bank. It discusses the first two phases - Preliminary Phase and Architecture Vision Phase - of the ADM (Architecture Development Method) as defined by TOGAF. The preliminary phase focuses on identifying business drivers, stakeholders, and configuring the architecture team and principles. The architecture vision phase aims to get organizational buy-in by validating business needs, demonstrating benefits, and refining the high-level target state architecture vision. Key techniques discussed are developing architecture principles and using business scenario planning to understand strategic objectives and derive requirements.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    4 Togaf 9 1 Enterprise Architecture Framework Overview m4 Slides

    Uploaded by

    Mounir Ben Mohamed
    122 views48 pages
    This document outlines the initial approach for establishing an enterprise architecture capability at WFBC bank. It discusses the first two phases - Preliminary Phase and Architecture Vision Phase - of the ADM (Architecture Development Method) as defined by TOGAF. The preliminary phase focuses on identifying business drivers, stakeholders, and configuring the architecture team and principles. The architecture vision phase aims to get organizational buy-in by validating business needs, demonstrating benefits, and refining the high-level target state architecture vision. Key techniques discussed are developing architecture principles and using business scenario planning to understand strategic objectives and derive requirements.

    Original Description:

    Togaf 9 1 Enterprise Architecture Framework Overview m4

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document outlines the initial approach for establishing an enterprise architecture capability at WFBC bank. It discusses the first two phases - Preliminary Phase and Architecture Vision Phase - of the ADM (Architecture Development Method) as defined by TOGAF. The preliminary phase focuses on identifying business drivers, stakeholders, and configuring the architecture team and principles. The architecture vision phase aims to get organizational buy-in by validating business needs, demonstrating benefits, and refining the high-level target state architecture vision. Key techniques discussed are developing architecture principles and using business scenario planning to understand strategic objectives and derive requirements.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    122 views48 pages

    4 Togaf 9 1 Enterprise Architecture Framework Overview m4 Slides

    Uploaded by

    Mounir Ben Mohamed
    This document outlines the initial approach for establishing an enterprise architecture capability at WFBC bank. It discusses the first two phases - Preliminary Phase and Architecture Vision Phase - of the ADM (Architecture Development Method) as defined by TOGAF. The preliminary phase focuses on identifying business drivers, stakeholders, and configuring the architecture team and principles. The architecture vision phase aims to get organizational buy-in by validating business needs, demonstrating benefits, and refining the high-level target state architecture vision. Key techniques discussed are developing architecture principles and using business scenario planning to understand strategic objectives and derive requirements.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 48

    ADM - Capability Iteration

    Joseph Anthony
    @ansolabs | www.ansolabs.net

    Lisa Knowsovich CSO of WFBC

    Strategic Themes
    1. Building the digital foundation for the
    bank
    2. Adopting a customer and value centric
    business model
    3. Cultural renovation

    Why Digital Foundation?

    On Customer and Value


    Centricity

    Cultural Renovation

    Next Steps
    Lisa seeks Toms advice on
    establishing the Enterprise
    Architecture capability
    Tom promises to come up with
    an initial approach shortly

    Capability Iteration
    Overall objective of Capability
    Iteration of ADM is to kick-start
    architecture development process
    Architecture capabilities include:
    Teams
    Stakeholders
    Roles
    Responsibilities
    Processes
    Principles
    Tools etc.

    Capability Iteration

    Preliminary

    Architecture
    vision

    Pattern Used for Each Phase


    Objectives

    Overall Approach

    Techniques &
    Guidelines

    Inputs & Outputs

    Preliminary
    Phase

    Objectives of Preliminary Phase

    Objectives of Preliminary Phase


    Form an initial view on where the
    enterprise desires to move to
    Configure the architectural capability to
    enable the enterprise to get there

    General Approach - Preliminary Phase

    Overall Approach

    WHAT

    First Step is to identify business drivers for change


    Establishing high-level view of target state architecture
    Business, Data, Applications and Technology architecture domains
    (i.e. BDAT domains)

    Identifying the scope and impact

    HOW

    Workout who the stakeholders are


    Workout how architecture capabilities need to be
    configured

    Configuring Architecture Capability


    Establish team structure, responsibilities
    and accountabilities
    Tailor TOGAF and plan ADM iterations
    Adapt to other Enterprise Frameworks
    Identify architecture principles

    Establish Team Structure

    A given architecture initiative typically require different skillsets


    Different levels of engagement required at various stages
    Team structure, responsibilities, accountabilities and availability
    need to be worked out

    Tailor TOGAF & ADM

    TOGAF actively encourages ADM to be tailored


    Tailoring helps determine, number of iterations, scope of each
    iteration, expected outcomes of each

    Adapt to Other Enterprise Frameworks

    Architecture is inherently collaborative in nature


    It is important to tailor TOGAF to other enterprise frameworks such as
    portfolio/ program/ change/ IT service management frameworks, etc.

    Identify Enterprise Architecture Principles

    Principles represent the framework of guidance within which


    architecture decisions are made

    Techniques & Guidelines

    What are Enterprise Architecture Principles?

    Enterprise Architecture
    Architecture is the structure of components, their
    inter-relationships, and the principles and guidelines
    governing their design and evolution over time.

    Architecture Principles
    Principles govern how the
    components of the architecture is put
    together and how this design is
    allowed to evolve over time
    Principles constrains architectural
    choices
    They have the net effect of increased
    order and consistency while
    simultaneously reducing complexity
    and cost

    Who Authors Principles?


    Typically developed by enterprise architects
    Endorsed by key business stakeholders and
    the architecture board
    In early stages of introducing EA within an
    organization, the principles are arrived at
    through expert opinions and adopted from
    the industry
    Principles are enduring but need to be
    reviewed periodically

    Template for Architecture Principle

    An Example
    Principle Name

    Adaptability and Flexibility

    Description

    Enterprise systems (both IT and non-IT systems) and their components are designed for
    adapting to change. Where the change could be an alteration in the enterprises
    context as a result of a mix of one or more factors

    Rationale

    Adaptability and flexibility leads to greater responsiveness and enables the business to
    respond quickly to threats in its environment as well as leverage opportunities

    Implications

    Business Architecture should continuously explore opportunities in the internal and


    external value networks to innovate and add value
    This implies negotiating new vendor contracts, standardizing external and internal
    interfaces
    Information systems should progressively move towards loosely coupled portfolio of
    services and consider active use of API management platforms
    Infrastructure should increasingly adopt hyper-convergence and cloud technologies
    Overall although upfront investments will be required on infrastructure and new
    architecture initiatives, over time the adoption of this principle leads to greater agility

    Are Architecture Principles Set in Stone?

    Nothing
    Is Set in Stone
    Principles evolve over time
    Architects should determine the applicable principles for each initiative and
    offer their right interpretation in a given context
    Principles may at times seem contradictory, and architects need to resolve and
    offer guidance towards making the right trade-off

    Preliminary Phase Inputs and Outputs

    Inputs
    Strategic objectives of the business
    Business drivers, goals and principles
    Other enterprise frameworks
    Organization structures
    Any architecture frameworks previously used
    Architecture principles
    Any other architecture artefacts

    Outputs
    Request for Architecture Work

    Enterprises current context and need for architecture


    work
    High-level view of desired target state architecture
    EA organization model
    Governance structure and process
    Architecture principles and their interpretation
    Tailored TOGAF framework

    Adapting other Enterprise frameworks


    ADM iterations and their scope

    This deliverable is used as a tool to drive


    consensus

    Architecture
    Vision
    (Phase A)

    Objectives of Phase A

    Objectives of Phase A
    Crystalizing on architecture vision
    Obtain organizational buy-in to proceed
    with architecture effort

    Overall Approach Phase A

    Overall Approach
    Validate business context and drivers for change

    Establishing the value proposition


    Demonstrate benefits
    Identify risks, unknowns, issues and assumptions
    Identify architectural constraints
    Evaluate business readiness as viewed from cultural, moral,
    regulatory and ethical perspectives

    Refine and clarify scope, impact and stakeholder


    engagements
    Refine the view on high level target state to be
    achieved
    Identify success criteria, metrics and KPIs
    Create Architecture Vision and Statement of
    Architecture Work deliverables

    Techniques & Guidelines

    Scenario Planning
    Introduced by Herman Khan in US and Gaston
    Berger et al. in France
    It was first adopted for business scenarios by
    Royal Dutch Shell in 1965
    According to a HBR article titled Living in
    Futures about 65 to 70% of large organizations
    use scenario planning
    Applied to strategy formulation
    Also applied to innovation, risk management,
    and leadership development

    Its Not About Predicting Future


    Obtaining deeper insights and organizational
    awareness
    Avoids the flaw of repeatedly planning for a
    future that is expected to look like today
    It encourages,

    Preparing for alternate futures


    Challenging the comfortable expectations
    Treating disagreements as assets

    It offers a safe space for planners to acknowledge


    uncertainties and discuss plausible realities that
    the enterprise needs to face

    Scenario Planning and Enterprise Architecture


    Enterprise architecture is a forward looking
    function
    Business led EA is closely tied to strategy
    formulation and execution
    TOGAF encourages the use of scenario
    planning for architecture development
    It encourages use of scenario planning in all
    ADM phases with emphasis on A & B

    Merging Scenario Planning and Architecture Development


    Understand Business Scenarios
    Identify SMART objectives
    Model business environment,
    processes etc.
    Identify principles and constraints
    Derive actionable requirements

    Understanding SMART Objectives


    Specific

    Timebound

    Measurable

    SMART
    Objectives

    Realistic

    Actionable

    Who Creates Business Scenarios?

    Benefits of Business Scenario Planning


    Enhances the ability of business to

    Perceive change
    Respond to change
    Exercise early influence
    Start early on new opportunities
    Enable holistic learning

    A good starting point for architecture


    requirements
    Helps engage internal and external
    stakeholders

    Phase A Inputs and Outputs

    Inputs

    The outputs from the Preliminary phase form key inputs for the
    Architecture Vision phase

    Outputs
    Architecture Vision and Statement of Architecture Work are
    the key deliverables
    Architecture Vision captures
    OUTPUTS

    Current state and target state capabilities


    Business, Information systems and infrastructure views
    Scope of architecture work envisaged
    Business scenarios addressed

    Statement of Architecture Work establishes business case


    for architecture work and includes
    Value proposition
    Outlay of anticipated investments/ expenses
    Metrics to track progress and performance
    Description of opportunities, risks, threats and issues

    Module Recap
    Tom Wisemans meeting with LisaKnowsovich
    ADM phases in capability iteration
    Two ADM techniques relevant for this iteration
    Architecture Principles
    Business Scenario Planning Technique

    You might also like