DevOps: The Key to Delivering High Quality Application Services Faster

DevOps: The Key to Delivering High

Quality Application Services Faster

Stephen Elliot Vice President Cloud and IT Infrastructure

DevOps Defined

DevOps is a methodology that unifies a team including business

leadership, architecture, development, testing, deployment, and

operations to be responsible for the creation and delivery of

IDC Prediction

DevOps will be adopted (in either practice or discipline) by 80% of Global 1000 organizations by 2019.

Trends Driving Quality Delivery

and DevOps

 Business Speed: drives the need for consistency, business dynamism

enabled by DevOps: service virtualization, release automation, ALM coordination, quality key for agility

 Organizational Change: optimize current resources; efficient approaches

for high quality, timely, software benefits from DevOps

 Flexible application paradigm (Quality) with services creation enables

technology & bus collaboration; agile emergence drives & benefits continuous delivery

 Improved security/audit/compliance issues (as driver) and

virtualization/cloud (as enabler) for DevOps adoption with analytics; ad hoc approaches unsustainable

 Customer experience and business impact challenges of rich Internet,

mobile, embedded (for IoT), with social systems of engagement collaboration/community, testing opportunities

We are entering the golden age of APIs. API design becomes a mainstream developer discipline. Organizations re-design APIs to new realities of mobile networks, IoT, and devices. API marketplaces proliferate.

■ Enterprises are exposing assets with powerful new APIs (e.g. Walgreens, Ford, US Dept. of Labor, BestBuy, FAA, Nike, etc..)

■ Companies w/ non-digital products desire

customer connection, alternative monetization, and differentiation

■ IoT “things” and product clouds

■ Salesforce1’s “API-first” re-architecture

■ Mobile architectures are bandwidth constrained

■ Proliferation of Mobile Back-end-as-a-Service

■ API marketplaces proliferate: Mashape, Mulesoft’s APIhub, APIS.io, …

The Age of API (Re)Design

Top Business Initiatives for 2014

In 2014, which of the following business initiatives will be significant in driving IT investments at your organization? Please select the top 3 initiatives.

53% 44% 41% 40% 34% 26% 26% 24% 23% 20% 9% 0% 10% 20% 30% 40% 50% 60%

Increase organization's productivity Improve organization's business process Introduce new and/or improved products & services Reduce organization's cost Increase organization's revenue Improve customer acquisition and retention Increase organization's agility Improve organization's security & mitigate risk Meet compliance requirements Expand into new geographic regions/countries Improve organization's ability to attract & retain…

N = 156

Why Projects Fail:

The Business Management Chasm

35%

Source: IDC 2015 CIO Sentiment Research

Over the past year, what percentage of your current projects have failed to meet your success criteria?

19% (n=84)

Why?

Poor requirements gathering/scope creep: 23% Lack of resources (staff and budget): 21%

Changed business priorities: 19%

Lack of business stakeholder ownership: 16%

Testing delays: 10%

User requirements change: 10%

Benchmark for Code Change Impact

24%

24%

9

DevOps Core Principles

_CORE

 CAMS: Culture, Automation, Measurement, Sharing

 Communication, collaboration, empathy, integration, and constructive conflict

 Organizational change; rethink feedback mechanisms, team creation, and reporting structure

 IT Risk reduction: assure staff that they understand its OK to fail, but not OK to not try.

 Share in success and people will commit. Fail fast, fail cheap.

 Communicate results to all levels, in their language (IT, business, financial, etc.)

 Choose the right metrics; business and technology

 Project management , and tool selection are critical

Mobility Best Practices

_ADVANCED

 If you build the service, you should run the service

 Include security, audit, and compliance teams early

 Create shared responsibilities/goals for a unified team of business stakeholders, developers, testing, and operations staff

DevOps: Two Organizational Options

Team Accelerators

 Increased automation across silos

 Empathy increases across domain expertise owners, driving more trust

 IT project success increases, and there is acceleration in the speed of success  Shadow or stealth IT decreases as business stakeholders are included early  IT's job satisfaction and career development improvements

Source: IDC DevOps Best Practice Metrics: Fortune 1000 Survey, December 2014

12

12 Pitfalls to Avoid

1.

Lack of management commitment

2.

Spending too much time on complicated process discussions

3.

Not assigning strong team leadership (SMEs, Product Mgmt., Ops,

Dev.)

4.

Allowing departmental chaos

5.

“Failure is not an option” mentality

6.

Poorly developed work instructions, project plans, and metrics

7.

Concentrating too much on performance and metrics

8.

Failing to maintain momentum

9.

Not reviewing the entire service lifecycle

10.

Ignoring key solutions

11.

Sidestepping political inhibitors

IDC’s DevOps MaturityScape Stages

Cultural inhibitors

IT culture that enables “silos” and limits collaboration, risk taking, and cross domain teamwork. Inability to measure

outcomes with fragmented processes and poorly integrated tools.

Business Outcome “Politically charged”

Highly political and insular organization with excessive costs.

Teamwork and measurement

Standardized processes and technologies drive increased teamwork, as business pressures force the need for measurable metrics. Business Outcome “Standardized change management and deployment” Standardization begins to lower costs and simplify development and operational processes.

Pervasive automation

DevOps practices enable broad automation and process standardization, and deliver more collaboration, trust, and teamwork with unified goals and responsibilities. . Business Outcome “Transparent value chain” Changes impact development, release, test, deployment, and operations staff, look to optimize resources and deliver measurable business outcomes.

Continuous feedback

A focus on business value creation, and a culture of quality where DevOps teams are accountable, and measured for speed and availability. This delivers agility, and the need to collect multiple inputs from internal and external (customer) sources.

Business Outcome “Center of Enablement”

Business and Technology leadership define business value creation for DevOps through a CoE and impactful metrics.

High performing service delivery

Enabled through DevOps values, processes, and procedures, customers dictate measurable adjustments. IT cultural transformation continues, via incremental successes with impactful business results via margin or revenue growth.

Business Outcome “Sustainable advantage” The business obtains sustainable, competitive advantage through differentiation and agility

IDC’s DevOps MaturityScape Dimensions

 People

Organization, staffing and talent management, skills development

 Culture

Values, collaboration, metrics, and customer alignment

 Technology

Road map, portfolio/tool planning, security, cloud

 Business

Strategy, budgeting, business alignment

 Process

Metrics that Matter: Communicate

Relentlessly in the Right Language

_Technology

Metrics

frequency

 Lead time for changes

 Change error rates

 Failure rates

 Lines of code

 Availability

 Recovery time

 Job satisfaction

Mobility Best Practices

Business Metrics

 Avoided costs  Customer feedback  Cash flow  Time to market  ROI & NPV  Customer satisfaction  Renewal rates  Cost per service/unit

Mobility Best Practices

Value Metrics

 Quality

 Opex

DevOps Benefits

Delivers reduced code errors, higher application availability levels, and reduced failure rates Automated application processes ensure applications work upon production deployment, with a faster time to market.

Accelerate speed as the Dev/QA teams streamline new version deployment frequencies Further extend the value of Agile, COBIT, ITIL, and related standards

Ensure rapid continuous feedback from internal, external, and customer sources.  Risk reduction through improved audit trails, transparent processes, and improved communications.

Automated processes enables staff reallocation, faster release cycles, improved security (reduced insider threats) and faster security releases.

Increase visibility and involvement with business stakeholders leads to business value creation.

Friday's Action Plan



Pick a small problem area and get started utilizing DevOps practices



Regardless of the approach you take, expect conflict and pushback;

create a set of tactics to solve or work around politics.



Consider automation tools; but they are only part of the answer



Re-evaluate what you expect from vendors and tools;

create a plan for the short and long-term.

Thank You

Stephen Elliot IDC

Vice President, Cloud and IT Infrastructure

[email protected]