Pre-Con Ed: Achieving Continuous Test & Delivery for Mainframe with CA Application Lifecycle Conductor

World®
’16
Achieving Continuous Test & Delivery
for Mainframe with CA Application
Lifecycle Conductor
Rose Sakach
Sr. Principal Product Manager
MFX56E
MAINFRAME

2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
For Informational Purposes Only
Terms of this Presentation
© 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies. The presentation provided at CA
World 2016 is intended for information purposes only and does not form any type of warranty. Some of the specific slides with customer
references relate to customer's specific use and experience of CA products and solutions so actual results may vary.
Certain information in this presentation may outline CA’s general product direction. This presentation shall not serve to (i) affect the rights
and/or obligations of CA or its licensees under any existing or future license agreement or services agreement relating to any CA software
product; or (ii) amend any product documentation or specifications for any CA software product. This presentation is based on current
information and resource allocations as of November 1, 2016, and is subject to change or withdrawal by CA at any time without notice. The
development, release and timing of any features or functionality described in this presentation remain at CA’s sole discretion.
Notwithstanding anything in this presentation to the contrary, upon the general availability of any future CA product release referenced in
this presentation, CA may make such release available to new licensees in the form of a regularly scheduled major product release. Such
release may be made available to licensees of the product who are active subscribers to CA maintenance and support, on a when and if-
available basis. The information in this presentation is not deemed to be incorporated into any contract.

Abstract
A crucial part of Agile development is continuously delivering your
changes while still ensuring they are properly tested. Developers for
distributed, cloud and mobile platforms have enjoyed the freedom to
code and release to an automated pipeline as soon as they check in. Join
us to see how CA's best of breed DevOps solutions have been extended
to the mainframe and can now be used to achieve End to End DevOps
for mainframe developers along with CA's market leading mainframe
development tools.
Rose Sakach
CA Technologies
Sr. Principal Product
Manager

Agenda
WHY AGILE? WHY NOW?
TIME-TO-MARKET IS A FACTOR OF MAINFRAME
WATER-FALLING YOUR WAY TO AGILE
ACHIEVING “PEOPLE OVER PROCESS”
DELIVERING AT THE SPEED OF CONTINUOUS
1
2
3
4
5

Customers are in the midst of Digital Transformation…
Why Agile, Why Now?
DistributedCloudMobile Mainframe
üDevOps
üAgile
While today DevOps and Agile practices are happening on Mobile, Cloud and
Distributed platforms, we are seeing more customers beginning to adopt these
practices on the Mainframe

Why Agile, Why Now?
§ A means to and end, not an end
– Collaboration (People) over Process
– Develop Early, Often, not Intermittently
– Continuously Improve
– Leverage Hindsight
Practices (training plans) designed to help product teams:
“Build the right thing at the right time as efficiently as possible”
Tenets of Agile

Why Agile? Why Now?
§ More work, fewer SME’s
§ Business pressing for more releases, more often
§ Mainframe applications continue to transition
– Web front-ends
– Mobile front-ends
– JAVA
– Services
§ Delivery to PROD has not changed in __ years
Look around your mainframe organization…..

Time-to-market is a factor of Mainframe
Barriers to Business Agility
v Long Lead Times results in slower
and less frequent delivery of changes.
Impacts Time to Market

Time-to-recovery is a factor of Mainframe
Barriers to Business Agility
v Long Lead Times results in slower
and less frequent delivery of changes.
Impacts Time to Market
v Higher Mean Time to Resolution
(MTTR) results in more service
disruptions, longer recovery times
and poor SLAs. Impacts Reliability.

CA Interviews with customers in the
Financial Services & Auto Industry
“Many of our development activities are still on 3270 (green-screen). We are in the
midst of skills-transition. Our newer generation of mainframe developers are not
trained on green-screen or Cobol. While we can get them to code Cobol or look to
convert to Java, we want to provide our developers modern dev toolkits, similar to their
distributed counterparts”
In the midst of skills transition, lack of modern dev tools impact productivity and
ability to deploy changes faster

“The areas for MF development that need the most attention are the provision of high
quality test data, the build of the test environment (JCL, Binds, PSBs, online
configurations and so on) and the automation of tests. For a given program change
this is where most of the work resides and takes the longest for a MF developer and
dev/test team, to get to executable code with good quality ”
It takes too long to deliver changes on the mainframe (average time for nominal changes: 8-12 weeks),
caused by lack of test data, test environments, dependent applications access in testing phase and
automated test scripts

“We have 100+ applications, test scripts, large sets of test data, dependent
components on mainframe and distributed. We currently use an Excel sheet and try to
track and manage these relationships. At some point we constrain ourselves, since it’s
too hard to track and manage these manually. We need a solution that can catalog
and automate these for use as part of our testing activities.”
Managing and tracking the relationship between test scripts, test data and all
dependent applications is another critical barrier leading to longer test cycle times.

“The management of the test environment for future re-use to do additional quality testing
like performance, scalability, security and lack of release management/orchestration is
a key challenge for us. We do this very well on the distributed side, but not on the
mainframe. It affects our overall mobile to mainframe delivery when one side of the
house (distributed) has automated delivery stages and the other side (mainframe) is
doing things manually, thus slowing down our overall time to market”
Lack of release orchestration and ability to reuse of test environments to conduct several additional quality
measures like performance testing, enterprise hardening, security testing is a key bottleneck to faster MF
Application delivery

Water-falling your way to Agile
§ Typical Linear Progression Of Change
– Development
§ Skillsets, Culture, Code Characteristics, Agile Iterations
– Delivery [prod]
§ Cross-enterprise dependency coordination
– Test
§ Data Availability, Plans, Scripts, Automation
– Deployment [test area]
§ Configurations (Environment & Data), Availability, Cost, SME dependency

Development Deployment & OperationalTesting
Challenges to Delivering Innovations … Continuously
Developers Release
Team
Operations
TESTBUILD DEPLOY
Testers
OPERATE
Deploy to
Production
Cultural
Barriers,
Large Code
Monoliths
Constrained
Environments
Test
Environment
Provisioning
Challenges
Manual
Testing and
Scripting
Incomplete
Test Cases
and Data
Cross-Enterprise
Delivery,
Coordination
and Visibility
Lack of
Integrated
Toolsets
IDLE TIME DELAYS
Code/Integrate/
Build
Functional
& UA Testing
Performance
Testing
defect
RE-WORK
defect defect
DELAYS DELAYS
RE-WORK

Achieving “People over Process”
§ Imagine a transformed journey to PROD
– Work item management in Agile tools trigger SCM containers
– Developers are positioned to interact with modern IDE smart editors
– CheckINs become a push-button trigger to automatically
§ Build
§ Deploy
§ Test
– Quality gates, Test Data, Test configurations are predefined and
dynamically configured
– Defects are automatically created when tests fail
Bringing Continuous Test and Delivery to Mainframe Development

Achieving “People over Process”
§ Reconsider Historical Processes from an Agile Perspective
– Review, revise, modernized
§ How many tools require approvals?
§ How many tests need to run for an iterative change?
§ Which environments can be virtualized?
§ What data can be actionable?
§ How many people need to be notified?
Bringing Continuous Test and Delivery to Mainframe Development

Introducing Mainframe DevOps Solution
CA offers Solutions in 4 key areas to foster principles of Agile and DevOps
Continuous MonitoringContinuous TestingAgile Development Continuous Delivery
Develop and maintain
mainframe applications
with agile and modern
methodologies,
toolsets and coding
languages
TEST
Early & Often
DEVELOP
Swiftly
DEPLOY
Reliably
OPERATE
Efficiently
Continuous Feedback Loop
Reduce test cycle times
and costs of mainframe
testing for better time
to market and
mainframe economics
Remove the barriers to
business agility on the
mainframe, with
automation to reduce
time to market and
manage skills gaps
Unify monitoring and
performance
management across
mobile and mainframe
teams for better MTTR
and lower skills costs

Delivering at the speed of Continuous
§ Direct integration to agile tools
from developer tools
– CA Endevor® Software Change
Manager
– CA Agile Central
– CA Application Lifecycle Conductor
Develop Swiftly
Use Case: As an Enterprise
Application Dev team, we
need the ability to easily
manage, develop, and
maintain cross enterprise
applications using diverse
teams, different tools, on
different platforms to
maximize productivity,
quality and MTTR.

§ Automate and Orchestrate Delivery
– Release Automation for Z
Deploy Reliably
Use Case: As a MF DevOps
team, we need the ability to
automate and orchestrate a
continuous delivery process
subjecting the application to
key quality measures like
Integration testing, UAT,
System & performance
testing & pre production
validations, so that we can
deploy changes quickly with
high quality.
Zero Touch
Deployment
for z/OS
Continuous
Delivery
Pipeline for
z/OS

§ Dynamically Configure Environment
§ Automatically provision data
§ Catalog and Manage Assets
– CA Service Virtualization
– CA Test Data Manager for the Mainframe
Test Early and Often

§ Continuously feedback to key stakeholders
Operate Efficiently
As an MF DevOps
(Application
Dev/test/Ops/Sec) team, we
need a continuous feedback
loop to identify, capture and
notify key stakeholders
about critical Ops, Sec, Test
& Delivery problems so that
the teams can inspect and
take corrective actions and
respond rapidly to critical
business issues.

CA DevOps for Mainframe Solution Demo

Recommended Sessions
SESSION # TITLE DATE/TIME
MFX57E
Webhooks & Continuous Feedback with CA Application
Lifecycle Conductor
11/15/2016 at 3:00 pm
MFT148S
Roadmap Session: Achieve DevOps on the Mainframe for
Faster Time to Market
11/16/2016 at 4:30 pm
MFX111S
Advanced Techniques for Initiating the DevOps Journey
[HSBC]
11/17/2016 at 12:45 pm

Must See Demos
Continuous Development
and Testing
Mainframe Theater
Continuous Delivery
Mainframe Theater

Questions?

Thank you.
Stay connected at communities.ca.com

@CAWORLD #CAWORLD © 2016 CA. All RIGHTS RESERVED.28 @CAWORLD #CAWORLD
Mainframe and Workload Automation
For more information please visit ca.com/alc
Rose Sakach
Sr. Principal Product Manager
rose.sakach@ca.com

Pre-Con Ed: Achieving Continuous Test & Delivery for Mainframe with CA Application Lifecycle Conductor

More Related Content

What's hot (20)

Viewers also liked (7)

Similar to Pre-Con Ed: Achieving Continuous Test & Delivery for Mainframe with CA Application Lifecycle Conductor (20)

More from CA Technologies (20)

Recently uploaded (20)

Pre-Con Ed: Achieving Continuous Test & Delivery for Mainframe with CA Application Lifecycle Conductor