governance as sustainability in the enterprise architecture discipline

<Insert Picture Here>

Governance as Sustainability in the Enterprise Architecture Discipline

Eric A. Stephens, Enterprise Architecture Director Oracle Consulting - Advanced Technology Services The Open Group Conference 31 January 2012 San Francisco, CA

Oracle Enterprise Architecture Oracle Enterprise Architecture

“Neither the importance nor the tedium of EA Governance can be

overstated.”

Copyright 2011 Oracle Corporation – Confidential 2

Introduction

•  Bombardment of new technologies continues –  Promises of magical fixes to our architectural woes

•  Critical to re-evaluate EA governance –  Processes –  Controls –  Standards

•  Risks in not doing so –  Architectural fragmentation, in color –  Misalignment to objectives


EA & The Second Law of Thermodynamics

• Closed Biological systems & entropy • Enterprise = system: entropy ensues • Funding streams and sub-optimization


Overview

• Technologies & phenomena requiring governance

• Aspects of a quality EA program •  Instilling a governance-driven technology

adoption process

TECHNOLOGIES & PHENOMENA REQUIRING GOVERNANCE


Service-Oriented Architecture (SOA)

•  “…A set of principles and methodologies for designing and developing software in the form of interoperable services…”

• Contemporary SOA adds technological innovation to older concept of modularity

•  Procurement of components not a guarantee of success

7

SOA Governance Considerations

•  What is your overall governance framework? •  What constitutes a service? •  Where in the SDLC are services sourced/designed/

created? •  What are the approval gates? •  What are the criteria for new COTS and SOA? •  Internal SOA roadshow & education


Mobile Computing – Adoption Rates

Mobile Adoption

•  CTIA - United States 2011 –  322.9M Subscribers –  102.4% Penetration rate –  29.7% Households are wireless only –  2.12T Text messages per year

•  Anecdotal study in Baldwinsville, NY (pop. ~7000) –  99% of middle school students have a mobile phone –  50% of these students have smartphones


Bring Your Own Device (BYOD)

• High-level management demands support • Younger employees prefer their own devices • Enterprises reap cost benefits • CIOs looking to exploit BYOD for productivity

gains • Poor Implementation leads to huge headaches

for IT and users


BYOD/Mobile Governance Considerations

•  Who owns the data? •  Who pays for the service? Device? •  Devices: forbidden, permitted, supported? •  Who permits the “data wipe”? User? Enterprise? •  Onboarding/off-boarding/emergency terminations •  Necessary Mobile Device Management (MDM) and

network protection


Cloud Computing

•  Elastic, self-service provisioning of pooled, measured, network-accessible computing resources

•  NIST: Three service models, four deployment models •  Adoption ranges from terror to total embrace

–  Healthcare still reluctant –  NSA seems bullish (eweek.com) –  “Why Not Cloud”

•  Hyped, but effective


Cloud Computing Governance Considerations

• Data ownership and location • Availability & control • Request processing • Procurement authority


Big Data


•  Global data creation –  2005: 150 EB (billion gigabytes) –  2010: 1.2 ZB

•  Big, yes, but also unstructured •  Movement to the cloud increases need for governance

–  Missing disks –  Laptops left in taxis, iPads on planes –  Obscure changes to Social Network privacy settings

Big Data Governance Considerations

• Standard Data Governance applies –  Architecture, Master Data Management –  Metadata management –  Privacy & Access management –  Data stewardship and ownership

•  Integrate with existing Business Intelligence Fabric


IT Consumerization

IT as Expense

Business & IT Partnership/Alignment

“There is No IT”


DIY Solutions

•  Local databases / web site proliferation •  Increase of LAMP and SaaS solutions •  Shadow IT •  Improve Time to Value (TtV) •  Twenty percent of information works built their own

solution


IT Consumerization – Governance Considerations

• Most are embracing BYOD (Avande) –  73% C-level executives report increased use, 60% adapting

IT –  88% report employees already using personal technology –  64% of IT executives consider the matter “simple” –  Risks: 66% security, 37% unmanaged data

• Your competition is figuring this out • Strategy: Trust & Facilitation


INSTILLING A GOVERNANCE-DRIVEN TECHNOLOGY ADOPTION PROCESS

23

Characteristics of Good EA Governance

• Organizationally specific •  Just enough, just in time •  (Alleged) tension of agility and governance • Well communicated and socialized •  Integrated with procurement, PMO, SDLC/ADM •  Iterative, persistent program


Technology & Process Adoption

• Comprehensive – people & process • Repeatable process with certification for new

components • Approval gates and roadmaps • Portfolio management essential • Governance-driven sustains the program


Thank You

Eric A. Stephens Enterprise Architecture Director

Oracle Advanced Technology Services

[email protected] +1 315.857.6423

@EricStephens


The Eames House in Los Angeles

http://www.youtube.com/watch?v=FRWatw_ZEQI http://www.nytimes.com/2011/12/08/garden/ice-cube-on-eameses-and-his-hometown-qa.html

"…its not about the pieces, its how the pieces work together…structure and nature as one…”


Oracle’s Practical EA Approach

People

Oracle Enterprise Architects

Process

Oracle Architecture

Development Process

Portfolio

Oracle EA Framework


Environmental Changes & Innovation

Business Strategy

Project Execution

IT-intensive Procurement &

AdoptionProject Funding

IT Governance EA Scorecard

EA Repository

Metadata, Patterns Standards, Waivers, &

Violations, Models, Reference Architectures, Strategies & Roadmaps

EA Governance

ImplementationGovernance

EA ChangeManagement

Value Measurement & Reporting

Safe Harbor

•  Oracle is pleased to present the reader with the attached presentation for the hardware, software, and/or services referenced therein. The attached presentation and its contents (collectively, "Presentation") are the confidential and proprietary information of Oracle. The Presentation may be used by You solely for evaluation of a business relationship between Oracle and You. The Presentation may not be reproduced, published, disseminated, or otherwise disclosed without Oracle's written consent.

•  The Presentation may include selected third party data, information, research and/or reference materials (collectively, "Third Party Information"). Oracle does not warrant the accuracy of the Third Party Information, which is provided "as-is." The inclusion of the Third Party Information does not constitute an endorsement of Oracle's products or services by any third party.

•  Further, this Presentation is not a commitment to deliver any future material, code, or functionality. The development, release, and timing of any features or functionality described in this Presentation remains at the sole discretion of Oracle.

•  The Presentation cannot account for all risks and other factors that may affect results or performance, or for changes in your business practices or operating procedures that may be required to realize results or performance, that are projected or implied in the Presentation.

•  The Presentation, and any discussion or negotiation of The Presentation between Oracle and You, is for informational purposes only and is not an offer by, commitment from, or contract with Oracle to provide any software or services. The Presentation is subject to change at Oracle's sole discretion.

governance as sustainability in the enterprise architecture discipline

Technology

party information

attached presentation

amp

governance

services

soa

device

service