Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start 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

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Enterprise Architecture

No description
by

Crdn Presentation

on 31 July 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Enterprise Architecture

What does it mean?
Why should we practice it?
How does it work?
What are the benefits?
EA is the process of translating business vision and strategy into…the enterprise’s future state and enabling its evolution
Technology
Business
Vision
You don't construct a building...
...without an architectural blueprint!
You don't change plans midway through...
...without consulting the architect!
1. EA Provides the Blueprint
2. EA Governs the Change
Typical Process (iterative):
Crdn Enterprise Architecture
Current State
Future State
Define/Refine the business strategy
Assess the current state
Design the future state (people/ process/ technology)
Identify the gaps
Enterprise Architecture Maturity Model
Disjointed Efforts
Not Following
Repeatable & Reliable Processes
Data Integrity
Multiple Points of Failure
Tactical Focus

vs
Strategic Focus
Loss of Productivity
(the same data stored in multiple locations)
(spaghetti architecture)
(administrators keying the same data multiple times)
(project by project)
(enterprise view to rationalize each project)
(Crdn is currently experiencing all the classic symptoms of operating without a formal EA practice)
Crdn's Symptoms
Next Steps
Develop a EA charter & roadmap to improve EA maturity
Address pressing EA needs (i.e. Redwood/SIMple/MyMove)
Establish Core Team & Align Virtual Team



Use a credible third party resources to support the EA implementation
Adopt TOGAF as the standard EA Framework
1) Establish Formal Enterprise Architecture Practice


2) Adopt Best Practices
Team Dynamics
1) Team Expertise
Coverage in the architectural domains
Charter & Scope
2) Organization & Archetype
Establish Core EA Leadership Team
Enterprise Mandate
Operate like HR Business Partner Model (Customer Focus)
Practical & Solution Oriented
Align Virtual Team
Business
Data
Application
Technology Infrastructure
Security
1) Team Expertise
2) Organization & Archetype
(*TOGAF is used by 80% of Forbes Global Top 50 worldwide)
Current State
Develop Project Portfolio
Examples of the benefits to you?
If the EA practice is constructed properly, Crdn has an opportunity to:
Implement global standards, practices and governance!
Set a crystal clear vision and strategy for both the short term and long term!
BizTech: Rationalize disparate business concepts and definitions with enterprise standards
Portfolio Management: Rationalize & prioritize project effort
Everyone: Partnership and advocate in your corner to help guide decision making.
Enterprise: Focus on foundation today so that future projects take 2 months vs 2 years to complete.
KEY RESPONSIBILITIES
Principles form the foundation of enterprise architecture.
Define the underlying general rules and guidelines for the use and deployment of all IT resources.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
33
38
39
30
What we have always done!
What we have never done!
(start small)
Core Team
Virtual Team
1. Principles & Standards
2. Strategy & Planning
To ensure that all stakeholders are included in defining, establishing, and using the architecture capability appropriately.
To assess current state and develop the future state Information Systems & Technology Architecture, describing how it will enable the business vision and strategy.
3. Architecture & Design
4. Governance & Assurance
Required to identify, manage, audit, and disseminate all information related to architecture management.
Less about overt control and strict adherence to rules, and more about guidance and equitable usage of resources to ensure sustainability of an organization's strategic objectives
5. Management & Development
An enterprise architecture practice must be managed and operated like any other functional department within a firm.
Defining goals and measuring success is of paramount importance
CIO
Product
Management
Infrastructure
Others
Align the technology strategy with the business vision
Maintain focus on the right things
Help manage the continual demand for change to the IT footprint
Drive standards and rationalize the use of disparate technology
Provide guidance with product development (technology standards, tools & processes)
Ensure developers are using standard design principles
Staff from different business units
Staff from third parties
Dedicated Staff

Dedicated Staff
Full transcript