Estab Successful EA Program Office.pptPresentation Transcript
Establishing a Successful Enterprise Architecture Program Office Presented by: Annette Hobbs, PMP [email_address] for Baltimore PMI Chapter
What is Enterprise Architecture (EA)?
Why is EA important?
How to create a successful EA program office
Questions and Answers
What is Enterprise Architecture?
The fundamental organization of an enterprise [ANSI/IEEE std 1471-2000]
The discipline of creating a blue print of an agency’s business, data, applications and technology [FEA-PMO http://www.egov.gov ]
Enterprise [Houghton Mifflin]
An undertaking , especially one of some scope, complication, and risk.
A business organization .
Industrious, systematic activity, especially when directed toward profit: Private enterprise is basic to capitalism.
The practice of designing structures (a discipline)
A coherent form or structure (an attribute)
Or we could say:
Is the practice of designing and documenting the form or structure of a business organization’s undertaking.
Do all enterprises have an architecture?
Most enterprise architectures were not planned, they just happened.
A large part of the effort
Involves analyzing and documenting the current architecture, as well as, planning, designing and engineering the future architecture.
EA Origin – John Zachman
Mr. Zachman focused on architecture since 1970. His 1st article and the original framework was published in 1987 (“A Framework for Information Systems Architecture,” IBM Systems Journal, vol. 26(3), 1987. http://www.research.ibm.com/journal/sj/263/ibmsj2603E.pdf ).
In 1992 John Zachman and John Sowa wrote another article (“Extending and Formalizing the Framework for Information Systems Architecture." J.F. Sowa and J. A. Zachman. IBM Systems Journal, vol. 31, no. 3, 1992. http://www.research.ibm.com/journal/sj/313/sowa.pdf ) expanded the framework to its current 36 cell framework (“Enterprise Architecture – A Framework”).
Zachman’s A Framework for Enterprise Architecture ® John A. Zachman, Zachman International http://www.zachmaninternational.coml Business Technical
User in the functioning enterprise
Zachman – for School Classroom Source: O’Rourke, C. (2003); Enterprise Architecture Using the Zachman Framework ; Course Technology Prepared students Timetables Students & teachers Classroom Montessori or individualization Books Functioning Enterprise Strategy & tactics based on plan, time, location & students Attendance Dismissals Security needs Location of classroom materials Lesson plan Arrange classroom things Sub-contractor Teacher rules and guidelines Teacher assignments Class assignments to remove conflicts Realistic location for activities Course plan based on enrollment & facility Practical material composition Builder Grading rules and guidelines Student and teacher interaction Teacher and student ratios Preferred location of teaching activities Optimal delivery of course plan Optimal material composition Designer Scholastic achievement targets Teaching schedule Teacher workflow Location of facilities Delivery according to student needs Material of classroom content Owner Government mandates School calendar Professors Instructors Staff Delivery technique Approved teaching delivery Approved Curriculum Planner Why Motivation When Time Who People Where Locations How Processes What Things
Why is EA Important?
Enterprise Architectures (EA) help align the infrastructure with the business mission.
Provides details of relationships.
Identifies gaps between needs and capabilities.
Describes where we are and where we are going.
EA is a tool; for when “systems” are built they become business tools.
Provides communications mechanism between business stakeholders because stovepiped-processes and systems lead to wasteful duplication.
Promotes interoperability and resource sharing providing greater potential for cost savings.
“ Can’t afford not to. The alternative is to suboptimize the enterprise’s performance and results.”, Randy Hite, Director of Information Technology Issues at GAO
Zachman on EA value
Without the EA you can NOT achieve:
IT alignment with the business goals
Reduced time to market
Speech at Data Management and Information Quality Conferences in the UK, 7-10 November 2005
EA’s value is tied directly to its ability help organizations deal with complexity and change. The greater the complexity and the greater the envisioned change , the greater will be the EA value to facilitate that change.
Readily available descriptive representations of the enterprise
Ability to unify and integrate business processes across the enterprise
Ability to unify and integrate data across the enterprise
Increased flexibility of the enterprise to link with external partners
Increased agility by lowering the "complexity barrier“.
Reduced solution delivery time and development costs by maximizing reuse of enterprise models
Ability to create a common vision of the future shared by the business and IT communities = continuous business/IT alignment
Source: Brown, A. (2004), “ Enterprise Architecture Value Proposition”
EA Return on Investment or Return on Asset
Return on Investment:
John Hancock realized a $6.25M savings on redundancies discovered.
Dow realized $300M savings on revenue from implemented a new project identified through EA work.
Key Corp realized a 1 year savings of $7M in reduction in software maintenance
Return on Asset :
EA helps you make decisions that will in due course improve your business’ productivity
Source: Blevins, T. (2004, April). “Enterprise Architecture: Return on Investment”. http://www.opengroup.org/comm/newsletter/2004/04.htm
Federal Government EA History
The Clinger-Cohen Act - 1996
Federal Enterprise Architecture Framework (FEAF) - 1999
OMB Circular A-130 - 2000
The E-Government Act - 2002
OMB Circular A-11 – 2004
Various OMB memorandums
OMB’s EA Assessment Framework for 2006
Use your EA to demonstrate results
Do you have an EA? Does it integrate cross agencies?
Does it show (business) results?
Future of EA in Federal Government E-Gov initiatives LOB Centers of Excellence Smart Buy Implementation/use of Government-wide Lower level Architectures include Department and Agency solutions Agencies include Gov-wide Initiatives in their EA Department/Agency Specific A gencies Contribute to Gov-wide Initiatives Source: Dick Burk Briefing at IAC meeting 1/27/2006 Program Solution Program Solution Program Solution Program Solution Agency/Bureau Solutions Department/Agency Solutions Federal Government-wide Solutions
Capital Investment Planning Strategic Plan Enterprise Architecture Migration Plan FY FY FY FY $$$ $$$ $$$ $$$ $$$ $$$ $$$ $$$ $$$ $$$ $$$ $$$ Maps Investment to Returns Today’s Architecture Future Architecture (today +)
Now that we understand what an EA is and its value to an organization Let’s talk about how to establish a successful EA program office
Staff the Program Office
Typically a staff of 4-6 people working closely with functional staff and system developers
EA Tool Expert
Make sure staff is qualified and trained
Identify other stakeholders
Sponsor – Champion of the EA program & ensures resources
Business Manager – Participates in EA decisions and promotes EA solutions
Business End-Users – Identifies requirement and provides feedback on results of solutions
CIO – Executive leader & primary EA decision maker
Other Chief Architects of related businesses
Determine the purpose of “your” EA
This is unique to each organization
Helps answer some other questions that will need to be answered for future decisions
Helps determines the depth and breadth of the EA effort
Create a charter
Similar to one for projects
Short, concise but informative
May be called other names in different organizations
Select an EA Framework Below is a partial list of available frameworks
EA 3 – Scott Bernard
Federal Enterprise Architecture Framework (FEAF)
Department of Defense Architecture Framework (DODAF)