10/30/2011 1 Enterprise Architecture 202: Enterprise Architecture 202: Creating the Information Age Enterprise and and Bridging the Chasm Between Strategy & Execution ITMPI005 1 1-November-2011 11:00 AM – 12:30 PM EST Leon A. Kappelman, Ph.D. Mi h l Mil i Professor of Information Systems Director Emeritus, Information Systems Research Center College of Business, University of North Texas Fellow, Texas Center for Digital Knowledge Founding Chair, Society for Information Management EA Working Group [email protected]2 Michael Milutis Director of Marketing Computer Aid, Inc. (CAI) [email protected]
Enterprises that are more agile and adaptable are more able to succeed in an Information Age world that demands they do more with less, faster, while traditional boundaries blur, and the rules of engagement change. Succeeding in such a world requires that organizations skillfully manage information about their products, customers, suppliers, markets, assets, and liabilities. Fortunately, most enterprises are skilled in such matters. But succeeding in the world of today, and to a even greater extent in the world of tomorrow, also demands that enterprises master the management all of the knowledge about itself, including details about all of its people and processes, intelligence and knowledge, things and places, timings and motivations, plans and measures, rules and jobs, structures and more. We are in the early stages of developing such skills and capabilities. Enterprise Architecture (EA) is the name of this emerging discipline.
EA represents a new way of thinking about and managing the enterprise, including its information technologies. EA is all about achieving the vision of bridging the chasm between strategy and implementation, of capturing all the knowledge about the enterprise and making it available in real time for every imaginable management need, and of having a shared “language” of words, graphics, and other depictions to discuss, document, manage, and make decisions about every important aspect of the enterprise. EA is key to being agile, adaptable, interoperable, integrated, lean, secure, responsive, efficient, effective, and thereby more able to succeed in the Information Age.
The Learning Objectives of Dr. Kappelman’s EA 202 webinar include matters like: • What is EA and why should you care about it? • Why and how our mental models and language about enterprises and IT must evolve. • How to build an EA practice by building on your current capabilities in analysis, design, architecture, governance, planning, and more. • How EA helps us better manage key trade-offs such as: • Short-term value versus long-term value. • Optimizing of parts (e.g., business unit or process) versus optimizing the whole. • What to expect and assume on your EA journey.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
10/30/2011
1
Enterprise Architecture 202:Enterprise Architecture 202:Creating the Information Age Enterprise
andandBridging the Chasm Between Strategy & Execution
ITMPI005
1
1-November-201111:00 AM – 12:30 PM EST
Leon A. Kappelman, Ph.D.
Mi h l Mil i
pp ,Professor of Information Systems
Director Emeritus, Information Systems Research CenterCollege of Business, University of North Texas
Fellow, Texas Center for Digital KnowledgeFounding Chair, Society for Information Management EA Working Group
Leon A. Kappelman, Ph.D. is a research scientist, teacher, author, speaker, and consultant dedicated to helping organizations better manage their information, systems and technology assets He is Director Emeritus of the IS Research Centersystems, and technology assets. He is Director Emeritus of the IS Research Center and a Professor of Information Systems in the Information Technology & Decision Sciences Department of the College of Business at the University of North Texas, where he is also a Fellow of the Texas Center for Digital Knowledge. Dr. Kappelman is founding chair of the Society for Information Management’s (SIM) Enterprise Architecture Working Group. He has assisted many public and private organizations with technology management activities including strategic planning, governance, software development, project management, enterprise architecture, continuity of operations, and IT workforce management. He has given presentations and written articles on these and other IT management topics, and testified before the US
3
a t c es o t ese a d ot e a age e t top cs, a d test ed be o e t e USCongress on technology legislation and IT management practices. Professor Kappelman has published several books, over 100 articles, and has lectured and conducted seminars and workshops on many management, business, and technology topics in North America, Europe, and Asia. His work has been reported in the Wall Street Journal, New York Times, BusinessWeek, Newsweek, Washington Post, LA Times, and scores of other newspapers and magazines; he has appeared on CNN, CNBC, PBS, ABC World News Tonight, as well as regional television and radio stations. He brought nearly $2.5 million in research contracts to the university.
CAI Achieves IT Operational Excellence
4
10/30/2011
3
PDU CREDITS FOR THIS WEBINAR
The Project Management Institute has accredited this webinar with PDUs
FOR THIS WEBINAR
5
NOW AVAILABLE!NOW AVAILABLE!
ONLINE WEBINAR RECORDINGS
ANYTIME ACCESS!
WWW ITMPI ORG / LIBRARY
6
WWW. ITMPI.ORG / LIBRARY7 Day Free Access For All Recordings
www.twitter.com/ ITMPI
10/30/2011
4
Enterprise Architecture 202:Creating the Information Age EnterpriseBridging the Chasm Between Strategy and Execution
Leon A. KappelmanLeon A. Kappelman, Ph.D., Ph.D.Professor of Information SystemsProfessor of Information Systems
Founding Chair, Society for Information Founding Chair, Society for Information Management EA Working GroupManagement EA Working Group
ITMPI005
Founding Chair, Society for Information Founding Chair, Society for Information Management EA Working GroupManagement EA Working GroupDirector Emeritus, Information Systems Research CenterDirector Emeritus, Information Systems Research Center
Fellow, Texas Center for Digital KnowledgeFellow, Texas Center for Digital KnowledgeInformation Technology & Decision Sciences DepartmentInformation Technology & Decision Sciences Department
College of Business, University of North TexasCollege of Business, University of North TexasWebsite: http://courses.unt.edu/kappelman/
If you can’t “see” it, then you can’t effectively change it or manage it. Especially if it’s complicated or big, or will grow, evolve, or change at some point in time.
••Enterprise ArchitectureEnterprise Architecture is “the holistic set of descriptions about the enterprise over time“ [SIMEAWG]the enterprise over time . [SIMEAWG]
••Enterprise Architecture Enterprise Architecture is is modeling the enterprise.modeling the enterprise.
“All we ever know is our models ”“All we ever know is our models.”"Our models may get closer and closer, but we will never reach direct perception of reality.”
• Every model is imperfect.• But models are all we have.• Even language is a model.
EAEA is about the creation of a is about the creation of a shared languageshared language (of (of words, images, and so on) to communicate words, images, and so on) to communicate about think about and manage the enterpriseabout think about and manage the enterprise
In terms of the whole organization…In terms of the whole organization…
about, think about, and manage the enterprise. about, think about, and manage the enterprise. If the If the peoplepeople in the enterprise in the enterprise cannot communicatecannot communicate
well enough well enough to align their ideas to align their ideas and thoughts and thoughts about the enterprise (e.g., strategy, goals, about the enterprise (e.g., strategy, goals, objectives, purpose, …), objectives, purpose, …),
thenthen theythey cannot align the things they managecannot align the things they manage (e g(e gthen then theythey cannot align the things they manage cannot align the things they manage (e.g., (e.g., applications, data, projects, goods and services, applications, data, projects, goods and services, jobs, vehicles, people, …).jobs, vehicles, people, …).
• “IT and business alignment remains CIO's top concern.… Some things never change.” (InformationWeek, 3Sept08)
• “Yet again, alignment is the top priority for CIOs.” Business Alignment: The Eternal Priority” (CIO Insight, 22Mar07)
• “top IT management concerns of CIOs intop IT management concerns of CIOs in 2006 … the alignment of IT and business at their companies …according to …survey by the Society for Information Management. ” (InformationWeek, 18Sep06)
• “Alignment,” “flexibility,” “nimbleness,” “simplicity,” “agility,” and so on are design objectives or goals. They answers questions like “what do we want it to look like?”
• The answer to the question “how do we accomplish it?” – Most call “planning” or “strategic planning” and
“execution” or “implementation”; – A few, but only those thinking in a very
comprehensive and holistic sense of the term, call it “enterprise architecture.”
Artwork by Russell Douglas in The SIM Guide to Enterprise Architecture: Creating the Information The SIM Guide to Enterprise Architecture: Creating the Information Age Enterprise, Age Enterprise, 2010, CRC Press, Taylor and Francis Group, NYC, (www.crcpress.com).Enterprise Architecture As Strategy: Creating a Foundation for Business Execution, Jeanne
Artwork by Russell Douglas in The SIM Guide to Enterprise Architecture: Creating the Information The SIM Guide to Enterprise Architecture: Creating the Information Age Enterprise, Age Enterprise, 2010, CRC Press, Taylor and Francis Group, NYC, (www.crcpress.com).Enterprise Architecture As Strategy: Creating a Foundation for Business Execution, Jeanne
Brooks on the difficulties of software development …Brooks on the difficulties of software development …
“To see what rate of progress one can expect in software technology, let us examine the
“The hardest single part of building a software system is deciding precisely what to build No other part of thegy
difficulties of that technology. Following Aristotle, I divide them into essence, the difficulties inherent in the nature of software, and accidents, those difficulties
build. No other part of the conceptual work is as difficult as establishing the detailed technical requirements…. No other part of the work so cripples the system if done wrong No other part is morethat today attend its
production but are not inherent.”
"No Silver Bullet - Essence & Accidents of Software Engineering”1986 in Information Processing 86. H.J. Kugler, ed., Elsevier, 1069-1076. (Invited paper, IFIP Congress '86, Dublin) Reprinted in The Mythical Man-Month, 20th Anniversary Edition, Frederick P. Brooks, Jr., Addison-Wesley, 1995.
wrong. No other part is more difficult to rectify later.”
SIMEAWG IT Management Practices StudyAverages (Scale: 1[=awful] to 5 [=superior])
SIMEAWG IT Management Practices StudyAverages (Scale: 1[=awful] to 5 [=superior])
• 3.67 Overall average (64 questions)
• 3.92 Purpose / function of EA (7 questions)• 3.90 Potential benefits of EA (20 questions)• 3.68 ISD CMM practices and capabilities (12 questions)• 3.53 Use of requirements artifacts (10 questions)q ( q )• 3.33 Requirements practices & capabilities (15 questions)
The SIM Guide to Enterprise Architecture: Creating the The SIM Guide to Enterprise Architecture: Creating the Information Age Enterprise, Information Age Enterprise, 2010, edited by Leon A. Kappelman, CRC Press, Taylor and Francis Group, NYC, (www.crcpress.com).
Zachman’s Framework for EA …… is an ontology, a data model (schema) for all the knowledge about the enterprise.… is process and method agnostic. It doesn’t care how you get the knowledge.… posits that if you want to be aligned, agile, optimized, or whatever your enterprise design objectives, then these are the data you must have and use in order to effectively:have and use in order to effectively:
• achieve those objectives;• manage change and complexity;• manage the enterprise & all its resources
• EA is a different way of seeing, communicating about, & managing the enterprise & all of its assets, including IT.
• EA gets to essence of IT success: Knowing &
What is EA?What is EA?
communicating the organization’s requirements. • EA is key to:
– achieving & keeping business-IT alignment & other objectives.– helping the organization create value.
• EA includes many things you are already do; such as requirements analysis, system design, strategic planning, network design, standard setting, knowledge management, data warehousing, SOA, BPR, etc., etc., …– BUT EA is much, much more than that.– Still, you can build your EA practice on what
Some graphical concepts for communicating with Zachman’s Enterprise Ontology• Scope about something is depicted by width
in a cell.in a cell.– A “sliver” is indicative of narrow or limited scope –
as in a stovepipe or a particular application.– Example: Run
• Level of detail about something is depicted by depth in a cellby depth in a cell. – It depicts how much you know about it– What you don’t know you must assume.
What is EA?What is EA?• EA is a different way of seeing, communicating about, &
managing the enterprise & all of its assets, including IT. • EA gets to essence of IT success: Knowing &
communicating the organization’s requirements.communicating the organization s requirements. • EA is key to:
– achieving & keeping business-IT alignment & other objectives.– helping the organization create value.
• EA includes many things you are already do; such as requirements analysis, system design, strategic planning, network design, standard setting, knowledge management,network design, standard setting, knowledge management, data warehousing, SOA, BPR, etc., etc., …– BUT EA is much, much more than that.– Still, you can build your EA practice on what
Road to the Future: Institutionalizing EARoad to the Future: Institutionalizing EA• This is a new way of life: There is no quick fix; no silver bullet.
Road to the Future: Institutionalizing EARoad to the Future: Institutionalizing EA• This is a new way of life: There is no quick fix; no silver bullet.• This will take time and determination, as well as vision,
courage and commitment: Do not underestimate the difficulty and complexity of architecting and engineering one of humankind’s most complex objects the Enterprisehumankind s most complex objects – the Enterprise.
• Do not get discouraged: This is a revolution in thinking, a discipline, an engineering process. Change of this magnitude takes time and perseverance.
• Set realistic expectations: Things have to be implemented and modified periodically so you have to accept some risk of “scrap and rework." Progress trumps perfection.
• Don't assume anything: Make executive education and• Don t assume anything: Make executive education and technical training a continuous process. It is easy to forget long-term issues in the short-term stress of daily life.
• Learn!: The state of the art is only about 25 years old and the "playing field" still pretty level – there is still much to learn & discover, & many opportunities to create advantage & value.
You will also need some EA processes and governance bodies that integrate EA into theEA into the processes and governance activities for everything else (IT and business).
Implementation Guidelines: Getting StartedImplementation Guidelines: Getting Started• Build on what you’re already doing (including projects).• Use collaborative approaches to doing & governing EA:
– Organize an EA working group or EA council. – Learn together & work toward agreement about language, models, methods
• Get participation & commitment from IT & business p pmanagement:– At all levels (but start as high as possible). Leadership counts!
• Determine the goals, focus, scope, and priorities:– Aim for completeness & comprehensiveness. Deal with day-to-day needs.
• Embrace continuous change, learning, & communication:– Remember, it’s a journey and a process.– Evangelize. Have an “elevator speech”. Get your “converters” one at a time.
• Start small and show early success. Then build on it. y– Identify EA initiatives of most value to organization. – Help the value creators, it creates champions and wins hearts and minds.
• Monitor, evaluate, and improve on a continuous basis:– Quantify the benefits– Regularly take a hard look at EA cost-value proposition, and make it better.
• Use EA in IT for CONTINUOUS IMPROVEMENT and to COMMUNICATE WITH YOUR CUSTOMERS & STAKEHOLDERS