HP Software Customer Forum FY14

DevOps – means no more testing right?

Stephen Smith

HPE Software Presales Business

Consultant

Setting the Scene

– A brief history

– What is the driving force behind DevOps

– A high level view of what DevOps is

– Guiding principles

– Continuous Integration and Testing

– A brief view of how HPE does it

The Evolution

– 1991: Continuous Integration (CI) named and proposed by Grady Booch

– 2001: Agile Manifesto was written, its 1st principle says:

“Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.“

– 2006: CI coined by Martin Fowler

– 2006 – 2010: CI evolved into Continuous Delivery (CD)

– 2009: The term DevOps was coined, and the first "DevOps Days" conference held

– Now: DevOps

– CI is commodity.

– Integrated CD tools focus on deployment and pipeline management.

– Continuous Assessment

– Expanding integrations with cloud

Digital Disruption defines today’s business climate

New Business ModelsThe Idea Economy

Cloud, mobility, IoT are redefining

how applications and devices are

written and delivered

No business, industry or

government is safe-and

many are both disrupted and

disruptor

Turning ideas into new

products or services has

never been easier

The Third-Platform is here

Financial Services… Disrupted

215 websites

Welcome screen

25+ countries

“Our busiest branch in 2014 was the 7:01 from Reading to Paddington – over 167,000 of our customers use our Mobile Banking app between 7am and 8am on their commute to work every day.”

– Ross McEwan CEO Royal Bank of Scotland

“The customer requests service and advice, 90 per cent of

transactions now takes place online, and most of them are done

after dinner. We must dialogue with the customer much more and

at all hours. The size of the branch network will be determined by

this evolution”– Federico Ghizzoni – CEO Unicredit

Digital landscape

Source: Goldman Sachs Fortnightly Thoughts intern survey, 2013

COMING OF AGE

One of the largest generations in history is about to move into its prime spending years. Millennials

are poised to reshape the economy; their unique experiences will change the ways we buy and

sell, forcing companies to examine how they do business for decades to come.

Millennials = Disruption: How important is it to own the following?

DevOps

Reduce

Latency

Increase

Automation

Increase

Visibility

Kaizen*

Customer orientationTotal quality controlRoboticsQuality circlesSuggested systemAutomationDiscipline in the workplaceTotal productive maintenance (TPM)Kanban (inventory control)Quality improvementsJust-in-time (JIT)Zero defectsSmall group activitiesCooperative labor/managementProductivity ImprovementNew product development

* Japanese business philosophy of continuous improvement of working practices, personal efficiency, etc.

• Not a product, spec, job title

• No one true authority

• No “one way”

People

Process Technology

However, getting to DevOps calls for a collaborative approach

https://www.forrester.com/Brief+Break+Your+Bad+DevOps+Habits/fulltext/-/E-res122276

Leadership and support through the change is

essential. Create a learning culture that seeks no

blame for failure but looks for opportunities to improve.

Organizations who have made the shift report that

employees find becoming customer-focused energizing and

rewarding, but the transition is unsettling.

DevOps represents an upending of the structure of the org from

an internally focused set of functional silos with accountability for

arbitrarily set objectives to an externally focused set of product

teams with accountability for customer satisfaction and,

ultimately, profit and loss.

PlanningApp

DevelopmentApp Testing

App

releaseRelease

decision

And engineering for high velocity exposes multiple constraints

Rapidly increasing WIP

Lack of effective customer insight and high latency drives “kitchen sink” requirements

Waiting time for build and test environments drives “desk-side” builds

Poor confidence in test data fosters “release aversion” driving more WIP

Isolated build and integration processes

Deployed

App

Manual Testing

increases latency or

drives limited test

coverage

Manual and error prone app deployments

Error prone manual hand-offs and processes

High # defects

Locally optimized teams, measures and tools drives escalating WIP, lack of end-to-end visibility and trust

One way flow

Poor user

experience

“patch in production”

leads to snowflake systems

InfoSec & compliance

engaged late driving

vulnerabilities & re-work

Business

demands

Automate! Automate! Automate!

DevOps Continuous Integration and Testing

ProductionStagingQADev

Continuous Testing

Continuous Integration

Planning

Continuous Integration & Testing

Build Manager

Connected

Intelligence

Solution

Continuous Assessment (high fidelity feedback)

Unit Test

(Single

Component)

Functional

(Component and

Dependencies)

Static Security

Validation

Performance

TestsCode/Build

Small Scale

Performance

Validation

‘Black Box’

Security

Validation

Continuous Delivery

Deliver Amazing

12

Deliver Amazing

Our ADM journey

5 year journey

FROM TO

8 products

Major release every 18-24 months

Build to QA every 2-4 weeks

Automation runs on demand for

specific areas

15+ products

Quarterly on-prem release &

a SaaS release every 4-8 weeks

Daily/hourly and continuous

builds to QA

Continuous automation in

DevOps pipeline

Our Devs can no longer wear the T-Shirt….

HP Software Customer Forum FY14

DevOps – means no more testing right?

Wrong!

Thank you!

Thank you

18

19

20

Dev and Ops aren’t best of friends..

A good read…

23© 2016 Scaled Agile, Inc. All Rights Reserved.

Management’s challenge

It is not enough that management

commit themselves to quality and

productivity. … They must know

what it is they must do.

Such a responsibility cannot be

delegated.

—W. Edwards Deming

“… and if you can’t come, send no one.”

—Vignette from Out of the Crisis, Deming,1986

The HPE R&D IT Continuous delivery pipeline

Infrastructure as codeCompute, DB, Storage, Network

Ownership,

Autonomy,

Business Outcomes

Change in

• Executable code

• Configuration

• Infra / environment

• Data

• Monitoring

Continuous Delivery Pipeline

IaaS/Helion OpenStackPaaS/Helion Dev Plat

Containers/Docker

Physical

Virtual

Pipeline has access to systems,

NOT people

Change

ChatOps

ChatOps: persistent chat with bots

People & bots

Team inbox

Chat

Rooms

Augmented reality for Dev and Ops: brings down silos without a re-org.

Infrastructure as code

HP ALM HP UFTAgile Manager

HP Codar

Enterprise

How HPE IT delivers value today

Customers

QA +

Customers

Analysis +

DesignDevelt Testing MTP + Operations

Customers

Dev team

(waterfall)IT Operations

Wa

terf

all

Agile Analysis + Design

Development

Testing

Iterations 0 1 2 3 4

MTP?

Agile brings welcomed flexibility

but, alone, does not deliver value

fast enough to businessCustomers

Project Team

MTP + OperationsCustomers

IT Operations

MTP?MTP?MTP?

Customers Dev & test IT Operations

• Micro changes (in scope, in target)

• Fast analysis, development, testing, MTP

• Collaboration between business, dev and operations

• Several MTP per month, per week, per day

• As much automated as possible

• Augmented feedback loop from operations back to dev, test and business

(monitoring)

CD

/ D

evO

ps

© Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Amazon.com

How do they achieve it?

• Stream of small deployments, incremental change, easy rollbacks

• Virtualization and “infinite” vendor capacity

• Blue-Green deployments

• User segmentation for experimenting

• Continuous optimization in architecture & infrastructure

• 0.001% of deployments cause outage

“Famous” deployment every 11.6 seconds case