Practical Enterprise Architecture with TOGAF
Post on 18-Jul-2015
Embed Size (px)
Establishing SCI Enterprise Architecture Practice AgendaChallengesEnterprise Architecture - overviewThe desired state end goalPractical steps how do we get thereChallenges
Effective Architecture Planning Current Architecture Planning
3ChallengesRapidly Evolving Business Capabilities, Aggressive Implementation Timelines -> Growing projects queue, Complex Project Management, Limited ability to extract common requirements for reusable solutions, Delays in providing business capabilities, Affected revenueCapabilities development is DRIVEN by resource availability > Delays in providing business capabilities; Limited ability to extract common requirements for reusable solutions, Affected revenue, Long term costLack of architecture governance > Independently evolving architectures for Retail and Enterprise Development products > Competing data and functionality, Limited impact and risk analysis; Limited emerging technologies adaptability, Increased short and long term costLack of traceability between business goals\ capabilities\ applications functionality\ information and data flow\ IT infrastructure > Non-transparent ROI, Impacted products integrity and quality, Increased long term costRedundant environments > Doubled maintenance and support effort, Increased short term cost 4Challenges contdInconsistent Platforms and Technologies (example Mule vs. BizTalk, different code repositories) Numerous Applications Internal Interdependencies Redundant Legacy Systems Limited Documentation of Legacy SystemsWhat is EA? If SCI is A Bowling Alley Pins - Solutions SCI provides to its ClientsWhat Would Be A Ball? Hint: Objective Is Obvious - Knock Down Maximum Pins With One Ball
What is EA? contdThe ball is a set of projects that are strategically picked to meet as much as possible objectives within a single effortGetting the most benefits from the effort = Effectiveness = Better ROITo identify that set of projects we need first to understand:Current and planned Business Capacities and ProcessesCurrent and planned state of Applications FunctionalityCurrent and planned state of IT InfrastructureRelations between all of them
What is EA? contdWe are NOT talking about rocket scienceWe ARE talking about:Using common senseBeing systematicAvoiding misunderstandingsKnowing what we are doing before we startKnowing why we are doing itLearning from the best practice of othersTalking to business users in business termsDocumenting only relevant information, but not less then thatUsing common sense
Why EA?Architected business information systems will have:A greater ability to respond to new demandsA greater business value to the organizationA greater ability to use new technologyA faster, simpler and cheaper procurement processThe ability to support a faster time-to-market
To support a faster time-to-market by
Creating a common language and repeatable processStoring knowledge and re-useable factsRe-use promotes continual qualityRe-use avoids reworkSurprising reuse savingsManaging business and technical complexityTracing impacts across many projectsCollaborating with many stakeholder views in one repository Why EA?
What makes that bowling ball to roll the most efficient way? Why EA?Enterprise Architecture PracticeWhats in EA Scope ?Whats in EA ScopeWhat:Create Business and Technical Reference Models - TaxonomyEstablish rules to record what, where, when, how, who and WHY
Why:Creates a single vocabulary and terminologyCreates a library of reusable building blocks Avoids redundant functions = Less reworkPoint of order/sanity in the chaos agile environmentEnables cost effective solutioning and development
Whats in EA Scope
What:Defining StakeholdersDefining a Viewpoint for each Stakeholder- set of Stakeholders concernsDefining Views artifacts that address a concerns of the specific Stakeholder (Viewpoint)
Why:To avoid producing a document for a sake of documentation, all produced artefacts should serve the purposeTo make the whole effort cost effective and easy in implementation.To assess the change impact effectively in future product iterations
Whats in EA Scope
What:Model Corporate Knowledge using a managed disciplineCreate full Traceability through business goals\ business capabilities\ applications functionality\ information and data flow\ IT infrastructure
Why:Transparent ROIBetter adaptability for changes driven by business and technology = Corporate AgilityProvides all necessary information for better decision makingResults in products integrity and qualityEnables cost effective solutioning and development
Whats in EA ScopeWhat:Establish architecture governance process Architecture Review Board
Why:Guards enterprise sanity in the agile reality Ensures the best quality of solutions and proper risk assessmentKeep solutions aligned with enterprise goals and architecture Provides ability to catch mistakes at the early stagesProvides forum for ideas/ knowledge exchangeAvoids unnecessary rework and financial lossResults in products integrity and qualityEnables cost effective solutioning and development
Whats in EA ScopeWhat:Current and Target Business Architectures = Business Capabilities/Products RoadmapCurrent and Target Applications and Information/Data Architectures = Application/Systems RoadmapCurrent and Target Technology Architectures = IT Infrastructure RoadmapAll roadmaps include transitional stages to meet intermediate objectives
Why:Iterative approach will ensure goals achievement through meeting all planned objectives All together = the realistic strategic plan based on clear logical decisions To reiterate the main rule of the EA practice It all should make sense
How do we get there?Steps to establish EATreat establishing of the SCI EA practice as an internal project and onboard it with the PMO.Identify EA evolved business and technical SMEs, their roles and responsibilitiesCreate a list of concerns to focusPlan communication methodsDevelop change impact/risk assessment methodologyEstablish and Agree on Principles, Standards and Governance Choose an EA FrameworkChoose a tool to model and populate EA Asset RepositoryIncorporate an EA practice into current project management methodology in close collaboration with the PMOEnforce architectural controlEstablish Architecture Review Board (ARB) to implement principles and standards by constraining a new development.Establish Incremental EA model development methodIts not realistic to make all the work at once.EA Framework and Model Development Method TOGAF Architecture Development Method - uses a step-by-step approach to create a method for developing Enterprise Architecture and helping to establish a framework.
The ADM is an iterative process, not only as the whole process but also between and within phases.
20TOGAF ADMHighly customizable methodCan be applied to any enterprise task/changeEach step has a comprehensive set of deliverables that is customizable based on needs PMI and Agile compatibleResults in an organization-specific architecturemore reusable building block assets Each iteration becomes easier and has more reusable building blocks to useIncreases CMM to Level 3 after successful completion of one full iteration.
EA Asset Repository
Zachman FrameworkZachman (1987) notes several advantages of his framework:Improving professional communications within the information systems community.Understanding the reasons for and risks of not developing any one architectural representation.Placing a wide variety of tools and/or methodologies in relation to one another.Developing improved approaches (including methodologies and tools) to produce each of the architectural representations, as well as possibly rethinking the nature of the classic application development process as we know it today.
In addition to all above, Zachman Framework is highly customizable and can be applied to various enterprise architectures
Advantages of Zachman Framework A good modeling tool must support Deliverables, Artefacts and Building BlocksAvailable Tool Sparx EAProvide Knowledge management & re-use Support the visual modeling of facts Support stakeholder and role views Generate documents, reports, diagrams & matrices Accelerate sharing and collaboration Provide Baseline changes to manage requirements Trace Requirements from business to implementation Be easy to use and customize for your project Support Industry Open Standards & Frameworks Be highly scalable for enterprise teams Be Affordable and widely used
Ensure governance across all projects Think Big - robust, scalable, secured, reusableStart Small - scale up while accumulating expertise Move Fast cross-train staff, design and build in iterationsBuild out enterprise business services aligned with stakeholders strategic planDevelop and adhere to a reference architectures, frameworks and open standards up frontEA set of mindCreates a common language and repeatable processCollaborate with many stakeholder views in one repository Store knowledge and re-useable factsManage business and technical complexityTrace impacts across many projectsRe-use promotes continual qualityRe-use avoids reworkSurprising reuse savingsIt all makes senseReiterating EA BenefitsNext StepsGet Support from the Leadership group for the EA initiative.Establish EA Team.Establish EA principles and standards.Tailor SCI EA Framework in more details Define deliverables for each step in the ADMCustomize Zachma