Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Transcript of Enterprise Architecture
Carlsberg aims to be
"The fastest growing global beer company"
An Enterprise Architecture in Transition...
Strong alignment with the overall strategy
Stronger, Faster, Leaner
Strong focus on global Standardization
Vendor dependent --> Taking ownership of the architecture
Model Centric --> Planning and Standards Centric
Ivory Tower Syndrome --> Usable artifacts and realistic EA
Carlsberg's EA Framework Solution:
EA at Carlsberg
Business (Process) Architects Role
EA/ BPM Roles
Carlsberg's EA Maturity
Sogeti maturity model for Carlsberg's EA function
Maturity measurements can:
Set baseline for cross-function collaborations
Identify performance and capability gaps
Identify constraints in EA and BPM collaboration
Track programme development over time
Used for creating to-be vision and road map
Sogeti maturity model of Carlsberg
-Focuses: “architectural thinking” and “integration”
strengths of maturity assessment
- Carlsberg agree that this could benefit (in the future)
- in collaborations (how the EA and BPM collaboration can benefit from this)
- strengthen implementations
- identify capability gaps
- takes time / incremental steps
TOGAF - The Open Group Architecture Framework
Divides architecture into 4 stages:
Architectural Development Model:
Development cycle of 8 phases
The Enterprise Continuum may be viewed as a "virtual repository" (as of TOGAF 9 this is not virtual any more) of all the architecture assets available to an organization. These include architectural models, architectural patterns, architecture descriptions, and other artifacts. These artifacts may exist within the enterprise and also in the IT industry at large.
The Enterprise Continuum consists of both the Architecture Continuum and the Solutions Continuum. The Architecture Continuum specifies the structuring of reusable architecture assets, and includes rules, representations and relationships of the information system(s) available to the enterprise. The Solutions Continuum describes the implementation of the Architecture Continuum by defining reusable solutions building blocks.
TOGAF is based on four interrelated areas of specialization, called architecture domains:
Business architecture, which defines the business strategy, governance, organization, and key business processes of the organization.
Applications architecture which provides a blueprint for the individual application systems to be deployed, the interactions between the application systems, and their relationships to the core business processes of the organization with the frameworks for services to be exposed as business functions for integration.
Data architecture which describes the structure of an organization's logical and physical data assets and the associated data management resources
Technical architecture or technology architecture which describes the hardware, software and network infrastructure needed to support the deployment of core, mission-critical applications
Kotter Change Management 8 steps for leading change
create a sense of urgency
gather a team
create a vision
communicate the vision
enable broard by-in
create short-term victory
never let up
make this a part of the org. culture
Project oriented culture and Ad hoc
temporary project function (BSP)
not defined areas of responsibility
not defined areas of expertise
Informal --> working towards becoming formalized
RACI - Responsible, Accountable, Consulted, Informed
Develop and implement a fully functional RACI model
(today only RA)
the project = "A business architect"
Schein on manifistations of Org Culture
Business Standardization Programme (BSP)
One Carlsberg IT (One CIT)
•Value through mediation of IT-knowledge for new projects, infrastructure changes, implementation of strategies and idea generation.
•Framework/repository for the architects.
•Value through stakeholders usage of the EA artifacts in planning and decision-making.
•Large-scale framework for the stakeholders.
•Some assumption of documentation usage.
Understand the future strategy
Model the strategy
Specify migration strategy
Understand the current state
Identify gaps in current architecture
Maintain architecture components
Develop the core team
Bring positive change through governance
Establish a cross-org EA board.
Develop a formal compliance EA review
Ensure that all aspects of the EA are communicated effectively
Physical link between EA planning efforts and business change (both strategic and tactical/operational changes).
Developing high-level models and principles for the future-state view of processes.
Creating conceptual and logical process designs for implementation.
Developing process performance metrics, targets and benchmarks,
Creating process notational standards
Maintaining a metadata repository for process artifacts
EA Roles and Responsibilities
Interview w Enterprise Architect, Emma Adolfsson and P.hd Student, Morten Gryning
Main theoretical basis by; Gartner, IBM and Scott Bernard
Carlsberg's EA reality vs. academia approach
Reactive and practical
Collaboration between EA and BPM
Impacted by org. culture and structures
Hard to define the value of
Competency Maturity Model Wheel
The Open Group