Architecture Series 5-5 Effective Enterprise Architecture Action Plan

3,240 views

Published on

Identify Enterprise Architecture activity & SDLC process gaps. Suggest agile top-down Enterprise Architecture actions to bridge those gaps.

Published in: Business, Technology
0 Comments
11 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,240
On SlideShare
0
From Embeds
0
Number of Embeds
50
Actions
Shares
0
Downloads
0
Comments
0
Likes
11
Embeds 0
No embeds

No notes for slide
  • Enterprise Architecture as Corporate Strategy - Introduction
  • Architecture Series 5-5 Effective Enterprise Architecture Action Plan

    1. 1. Architecture Series 5-5 Effective Enterprise Architecture Action Plan <ul><li>Frankie Hsiang – Enterprise Technologist </li></ul><ul><li>[email_address] </li></ul>Architecture Series 5-5 - Effective Enterprise Architecture Action Plan
    2. 2. Architecture Series 5-5 - Effective Enterprise Architecture Action Plan Audience & Objectives <ul><li>Audience - Senior Business and IT executives, managers, architects, and other key System Development Life Cycle (SDLC) roles. </li></ul><ul><li>Objectives - Identify common architecture activity & SDLC process gaps. Suggest agile top-down Enterprise Architecture (EA) actions to bridge those gaps. </li></ul>
    3. 3. Business Challenges & EA <ul><li>Business proactively seeks meeting fast evolving customer needs. </li></ul><ul><li>Business reacts to mission change. </li></ul><ul><li>Manage operation costs and efficiency. </li></ul><ul><li>Government regulatory compliance. </li></ul><ul><li>Enterprise Architecture is a proven tool to address those business challenges. </li></ul><ul><li>Goals : Better, Faster, and Cheaper business operations. </li></ul>Architecture Series 5-5 - Effective Enterprise Architecture Action Plan
    4. 4. Enterprise Architecture Improves Business Architecture Series 5-5 - Effective Enterprise Architecture Action Plan <ul><li>Architecture work is a set of planned activities that need business motivation, management support, financial investment, and technical resources to demonstrate its strategic business value. </li></ul><ul><li>Goals : Build agile, high quality, and yet cost effective IT operations, and systems to enable First-Class business operations. </li></ul>
    5. 5. Architecture Definition Architecture Series 5-5 - Effective Enterprise Architecture Action Plan <ul><li>Enterprise Architecture - The alignment of business vision and operations with IT investment to produce optimized business results and maintain high quality and yet cost effective IT operations </li></ul><ul><li>System Architecture - The fundamental organization of a system embodied in its components, their relationships to each other and to the environment and the principles guiding its design and evolution - ANSI/IEEE 1471-2000. </li></ul><ul><li>System Of Record (SOR) - An information storage system which is the authoritative data source for a given data element or piece of information. </li></ul>
    6. 6. Effective Enterprise Architecture Architecture Series 5-5 - Effective Enterprise Architecture Action Plan <ul><li>Align business vision and operations with IT investment to produce optimized business results and maintain high quality and yet cost effective IT operations. </li></ul><ul><li>Business driven, proactive and collaborative across the entire enterprise, and better use of enterprise information resources. </li></ul><ul><li>Guide by EA, and EA Assessment framework. * </li></ul><ul><li>Actionable, accountable, measurable, and result driven action plan. </li></ul><ul><li>* See Reference # 2, 3, 4 </li></ul>
    7. 7. EA Program Execution Architecture Series 5-5 - Effective Enterprise Architecture Action Plan Select EA methodology & assess progress Gain C-level executives support Business operating model IT engagement & governance model IT architecture definition, & optimization EA methodology adoption Guidance, compliance & control Culture change
    8. 8. Common Architecture Issues Architecture Series 5-5 - Effective Enterprise Architecture Action Plan Strategic Operational
    9. 9. Analysis & Synthesis to Action Architecture Series 5-5 - Effective Enterprise Architecture Action Plan Identify Issues Synthesis Root cause analysis Actions <ul><li>project plan lacks details </li></ul><ul><li>Not familiar with SDLC </li></ul><ul><li>Lack of communication </li></ul><ul><li>Late communication </li></ul><ul><li>Lack of reusable design </li></ul><ul><li>Patterns </li></ul><ul><li>Insufficient enterprise </li></ul><ul><li>Solution </li></ul><ul><li>… </li></ul><ul><li>Projects over budget & time </li></ul><ul><li>Not meeting business needs </li></ul><ul><li>Lack of design review resource </li></ul><ul><li>PM engages architect late </li></ul><ul><li>Dev team not following guidance </li></ul><ul><li>Document lack of details or too much details </li></ul><ul><li>… </li></ul>Theme Inconsistent Executive Support Theme Fragmented IT Engagement & Mgmt Theme Lack of IT Architecture Guidance Action Integrated Executive Support Action Integrated IT Engagement & Mgmt Action ARB provides IT Architecture Guidance
    10. 10. Theme: Inconsistent Senior Executives Support Architecture Series 5-5 - Effective Enterprise Architecture Action Plan <ul><li>Is major IT investment guided by architecture roadmap? </li></ul><ul><li>Is architecture result measurable in time, quality, and money? </li></ul><ul><li>Are there enough architecture resources? </li></ul><ul><li>Do architects work on strategic tasks? </li></ul><ul><li>Is there SDLC role level accountability on each activity? </li></ul><ul><li>Note: EA is about business transformation. Senior executives leadership and continues focus on strategic EA activities is crucial for EA program success. </li></ul>
    11. 11. Action: Integrated Senior Executives Support Architecture Series 5-5 - Effective Enterprise Architecture Action Plan <ul><li>Integrated Business & IT Executives Steering Committee to define visions, set business priority, and IT programs funding priority. </li></ul><ul><li>Major IT program funding request must provide business plan and architecture overview, & guided by Roadmap. </li></ul><ul><li>Routine review program status and architecture risks and exceptions report. </li></ul><ul><li>Ensure better business operations from good IT investment, also reduce architecture risks, and minimize exceptions. </li></ul><ul><li>Result is better strategic Business – IT alignment, appropriate accountability to all parties involved, and better enterprise risk management. </li></ul>
    12. 12. Theme: Fragmented IT Engagement & Governance Architecture Series 5-5 - Effective Enterprise Architecture Action Plan <ul><li>Lack of architecture resources, and work on tactical tasks mostly. </li></ul><ul><li>Lack of SDLC role level accountability on architecture activities. </li></ul><ul><li>Architecture result is not measurable in time, quality, and money. </li></ul><ul><li>Architecture happens after system construction started. </li></ul><ul><li>Lack of integrated architecture view among business, application, information, technology, infrastructure, and security. </li></ul>
    13. 13. Action: Integrated IT Engagement & Governance Architecture Series 5-5 - Effective Enterprise Architecture Action Plan <ul><li>Integrated Business and IT PMO. </li></ul><ul><li>Enforce SDLC process to all IT projects and all SDLC participants. </li></ul><ul><li>Architecture work is a set of planned activities. In SDLC Planning phase, Project Manager engages architect to plan resources, activities, and schedule for all architecture activities. </li></ul><ul><li>Identify single point of accountability for each SDLC activity. </li></ul><ul><li>Ensure reviewer understanding and quality review artifacts at review gate </li></ul><ul><li>Create Architecture Review Board (ARB) as the technical authority to promote integrated architecture view. ARB produces routine architecture risk and exceptions report to CIO and Executives Steering Committee. </li></ul><ul><li>Development runtime environment (database) availability is gated by planning, and requirements review result. </li></ul><ul><li>Accelerate SDLC adoption campaign on both IT and Business areas. </li></ul><ul><li>Result is appropriate accountability to all parties involved, better architecture governance, high quality deliverables from review gates, and improved architecture risks and exceptions reporting. </li></ul>
    14. 14. Architecture Review Board (ARB) Architecture Series 5-5 - Effective Enterprise Architecture Action Plan <ul><li>ARB is a group of architects with technical authority to </li></ul><ul><li>Promote integrated architecture view among business, application, information, infrastructure, and security. </li></ul><ul><li>Enforce architecture governance </li></ul><ul><li>Verify Business – IT architecture alignment </li></ul><ul><li>Provide technical guidance to project teams </li></ul><ul><li>Set consistent architecture review practice </li></ul><ul><li>Review & approve major IT program architecture </li></ul><ul><li>Share business domain and technical knowledge among reviewers. </li></ul><ul><li>Produces routine architecture risk and exceptions report to CIO and Executives Steering Committee. </li></ul>
    15. 15. Theme: IT Architecture Guidance Architecture Series 5-5 - Effective Enterprise Architecture Action Plan <ul><li>Architecture happens after system construction started. </li></ul><ul><li>Major IT investment is not guided by architecture roadmap. </li></ul><ul><li>Enterprise Architecture initiative is too broad and time consuming. </li></ul><ul><li>Insufficient reusable design, and integration patterns. </li></ul><ul><li>Inconsistent architectural structure, and poor technical communication. </li></ul><ul><li>Lack of integrated architecture view among business, application, information, technology, infrastructure, and security. </li></ul>
    16. 16. Actio n: IT Architecture Definition & Optimization Architecture Series 5-5 - Effective Enterprise Architecture Action Plan <ul><li>Good Software Engineering : Business use case driven, and architecture centric development practice. </li></ul><ul><li>Promote standard technologies, layered architecture, common design patterns, and shared services to reduce development and maintenance cost. </li></ul><ul><li>Build ARB to promote integrated architecture view. See ARB slide for details. </li></ul><ul><li>Better technical communication via common architecture visual notations. Business common notations for executives, and business audience. Technical common notations (UML, 4+1 views) for technical audience. </li></ul><ul><li>Business functions based System Of Record (SOR) definition. </li></ul><ul><li>Document baseline LOB architecture incrementally . </li></ul><ul><li>Document to-be state LOB architecture one project at a time. Project team takes some ownership on EA alignment. </li></ul><ul><li>Create Architecture Roadmap to guide strategic business and IT investment. Revise Roadmap annually. </li></ul><ul><li>Identify key showcase projects for each LOB as SDLC examples. </li></ul><ul><li>Result is actionable enterprise architecture, business driven SOR definition, better technical communication, and lower total cost. </li></ul>
    17. 17. Good Software Engineering Architecture Series 5-5 - Effective Enterprise Architecture Action Plan <ul><li>Business Use Case Driven </li></ul><ul><li>SPA promotes good software engineering </li></ul><ul><li>S eparation of Concerns – Layered, and componentized architecture definitions. FEA: PRM, BRM, SRM, TRM, DRM. * </li></ul><ul><li>P atterns driven system design, integration and communication consistency. </li></ul><ul><li>A rchitecture centric solution development. </li></ul><ul><li>* See Reference # 2, 3, 4 </li></ul>
    18. 18. Document Baseline LOB Architecture Incrementally Architecture Series 5-5 - Effective Enterprise Architecture Action Plan <ul><li>High level business use cases. Factor in customer needs, time line, and budget for documenting the history. </li></ul><ul><li>Create LOB business functions catalogue, including functions, data, systems, owners, users, and maintainers. </li></ul><ul><li>Business functions based, or organizational structure neutral, System of Record (SOR) definition. </li></ul><ul><li>Apply common architecture structure and visual notations for better technical communication. Power Point or Visio business diagrams for executives and business audience. UML based diagrams (4+1 views) for technical audience. </li></ul>
    19. 19. Create Architecture Roadmap Architecture Series 5-5 - Effective Enterprise Architecture Action Plan <ul><li>Research and analysis of current state baseline architecture to identify common business themes. </li></ul><ul><li>Work with business owners to identify business priority, gaps and identify keeper systems. </li></ul><ul><li>Create long term roadmap to guide strategic business transformation and IT investment. </li></ul><ul><li>Strategic IT investment needs to align to the Roadmap which is the result of EA alignment. </li></ul><ul><li>Revise roadmap annually. </li></ul>
    20. 20. Agile EA – Increase Communication & Reduce Complexity Architecture Series 5-5 - Effective Enterprise Architecture Action Plan <ul><li>Focus on People and Communication. </li></ul><ul><li>Routinely display updated EA models & business processes in users workspace – increase communication and demonstrate value. </li></ul><ul><li>Keep It Simple, and Stupid (Short): KISS </li></ul><ul><li>Standardize business processes and technologies </li></ul><ul><li>Separation of Concerns: Divide and Conquer </li></ul><ul><li>Layered and componentized business and technologies - reduce inter-dependency. </li></ul><ul><li>Agile & Iterative Process: Demonstrate value early and iteratively. Agility from fast and short iterative process cycle. </li></ul>
    21. 21. Culture Change Takes Time Architecture Series 5-5 - Effective Enterprise Architecture Action Plan <ul><li>Issues identified, good action items and engagement & governance plan created, capital invested, organization supports architecture program. But where is improvement? </li></ul><ul><li>It sill takes time to improve from current state to future state. How soon? </li></ul><ul><li>Paying long term architecture debt needs continuous financial and people investment. </li></ul>
    22. 22. Key ideas to take away <ul><li>Deep adoption of EA framework </li></ul><ul><ul><li>Strong and consistent executives support, good IT engagement & governance model, and consistent IT architecture definition & optimization. </li></ul></ul><ul><ul><li>Agile and iterative architecture approach </li></ul></ul><ul><ul><li>SDLC training to IT and business partners. </li></ul></ul>Architecture Series 5-5 - Effective Enterprise Architecture Action Plan
    23. 23. Reference <ul><li>“ Enterprise Architecture as Strategy “ ISBN 1-59139-839-8 </li></ul><ul><li>E-Gov FEA http://www.whitehouse.gov/omb/egov/a-1-fea.html </li></ul><ul><li>OMB FEA_Practice_Guidance_Nov_2007.pdf </li></ul><ul><li>OMB FEA Program - EA Assessment Framework 2.2 </li></ul><ul><li>DoDAF http://www.defenselink.mil/cio-nii/cio/earch.shtml </li></ul><ul><li>The Open Group – TOGAF 8.1.1 http://www.togaf.org/ </li></ul><ul><li>Zachman Framework http://www.zifa.com/ </li></ul><ul><li>“ Architecture Series 5-1 - EA as Corporate Strategy - Introduction.ppt” – Frankie Hsiang </li></ul>Architecture Series 5-5 - Effective Enterprise Architecture Action Plan

    ×