Ray Gorman

Technical Director

21 March 2017

The Journey to DevOps#MFSummit2017

DevOps (a clipped compound of "software

DEVelopment" and "information technology

OPerationS") is a term used to refer to a set of

practices that emphasise the collaboration and

communication of both software developers and

information technology (IT) professionals while

automating 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. (Wikipedia)

DevOps

Which of these most represents the organisation you work for:

a) We have well established DevOps processes that are widely used

b) We have pockets of DevOps processes but still need to broaden it

across the organisation

c) We are in the planning and early stages of adopting DevOps

practices

d) We will never have DevOps in this organisation

Quick Survey

Application Delivery Challenges

Time to market Proliferation of devices User experience

Digital Transformation - Massive Budget Shift

Back office

Systems of record

Digital front office

Systems of engagement

80% 45%

2011 2016

20% 55%

2011 2016

$

Source: Forrester

Our Challenge – Keep up the PaceA

gili

ty a

nd

Sca

le

Time

IT delivery capabilities Business demands

1

2

Legacy infrastructure

Legacy architecture

Legacy processes

Poor user experience

Modern Infrastructure

Modern Architecture

Modern Processes

Great User Experience

The Good

Old Days

Today

Internet of

Things

Digital industrial economy

Delivery Gap

More frequent

release cycles

Involve customers

in the

development

process

Demonstrate

progress through

working demos,

not slides

Faster time to

market

Boost quality and

efficiency

+

Build the right product

Transparency

+

Instilling

confidence

Why Consider DevOps?Agile practice Business goal

Need to drive competitive advantage and respond to market needs with minimal risk and maintain compliance

Agile practices have increased the

speed of engineering delivery to

match business cadence

Compliance and risk mitigation

while maintaining system stability

and availability matter most

BUSINESS

DEVELOPMENT OPERATIONS

Conflicting Priorities with Dev and Ops

Move Fast Without Breaking Things

Deployment Pipeline – the Ideal

Deployment Pipeline

Dev OpsBizidea Release and Monitor

Plan Test Deploy

DevOps “Purist” Enterprise DevOps

Single application Hundreds of applications

Co-located teams Geographical dispersed teams

Single stack “loosely coupled”

infrastructure

Many environments including

mainframe both “loosely” and “tightly”

coupled.

Minimal security and compliance risks Highly regulated and high security risks

Solely agile development Multiple development methodologies

A single deployment pipeline across a

single application stackMultiple deployment pipelines across a

vast heterogeneous system

Simple application architecture Complex multi-platform architecture

Enterprise DevOps is Different

But in Reality

Deployment

Pipeline

Dev OpsBizidea Release and Monitor

Plan Test Deploy

Deployment

Pipeline

The Enterprise has many Deployment Pipelines

Mobile Apps

• Loosely coupled infrastructure, Cloud and IoT

• High growth, lots of change, needs more resources

New “Core” Apps

•Loosely coupled infrastructure but uses mainframe,

•High growth, uses mobile apps, needs more resources

Website

•Loosely coupled infrastructure,

•High number of changes

Legacy “Core” Apps

• Tightly coupled infrastructure, migrating to agile,

• Existing large revenue stream, moderate change, high cost

Back Office Apps

•Tightly coupled infrastructure, waterfall, mainly mainframe,

• Keep the lights on, no growth, low number of changes, high cost

Removing Delivery Barriers

Build TestPlan Release

Traditional development practices prevent people, processes and technology

working efficiently together

Continuous Workflow

Build TestPlan Release

The DevOps movement is intended to unite the objectives of all areas

Dev Ops

The Journey

Build TestPlan Release

Agile Practices

Dev Ops

• Demand and requirement management

• Analysis

• Agile planning

Stories, epics, tasks, sprints / iterations

• Development task in sprints / iterations

Edit, compile, debug, continuous inspection

• Development project provisioning

Packages, streams, projects, build configuration, ...

• Release Management

Agile Practices: People

Plan

Build

Providing:

• Requirements Management tools

• Agile tools

• Analysis tools

• Development tools

• Mainframe, distributed

• Configuration management tools

• Mainframe, distributed

• Integration of current third party tools

Agile Practices: Micro Focus

Plan

Build

The Journey

Build TestPlan Release

Agile Practices

Continuous Integration

Dev Ops

• Automation depends on

• Continuous Integration

• Configuration Management

• Automated provisioning environments across

• the delivery pipeline

• Automated application build and deployment

• Automated / semi-automated testing

• Functional

• Acceptance Testing

• Continuous feedback

Continuous Integration: Automation

Build

Providing:

• Test execution environments

• Build and Test Automation tools

• + Integration with third party tools

• Continuous Inspection tools

• Test coverage tools

• Deployment automation tools

• Orchestration of deployment process

Continuous Integration: Micro Focus

Build

The Journey

Build TestPlan Release

Agile Practices

Continuous Integration

Continuous Delivery

Dev Ops

• Automation depends on

• Continuous Integration, configuration Management

• Automated provisioning environments across the delivery

pipeline

• Automated application build/configure and deployment

• Automated / semi-automated testing

• Functional, acceptance testing

• Automated testing

• Non-functional: validate application performance, infrastructure and

devices of choice

Continuous Delivery: Automation

Test

• Providing deployment automation tools

• Orchestration of deployment process

• Providing build and test automation tools

• Integration with third party tools

Continuous Delivery: Micro Focus

Test

The Journey

Build TestPlan Release

Agile Practices

Continuous Integration

Continuous Delivery

Application Release Automation

Dev Ops

• Final release configuration / release train

• Manual or automated depending on application

architecture

• Package dependencies

• Approvals

• Release scheduling

• Deployment tasks / run books

• Automated deployment

• Across all platforms and environments

Application Release Automation

Release

Providing:

• Deployment Orchestration

+ integration with third party tools

• Collaboration

• Continuous release management across the whole ALM

process, from planning to release

• IT Service Management

+ integration with third party tools

Application release automation: Micro Focus

Release

Micro Focus DevOps

Dev Ops

Plan

Bu

ild

De

plo

y

Audit

Feedback

Management, orchestration and collaboration

Planning

Capabilities

Developer

productivity

Continuous

Integration

Configuration

Management

Release

Management

Deployment

Management

IT Service

Management

Data

ManagementPerformance

Management

Test

Management

DevOps Engagement ModelInitial

meetings

Value

workshop

Proof of Value

(PoV)

Executive

endorsement

Sign off and

project initiation

Customer

actions

Inform about business

objectives, urgency, and

DevOps initiatives

Present SDLC process,

people, tools and challenges

Define use case and

success criteria

Arrange DevOps

roadmap presentation to

stakeholders

Procurement process

management and contract

signature

Complete applications

Landscape Questionnaire

(L0Q)

Provide Infrastructure (as

required)

Resources for project

implementation allocated

Micro Focus

deliverables

DevOps implementation

examples by Micro Focus

customers

Draft DevOps roadmap with

priorities and expected

benefits

PoV SOW and RASCIImplementation plan

and proposal

Micro Focus

products

Customer need -

understanding summary

Mutually Agreed

Action Plan (MAAP)

Resources allocated

(as required)

Prerequisite

for

next steps

Resources allocated by

both parties

Budget and resources

available for joint

Proof of Value

DevOps roadmap with

short term benefits

confirmed

Investment approved by

executive

Implementation project

kick off scheduled

DevOps Value Workshop: Heat Map

DevOps Value Workshop: Roadmap

In Summary - Our Expertise is in:

• Aligning business objectives with the software development process

• Providing visibility and control across the software development process

• Continuous Delivery from mainframe to mobile.

• Unlocking core business applications to scale DevOps practices on what already works,

in essence bridging the old with the new.

• Helping maintain high levels of customer satisfaction and uptime while ensuring on all

major platforms and devices

Starting from here…

Aligning business objectives

visibility and control Continuous Delivery

old with the new

ensuring an exceptional user experience

on all major platforms and devices

www.microfocus.com