DevOps: A primer

Today, one of the world’s biggest taxi companies…

Image : Mark Warner, used under Creative Commons license

has no taxis

Today, the fastest growing hotel chain…

Image : Jeremy Levine, used under Creative Commons license

has no hotels.

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

New competition can come from anywhere, at any time, and move

faster than ever before.

Adapting to the New Style of Business requires IT to be effective at managing risk…

EffectivenessHistorically, IT was taught

to be the tortoise: vigilant, methodical,

disciplined

Image : Andrea Westmoreland, used under Creative Commons license

Speed

As opposed to the hare, who relied on speed and

greater risk taking to achieve expected

outcomes.

while moving faster.

This combination of speed and effectiveness helps make businesses more agile.

“…agility tops business leaders’ list of priorities, as they prepare for the fast-paced, hypercompetitive future.”

+ Speed

Effectiveness

The traditional story required IT to make tradeoffs between speed and effectiveness, sacrificing agility

Speed

ResourcesPrograms limited by security andcompliance risks

ScopeBroad and ambitious projects crippled in favor of faster time

to delivery

TimeMajor programs

with lowtime-to-value

Effectiveness

Eliminating tradeoffs and increasing agility means embracing a philosophy of IT that merges speed with effectiveness.

IT will always need to think about risk, efficiency and costs, but will also need to move with

greater speed and velocity to deliver competitive advantage to the business.

Effectiveness

Speed

DevOps isthat philosophy.

DevOps=

11

DevOps is a philosophy of collaboration between development and operations.

12

It isn’t a job title, a toolset,or a marketplace.

13

It isn’t a job title, a toolset,or a marketplace.

It isgrounded in a combination of speed, efficiency and quality methodologies:

- Agile software development- Lean Manufacturing- Kaizen- Six Sigma

DevOps, Defined:

“The term ‘DevOps’ typically refers to the emergingprofessional movement that advocates a collaborative working relationship between development and IT operations, resulting in the fast flow of planned work (i.e., high deploy rates) while simultaneously increasing the reliability, stability, resilience, and security of the production environment.”

Gene KimAuthor of “The Phoenix Project”

DevOps is for any organization challenged by the increasing pace of application releases.

Early practitioners of agile methods accelerating delivery and deployment to match the rapid pace of software creation.

Web-scale practitioners responding to ever-evolving customer expectations and competitive threats.

Traditional IT organizations in well-established (and often regulated) industries, such as finance.

HighLow

Multiple daily releases

Daily to monthly releases

Structured releases

Release Frequency

Regardless of size, organizations that implement DevOps share a common goal:

Eliminating the time and resource constraints of application delivery, while ensuring the quality, stability, and continuous improvement of their releases and the experience for their end users.

The DevOps Cycle typically spans four functional areas

Continuous assessment

Continuous assessment

Continuous integration &

testing

Continuous delivery &

deployment

Continuous operations

BuildTest

Continuous Integration

Integrating code into a shared repository several times a day, verified by an automated build, allowing teams to detect problems early in the cycle.

The DevOps Cycle

Continuous Testing

Automating unit, functional, and non-functional tests against each build of the code base.

01

ReleaseDeploy

Continuous Delivery

Ensure software is always production-ready by standardizing infrastructure configuration and details with same discipline applied to managing source code.

Continuous Deployment

Automatically releasing and installing good code build to production and end users.

The DevOps Cycle

02

OperateMonitor

Continuous Operations

Managing software and hardware changes in a way that is non-disruptive to end users, such as patching and compliance.

The DevOps Cycle

03

Assess

Continuous Assessment

Involves continuously evaluating an application, based on three elements of feedback:

Feedback loops—monitoring application and user experience throughout the lifecycle

Planning prioritization—assess and prioritize new features, functions, and defect fixing

Portfolio investment—assess and prioritize investments based on business drivers.

The DevOps Cycle

04

can significantly improve time to value and allow IT to incrementally deliver new user and customer experiences; then scale to meet demand.

The DevOps Cycle

What are outcomes of successfulDevOps adoption?

Increased velocity andspeed of delivery

The overarching objective is responsiveness to business demand for new features and functionality.

A DevOps team will organize, align, and automate to streamline delivery.

Improved quality and stability

Reduced opportunity for manual errors in application delivery, with the gauntlet of automated testing serving to increase the quality of the final product.

And increased efficiency and capacity

Eliminated waste and rework, enabling the same size team to complete more work.

Realizing DevOps outcomes means building and supporting the cultural and process changes required for DevOps to thrive.

“…You start with a few sparks [passionate developers] and some dry tinder [well chosen projects]. Be careful not to add too much additional fuel to the fire too soon, or to leave it exposed to the elements of corporate governance before the flame catches and is strong enough to survive.”

Ralph LouraPrevious CIO HPE Enterprise Group, Global Sales Operations,and HPE Labs on starting a DevOps fire

Understanding and documenting the entire end-to-end system—the steps, players, goals, bottlenecks, errors, waste

A DevOps culture change begins with getting everyone on the same page,

Value-stream mapping Timeline Analysis Waste Analysis

Committing to continuous business stakeholder engagement,

IT must be plugged into business strategy and design capabilities to address issues or drive key initiatives.

The business should be more closely involved in IT planning, testing, and implementation.

IT

Business

Comparing projects/ experiments against abaseline to discover continuous improvement opportunities,

And knowing where to look for help.

With more than 75 years of experience in the technology industry, customers around the world trust Hewlett Packard Enterprise to help transform their infrastructure from one that simply keeps the lights on, to one that creates competitive advantage today and prepares for tomorrow.

Hewlett Packard Enterprise and DevOps

HPE infrastructure that supports scalability

Wherever you are in your DevOps journey, you can find an HPE solution that fits your needs.

HPE Transformation Services to develop your roadmap

HPE Software Solutions that enable the automation you need for DevOps

“DevOps adoption isn’t mandatory, but neitheris survival.”

Gene KimAuthor of “The Phoenix Project”

Learn more about how HPE’s IT has been going through its own DevOps cultural transformation

Visit HPE’s DevOps solutions portal

Planning to lead a transitionto a DevOps Culture?

© Copyright 2016 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice.