Case Study: GM Financial Builds a Sustainable, Holistic, Continuous Delivery Practice

World®
’16
Case Study: GM Financial Builds a Sustainable,
Holistic Continuous Delivery Practice
Matt McComas - AVP Critical Apps - GM Financial
DO5T19S
DEVOPS

2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
© 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.
The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type
of warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA.
For Informational Purposes Only
Terms of this Presentation

Abstract
As the growing financial arm of General Motors, GM Financial realized that its software delivery
lifecycle was inadequate to meet the needs of its 400+ business lines. With manual release
processes, a sprawling server footprint and marathon deployment windows, the division was
encountering too many errors, compliance risks, rampant configuration creep and
overdependence on tribal knowledge. The company was at a crossroads—on an unsustainable
path, throwing more resources at bad processes. That’s when the company begin their
transformation, leveraging CA Continuous Delivery solutions to automate, standardize and align
processes and teams from development to production. Learn about GM Financial’s unique
journey to continuous delivery—from implementing CA Release Automation and standardizing
its continuous delivery ecosystem to accelerating and improving QA with CA Test Data
Management and CA Service Virtualization. Hear about lessons learned, results thus far and the
visionary roadmap to true continuous delivery.
Matt
McComas
GM Financial
AVP Critical Apps

Agenda
CHALLENGES OF RAPID COMPANY GROWTH GLOBALLY
OBVIOUS USE CASES FOR AUTOMATION
CONTINUING OBSTACLES AND CHALLENGES
ADOPTION OF CA TOOLS IN SDLC
CURRENT EFFORTS ACROSS SDLC
FUTURE ROAD MAP
1
2
3
4
5
6

Enterprise Servers Business Lines
Where We Were, Where We Are
Five Years of Explosive Platform Growth
2000+ servers across
enterprise
700 line of business
11 loan and lease
originations platforms
Global business units:
NA, Europe and Asia
300 servers across
enterprise
50 line of business
1 loan originations
platform
NA business unit only
2011 2016

Growing Operational and Compliance Risks
…Stemming from Rapid Expansion and Poor Deployment Processes
Proliferation of servers
meant increasing “creep”
Code and configuration creep
between Dev / QA / Prod
Separation of duties /
weaknesses in
deployment process
More platforms means
greater compliance risks
Very difficult to remediate
across SDLC with manual
processes

Considerable Challenges in the Old Delivery Model
Long deployments in
increasingly complex
platforms
§ Manual release process with poor
deployment tracking
§ Poor documentation, tribal
knowledge
§ Processes replete with human error
§ Growing need for heroics leading to
employee burn out
WAITING FOR
DEPLOYMENT

Increasingly Compromised Delivery
Too many systems, too much
complexity, too much risk
Throwing bodies
at bad processes

Changing IT Mindset
DevOps
Development QA
Operations
The software
company that does
auto finance!
§ The role of software delivery in driving
business value became increasingly clear
§ Need for model to support faster, more
frequent delivery and higher quality apps

Give me six hours to chop
down a tree and I will
spend the first four
sharpening the axe.
—Abraham Lincoln
“
“

Shifting Focus to Sharpen the Axe
Journey to Automation
STARTING AUTOMATION FORMAL ADOPTION
Script-based
Automation
Release
Automation
POC
Growth
Gridlock
Human
Error
DevOps?
CA Release
Automation
+ Tooling
Ecosystem
CROSSROADS
2014 2015 2016

Initial Results with CA Release Automation (POC)
Large scale,
multi web server
deployment
§ Manual deployment
would have taken
1 to 2 hours
§ Automated deployment
was completed in
3 minutes

CA Release Automation Current State and Efforts
At the One Year Mark…
Integration,
tokenizing,
standardization
Across all platforms
Full ServiceNow integration
§ End-to-end integration already
configured in some QA deployments
§ Working toward production
integration with SNOW change tickets
Socializing
capabilities

Metrics
Deployment
Failed
Deployment
Succeeded
Grand
Total
DEV 728 6757 7485
PRD 42 292 334
QA 198 2042 2240
TRN 38 71 109
STAGING 13 5 18
Grand Total 1019 9167 10186
2016 Deployments as of October
§ Averaging 1,000 deployments
per month in 2016
§ Average deployment takes
3 to 5 minutes

Meanwhile in QA…
Adoption of CA Test Data Manager
Platform growth
= accelerating
need for test data
Demand for
automated
sanitized data
Better cross-
platform data
synchronization
capabilities

Meanwhile in QA…
Adoption of CA Service Virtualization
Complex inter-platform and
vendor call outs demand
service virtualization
Acute need to “shift left” and
simulate service calls earlier
in project development

Roadmap to Desired State
Finish ITSM integration with build pipeline
§ End-to-end ServiceNow integrated production
deployments
§ Deploy any time with rolling deployments
End to end automated testing and validation
Full integration with Project Management
§ Project tracking and auditing through the
pipeline
§ Release management capabilities

And the Journey Does Not End
Integration of
infrastructure as code
Immutable server
deployments
Application
virtualization
Microservices and
containers
Hybrid cloud models
Aligning architecture and infrastructure
for seamless transition between on prem
and off prem

Roadblocks on the Way to Continuous Delivery…
ONE DOES
NOT SIMPLY
IMPLEMENT
CONTINUOUS
DELIVERY

Outmaneuvering Obstacles
Challenge culture,
team siloes, cozy
status quo
Encourage
communication,
collaboration and
sharing
Reinforce “the big
picture” about IT’s
business value
proposition
Executize
“DevOps”
message
Get past the
buzzword
Ensure alignment
on what DevOps
means to your
company across
teams and within
management
Show ‘em and
show ‘em again
Get those quick wins
to build/maintain
momentum
Reinforce that this is
a journey that never
ends: Automation
is a front loaded
effort that pays
exponentially over
time
Adjust attitude:
failure is an option
Push a change in
attitude toward
“failure”
Failures don’t
mean return to
status quo; instead
they represent a
new engineering
opportunity

Keep trying until
you get it—and
don’t be afraid to
fail
Realize software
drives the
business—
requiring faster,
more frequent
app delivery
Build an inclusive,
sustainable,
automation
model (with the
right tools) from
the start
Summary
A Few Words to Review

Must See Demos
Modernize
App Delivery
Integrated CD
Theater 5 - DOV501P
Deliver Test
Data Faster
Test Data Manager
Theater 5 - DOV511P
Deliver
Better Apps
Service Virtualization
Theater 5 - DOV507P
Orchestrate
Your Release
Release Automation
Theater 5 - DOV513P

Stay connected at communities.ca.com
Thank you.

DevOps – Continuous Delivery
For more information on DevOps – Continuous Delivery, please
visit: http://cainc.to/PiTFpu

Case Study: GM Financial Builds a Sustainable, Holistic, Continuous Delivery Practice

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (20)

Similaire à Case Study: GM Financial Builds a Sustainable, Holistic, Continuous Delivery Practice

Similaire à Case Study: GM Financial Builds a Sustainable, Holistic, Continuous Delivery Practice (20)

Plus de CA Technologies

Plus de CA Technologies (20)

Dernier

Dernier (20)

Case Study: GM Financial Builds a Sustainable, Holistic, Continuous Delivery Practice