Developing a Results Driven Enterprise Architecture_September ...


Published on

Published in: Business, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Developing a Results Driven Enterprise Architecture_September ...

  1. 1. Mark Griffith State of North Carolina - Senior Enterprise Architect Thursday, September 11, 2003, 1:15 PM - 2:30 PM Developing a Results-Driven Enterprise Architecture · STRATEGY and PLANNING · QUALITY ASSURANCE ENTERPRISE ARCHITECTURE TECHNOLOGY ASSISTANCE
  2. 2. Agenda <ul><ul><li>Overview of North Carolina IT Governance </li></ul></ul><ul><ul><li>IT Project Review Process </li></ul></ul><ul><ul><li>Life Cycle of IT Investments </li></ul></ul><ul><ul><li>Overview of the NC Enterprise Architecture </li></ul></ul><ul><ul><li>Enterprise Architecture Review Findings </li></ul></ul><ul><ul><li>Overview of the Resulting Changes to the EA </li></ul></ul>
  3. 3. Governor’s Office Governmental Lines of Business (Also Known as State Agencies) State CTO Head of ETS COO CFO CSO CRM & Public Relations State Chief Information Officer Statewide IT Procurement Statewide IT Leadership Central IT Agency NC IT Governance
  4. 4. <ul><li>Enterprise Technology Strategies Office </li></ul><ul><ul><li>Review agency IT projects and recommend approval to governing bodies. </li></ul></ul><ul><ul><li>Provide leadership, guidance, and mentoring to agencies on approaches to IT, IT procurement, and IT project management. </li></ul></ul><ul><ul><li>Independent Verification & Validation on key projects, services, and systems. </li></ul></ul><ul><ul><li>Provide enterprise IT planning and strategies for the State CIO and governing bodies. </li></ul></ul>NC IT Governance
  5. 5. NC IT Governance Governor State Chief Information Officer Information Resource Management Commission Other IT Boards and Commissions North Carolina General Assembly Appoint Appoint Representation Support Advice Appoint
  6. 6. Project Closeout Project Review & Closeout Project Review Process Monthly Project Status Reporting and Independent QA Reviews IRMC Project Certification Project Concept Definition Project Implementation Agency Strategic Plan Business Case Statewide and agency technical architectures - security & application architectures
  7. 7. Life Cycle of IT Investments Phase 1 – Planning, Budgeting and Funding (State Expansion Budget Process) Phase 3 - Operation, Maintenance and Retirement Phase 2 - Project Certification and Implementation <ul><li>Potential Investments Approved by Agency </li></ul><ul><li>Potential Investments Certified by State CIO and Reviewed by IRMC </li></ul><ul><li>Potential Investments Included in Governor’s Budget </li></ul><ul><li>Projects Funded by General Assembly </li></ul><ul><li>Candidate IT Investments for Agency Review </li></ul><ul><li>Operational Assets Under Budget Review for Cost-Effectiveness </li></ul><ul><li>Completed Projects Creating Operational Assets </li></ul><ul><li>Projects Being Implemented </li></ul><ul><li>Certified Projects </li></ul>NC Enterprise Architecture
  8. 8. <ul><li>North Carolina Enterprise Architecture </li></ul><ul><ul><li>It is an Enterprise-Wide Technical Architecture; we call it a Statewide Technical Architecture. </li></ul></ul><ul><ul><li>It is NOT currently an Enterprise Business or Information Architecture. </li></ul></ul><ul><ul><li>It is NOT a product list. </li></ul></ul><ul><ul><li>We have a mature architecture. We began using the STA as a framework for projects in 1997. </li></ul></ul><ul><ul><li>We recently completed a self-directed review. </li></ul></ul>IT In North Carolina
  9. 9. EA Review Findings <ul><li>We Found That: </li></ul><ul><ul><li>Agencies often had difficulty interpreting the principles, practices, and standards. </li></ul></ul><ul><ul><li>There was resistance, on the part of some agencies, to following the STA. </li></ul></ul><ul><ul><li>The technical architecture was not very usable. </li></ul></ul><ul><ul><li>The technical architecture was not current. </li></ul></ul><ul><ul><li>Change happened very slowly. </li></ul></ul><ul><ul><li>The architecture team was too small. </li></ul></ul>
  10. 10. EA Review Findings <ul><li>We Found That: </li></ul><ul><ul><li>The technical architecture was too narrowly focused. </li></ul></ul><ul><ul><li>There were inconsistencies in the architecture. </li></ul></ul><ul><ul><li>We did not have a way of measuring whether having an Enterprise Architecture was having the desired effect. </li></ul></ul><ul><ul><li>The supporting products and processes were often poorly defined. </li></ul></ul>
  11. 11. Presentations Glossary Workgroups & Committees White Papers Purchasing Contracts Implementation Guidelines Policies & Legislation Principles, Practices, Standards Architecture Products Informational items that comprise the enterprise technical architecture.
  12. 12. NC Enterprise Architecture Maturity Review Evergreen Strategy Training Plan Content Development Governance Architecture Processes Processes are the methods used to maintain the Architecture.
  13. 13. Contact Information Mark Griffith Senior Enterprise Architect [email_address] State of North Carolina Enterprise Technology Strategies Office PO Box 17209 Raleigh, North Carolina 27619-7209 North Carolina Enterprise Architecture Website