shifting to continuous delivery

DevOps IntroductionBringing three worlds together!

March 23rd, 2017

Copyright © 2017 Accenture All rights reserved. 2

GUILLERMO MARTINEZ

Meet the presenter

Accenture:

Technology Architect - Accenture NL

https://people.accenture.com/Experience.aspx

Allianz:

Lead DevOps Architect – Allianz Benelux

LinkedIn:

https://nl.linkedin.com/in/guillermomtzfdz/en

Email:

[email protected]

https://people.accenture.com/Experience.aspx

https://nl.linkedin.com/in/guillermomtzfdz/en

mailto:[email protected]


What is “DevOps”?

• DevOps is a new engineering culture, mind-set and practices that emphasizes the collaboration

and communication of both software developers and other information-technology (IT)

professionals while automating and streamlining the process of software delivery and

infrastructure changes.

• It aims at establishing a culture and environment where building, testing, and releasing software,

can happen rapidly, frequently, and more reliably.

Source: https://en.wikipedia.org/wiki/DevOps


Introduction into DevOps - Challenges

MANY TEAMS…

UI agencyTraditional

operations

“Legacy

System” owner

Mobile

partnersERP owner

CMS vendor

CRM owner

SaaS

Operations

(or self-

managing

teams)

Cloud

Operations

(or Shadow

IT)

What does the DevOps challenge really look like?

DevOps is “…the org structure that lets you release as fast as possible without losing control” Markos Rendell

http://markosrendell.wordpress.com/2014/09/25/paaa-is-great-for-devops-too-treat-your-platform-as-a-product/

PREFERRED (Product-oriented teams)

Development

and

Operations

Team

IB

Development

and

Operations

Team

CMS

Development

and

Operations

Team

SiteDevelopment

and

Operations

Team

Tools Platform

Development

and

Operations

Team

PIM

TRADITIONAL

Development Team

CMS Site IB

Tools PIM DB

Operations Team

CMS Site IB

Tools PIM DB

Platform

NO OPS?

CMS Site IB

Tools PIM DB

Platform

Development and

Operations Team

http://markosrendell.wordpress.com/2014/09/25/paaa-is-great-for-devops-too-treat-your-platform-as-a-product/

Do companies need a complete reorganization for working DevOps?


DevOps: the three stage conversation

Lean DeliveryTalent, Culture and

OrganizationLiquid Architecture


Introduction into DevOps – What do you need!

What do you need!

Lean Delivery

Design Thinking, Agile, Lean Engineering, DevOps,

Operations Analytics with tools and practices to enable

automation and differentiated multi-speed management and

governance

2

Talent, Culture and Organization

Aligned strategy, organization structure, talent

strategy, sourcing plans and innovative/risk taking

culture

1

Liquid Architecture

Loosely coupled, lightweight and micro-service based,

cloud native,

mobile-first Cloud-Native Platforms & Infrastructure, backed

by monitoring, analytics, and self-healing/self-scaling

3

Liquid

Architectures

Talent,

Culture and

Organization

Lean

Delivery

New ITInnovation

Agility

Cost Reduction

Dis

ruptio

n

Is DevOps only software delivery?


‘Culture eats Strategy for breakfast’- Peter Drucker

Gartner, said: "We estimate that, by 2018, 90% of organizations attempting to use DevOps without specifically addressing their cultural foundations will fail.


Netflix considers 90% of what they try to be wrong.


Introduction into DevOps - Talent Culture and Organization

Key Components

Infuse business acumen and technical skills across

design, development and operations to react quickly

to changes in business and technology environments

Ability to quickly access the extended talent

ecosystem for a range of technical skills and know-how

Generative culture focused on innovation, co-

creating and collaboration across the entire

ecosystem

Organization around services rather than an

enterprise structure. Agile teams own end-to-end

delivery of IT services, and are accountable for driving

customer/user delight

Funding and governance that encourages

“Entrepreneurial” service teams to behave as stand-

alone businesses, fully empowered and responsible

• Stage Gate Delivery

• Silo’d Organization

New ITOrganization

Talent

Culture

Traditional IT

• Full Time Employees

• Function Oriented

• Management Drives The

Experience

• Culture Promotes Efficiency

• Viewed as a Cost Centre

• Digital Pace

• Modular, Service Based

Teams

• Employees Drive the

Experience

• Culture Promotes Creativity

• Viewed as an Innovation

Engine

• Global, On-Demand

Workforce

• Network Oriented

Do you have to work Agile for implementing DevOps?


IT organizations typically

spend more time testing,

deploying and releasing

software than designing

and building it

A high proportion of

production incidents are

a result of human errors

in the manual release

of software

IT Development and IT

Operations have different

values and ways of

working that are often

not in alignment

“IT Speed: The Crisis and the Savior of the Enterprise,” A Forrester Consulting study commissioned by Chef, December 2013

Only 17% of IT teams can deliver fast enough*

Challenges . . .


Release

Confidence

Cycle-Time

Risk of

Change

• New features introduced in days or hours, not months

• Continuous experimentation without regret allows business services to be continuously tuned

• Metric-driven feedback-loops improve productivity

• Changes introduced real-time and trivial to revert

• Tests executed in representative environments automatically on check-in

• Elimination of regression defects

• Managed roll-out of new features – via A/B testing

• Business-centric metrics enable real-time service management

• Security vulnerabilities identified at build-time.

What great feels like


Benefits

Accenture’s DevOps services can help organizations maximize business value

Throughput

Teams are more

productive and can

deliver new

functionality faster

Security

Eliminate

regression defects

and release with

confidence

Time To Market

Up to 50% reduction

in

to market through

streamlined software

delivery

Cost

10% - 20% cost

reduction across

IT delivery


Introduction into DevOps - Lean Delivery Model

Most of the legacy approaches have served well and will not vanish, but Lean Delivery Practices enable

agility, innovation, and improved total cost


Introduction into DevOps - Lean Delivery Model


Introduction into DevOps - Lean Delivery

Key Components

Innovation, innovation, innovation. Agility is better than consistency.

Source: “The Lean Startup” (http://theleanstartup.com).

Capabilities Characteristics

DevOps Speed

Agile Iterative

Design Thinking Innovation

Operational Analytics Insight


Introduction into DevOps - Liquid Architecture

Architectural Journey

Liquid Architecture

Core System(s) Core System(s)

Monolith Layered / SOA

APIs

Platform & Infrastructure


Introduction into DevOps - Liquid Architecture

Characteristics

Interfaces Seamless

Business

LogicModular

Frameworks Lightweight

Platforms Open

Infrastructure Software-defined

Architectural

Component

Liquid

Architecture

Characteristic

1

2

3

4

5

Liquid Architecture

Benefits

• Speed

• Agility

• Scale

• Resiliency

• Security

• Data-Driven Decisions

• Experimentation

Additionally, De-centralized Integration, Big & Fast Data, and

Ubiquitous Security defines characteristic of cross-

components…

APIs

Platform & Infrastructure

1

2

3

4

5


Introduction into DevOps

Traditional Development and Operations

Can you go half DevOps?

Copyright © 2017 Accenture All rights reserved. 26Copyright © 2017 Accenture All rights reserved. 26

Expected Value –

Methodologies comparison

Value Released

Time

Waterfall –

Short Waterfall –

Agile –

DevOps –DevOps + AI –