Lean, Agile, Resilient: Crafting a Next- Generation ... · “Enterprise Architecture represents an...

Lean, Agile, Resilient: Crafting a Next-Generation Enterprise Architecture

Johna Till Johnson CEO, Nemertes Research

[email protected], @johnatilljohnso

September 20, 2018

© 2018 Nemertes Research DN6749 1

mailto:[email protected]

Agenda

• About Nemertes• EA is Dead!....• …Long Live EA!• Next-Generation EA• Best Practices in EA Development• Success Metrics for EA• Takeaways and Actionables• Upcoming Research• Q&A


ABOUT NEMERTES


About Nemertes

Topics We Cover Research We Conduct Services We Provide• Cloud and Networking

• Digital Customer Experience

• Digital Transformation

• IoT

• Next Generation Endpoints

• Security and Risk Management

• Unified Communications & Collaboration

• Benchmarks: Live discussions with IT leaders

• Surveys: Industry-leading data integrity methodology

• Vendor discussions: Product, technology analysis

• Research advisory service

• Strategy & roadmap consulting

• Vendor & technology assessment

• Cost models

• Maturity models

• Annual conference

Global research and strategic consulting firm that analyzes the business value of emerging technologies. Our real-world operational and business metrics help organizations achieve successful technology transformations. Founded in 2002.


ENTERPRISE ARCHITECTURE IS DEAD!!



EA Has Demonstrably Failed“Enterprise Architecture… has been an initiative for most financial institutions (banks, insurance companies, government, etc.) for the last five yearss or so…Most EA initiatives failed. My guess is that more than 90% never really resulted in anything useful.”---Ivar Jacobson, 2007

"... by 2012 40% of [2007’s] enterprise architecture programs will be stopped.”--Gartner

“Far too often enterprise architecture…actually creates a bottleneck for business activities and becomes an active dampener on what is possible…Enterprise architecture as its often practiced today might be broken,” –Dion Hinchcliffe, 2009

The federal enterprise architecture program has mostly failed—report, 2011


The Rise (and Fall) of the Enterprise Architect

1990 2008 2012

Impact

Why and How Did EA Fail?

• Too silo-ed from real-world business and technical environments

• Focus on slideware, not running code

• Top-down frameworks and methodologies served as bottlenecks: “You can’t” vs “Here’s how you can”

• Nebulous metrics for success (“it seems like a good idea…”)


LONG LIVE ENTERPRISE ARCHITECTURE!


The Rebirth of Enterprise Architecture

• “There are three things required to make DevOpshappen: Culture, tools, and enterprise architecture.”—Gene Kim, 2016



What Is Enterprise Architecture? "Enterprise architecture (EA) is a discipline for proactively and holistically leading enterprise responses to disruptive forces by identifying and analyzing the execution of change toward desired business vision and outcomes.” --Gartner

“How the elements of an organization fit together,” –Enterprise Architecture Body of Knowldege (EABOK), 2004

“Enterprise Architecture represents an approach to developing a general conceptual plan which describes structure of the enterprise with its separate components and links between them; it defines the principles and rules for the design and operation of the organizational structure, the processes and information systems in the enterprise, and…synchronizes technology with business goals.” –Capp. Dankova, 2009

?


What Is Enterprise Architecture?

“A plan for deploying and connecting stuff to make the business work right,” –Nemertes, 2018

?Business

Drivers

Technology

ImperativesArchitecture

Decisions

Technology

Selection

Vendor

Choice

NEXT-GENERATION ENTERPRISE ARCHITECTURE


Goals of A Next-Generation EA

1. Document the critical components of the software and infrastructure that enables present and future business capabilities

2. Define relationships between these components

3. Provide guidance on physical location (cloud, on premise, mobile) based on business requirements

4. Include embedded security

5. Support agility (dynamic change) and reusability



IoTmobile

Remote branch

Remote branch

Multicloud LegacyOn Prem

ComputeComputeComputeCompute

Location, Location, Location!

AWS,Azure,Etc

SaaS

Data centersMobile devicesIoT sensors, controllers

Applications, Services, Microservices


AppAppApp AppApp App

IoTmobile

Remote branch

Remote branch


Compute Compute ComputeCompute

APIs, integration

among cloudsAPIs,

integration between

clouds and prem

Service calls locally, to cloud, to on-premise resources

O Data, Where Art Thou?


Data


Data Data Data Data DataData

IoTmobile

Remote branch

Remote branch


Compute Compute ComputeComputeLocal

storage & cache

Local storage & cache

Cloud-based data storage (compliance,

regulatory, EoL)

Legacy and on-prem data

Processing: Power vs Cost


Data



IoTmobile

Remote branch

Remote branch


Compute Compute Compute ComputeComputeComputeCompute

Processing limitations

Usage-based processing

The Many Flavors of Networks


Data



IoTmobile

Remote branch

Remote branch



Network Network Network Network

Cellular, WiFi,

dedicated IoT

MPLS, business Internet, SD-WAN, 5 G (coming)

Direct connect, WAN exchange (also cloud i/o)

Direct, to cloud, etc.

Data protection, authorization,classification, encryption (in situ/intransit), DLP, etc

One Architecture to Secure Them…


IoTmobile

Remote branch

Remote branch


Compute Compute ComputeCompute

MDM

IoT Security

AppSec

CASB

Advanced EndpointSecurity (AES)

Firewalls (physical, virtual) Cloud SSO

Behavioral Threat Analytics (BTA)

Legacy Security (RACF)

Next-Generation EA


Data



IoTmobile

Remote branch

Remote branch



Network Network Network Network

BEST PRACTICES



Take a DevOps Approach

• Eliminate silos. Engage business, engineering, and operations in architecture development.

• Engage SMEs for each component. Maintain subject-matter expertise in each core “silo” (app dev, compute, storage, data, networking, cybersecurity, etc.) and engage with SMEs throughout.

• Develop architecture in “chunks”—fast turnaround, testable in parallel

• Iteratively test for integration across subject-matter silos


Engage Security Throughout

“The days are over when we just reviewed application security and the environment at the end of a project. Now we have to integrate that into daily work.”

Cybersecurity


Test Often, Fail Fast

• Instantiate a reference architecture. As much as possible, develop a reference architecture (instantiated with real-world products)

• Reference architecture should be modularly designed (slot out vendors/products with similar functionality).

• Simulate real-world environment (latency, computational bottlenecks, etc. )

• Test regularly, acknowledge failures, improve, iterate.

SUCCESS METRICS


What is the Business Value of EA?

1. Speed. Having an effective EA means you’re able to deploy technologies faster, thanks to: o Less overhead required to assess vendors/technologieso Better-understood integration requirements and capabilitieso Re-usable “utility” software and business components that can be

leveraged across the enterprise

2. Accuracy. Fewer blind alleys and cul-de-sacs (“you can’t get there from here”) because issues have been addressed in advance.

3. Future-proofing. Effective EAs are scalable, extensible, and support functions above and beyond current defined requirements.


EA Success Metrics

• In Nemertes’ research, having an architecture correlates highly with operational success metrics: o Time to deploy (infrastructure, applications)o Time to detect, understand, contain threats (cybersecurity)

• Potential correlation with business success metrics: o Cost to deployo ROIo TCOo Revenue generated/savedo Ability to meet compliance/regulatory constraints on a timely basis

• Bottom line: Use established metrics where available; eschew hand-wavey metrics


ACTIONABLES AND TAKEAWAYS


To Make EA Effective…

• Take a DevOps approach. Engage business, engineering, and operations teams in architecture development ab initio.

• Maintain subject-matter expertise. Apps, data, compute, network folks should think across all locations (versus having location-specific experts)

• Engage security throughout and across silos. • Test often, fail fast. “On-paper” architectures too often fail.

Wherever possible, construct POCs to determine potential roadblocks and challenges.

• Rely on established metrics to show benefits. • Stay engaged in the community! Keep attending WSTA, work with

other organizations.



Participate in Our Research

In progress –currently recruiting participants

Begins October 2018 –currently recruiting participants

To participate, please click the link in your “attachments” tab

Current Status Call to Action

To participate, please click the link in your “attachments” tab

Thank you!

[email protected]

[email protected]

@Nemertes


Lean, Agile, Resilient: Crafting a Next- Generation ... · “Enterprise Architecture represents an...

Documents

Transcript of Lean, Agile, Resilient: Crafting a Next- Generation ... · “Enterprise Architecture represents an...