TechValidate Research on CA Release Automation

Introduction

This case study of a Global 500 banking company is based on a June 2016 survey of CA Technologies Release Automation customers by TechValidate, a 3rd-party research service. The profiled company asked to have their name blinded to protect their confidentiality.

Challenges

• Reasons for automating application releases:
  • Increase the volume of release deployments
  • Reduce release failures and improve deployment quality
  • Manage the complexity of applications, tools and environments
  • Get better control over the release process and pipeline
  • Track releases for compliance and audit purposes
• Chose CA Release Automation over:
  • VMware

Use Case

• Using CA Release Automation version 5.5
• Currently using CA Release Automation to:
  • To orchestrate the release pipeline – deploying an application from stage to stage
  • To extend Agile development methodologies into the release pipeline
  • To deploy in a compliance-driven environment
  • To improve team collaboration and accountability for application deployments
  • To provide Continuous Delivery as an IT service

Results

• Most valuable features of CA Release Automation:
  • Release execution flexibility to pause, restart, or roll back a deployment
  • Visual UI for building workflows
  • A consolidated reporting dashboard
  • Artifact management, modeling, and tracking
  • Re-usability of workflows and components
  • Support for complex processes, looping, and cross-server processing
  • Ability to deploy a large number of applications across multiple environments
• Rating of CA Release Automation’s features when compared to the competition:
  • Depth/breadth of integrations: Highly superior
  • Deployment workflow design: Significantly superior
  • Release execution/reliability: Significantly superior
  • Visibility to release activity: Significantly superior
  • Scalability: Significantly superior
• Value achieved by implementing CA Release Automation:
  • The ability to reliably release applications on demand
  • Getting customer feedback faster
  • Increased volume of releases
  • Improved visibility, consistency, and reliability of release processes across the pipeline
  • The ability to easily integrate with existing environment and tools
  • Reduced or eliminated downtime
• Improved with CA Release Automation:
  • Time to market: By more than 50-75%
  • Ability to handle more releases: By more than 75%
  • Speed of release cycles: By more than 75%
  • Release quality: By 50-75%
  • Tracking for compliance and audit: 50-75%

Introduction

This case study of HMS (Health Management Systems) is based on a July 2016 survey of CA Technologies Release Automation customers by TechValidate, a 3rd-party research service.

Challenges

• Reasons for automating application releases:
  • Increase the volume of release deployments
  • Reduce release failures and improve deployment quality
• Chose CA Release Automation over:
  • Microsoft Release Management

Use Case

• Using CA Release Automation version 5.5
• Currently using CA Release Automation to:
  • To orchestrate the release pipeline – deploying an application from stage to stage
  • To extend Agile development methodologies into the release pipeline
  • To provide Continuous Delivery as an IT service

Results

• Most valuable features of CA Release Automation:
  • Visual UI for building workflows
  • Artifact management, modeling, and tracking
  • Re-usability of workflows and components
• Rating of CA Release Automation’s features when compared to the competition:
  • Depth/breadth of integrations: Highly superior
  • Deployment workflow design: Highly superior
  • Release execution/reliability: Significantly superior
  • Visibility to release activity: Highly superior
  • Scalability: Highly superior
• Value achieved by implementing CA Release Automation:
  • Getting customer feedback faster
  • Significantly sped up release cycles
  • Reduced or eliminated downtime
• Improvements to Application Delivery with CA Release Automation:
  • Time to market: More than 75%
  • Ability to handle more releases: More than 75%
  • Speed of release cycles: More than 75%
  • Release quality: More than 75%
  • Tracking for compliance and audit: More than 75%

Introduction

This case study of a Global 500 Banking Company is based on a June 2016 survey of CA Technologies Release Automation customers by TechValidate, a 3rd-party research service.

Challenges

• Reasons for automating application releases:
  • Increase the volume of release deployments
  • Manage the complexity of applications, tools, and environments
  • Get better control over the release process and pipeline
• Chose CA Release Automation over:
  • IBM UrbanCode

Use Case

• Using CA Release Automation version 6.0
• Currently using CA Release Automation to:
  • Orchestrate the release pipeline – deploying an application from stage to stage
  • Accurately deploy service updates across multiple applications and environments
  • Improve team collaboration and accountability for application deployments
  • Provide Continuous Delivery as an IT service

Results

• Most valuable features of CA Release Automation:
  • Depth and breadth of integrations with 3rd party and in-house technologies
  • Visual UI for building workflows
  • Artifact management, modeling, and tracking
  • Re-usability of workflows and components
  • Support for complex processes, looping, and cross-server processing
  • Ability to deploy a large number of applications across multiple environments
• Rating of CA Release Automation’s features when compared to the competition:
  • Depth/breadth of integrations: Highly superior
  • Deployment workflow design: Highly superior
  • Release execution/reliability: Highly superior
  • Visibility to release activity: Highly superior
  • Scalability: Highly superior
• Value achieved by implementing CA Release Automation:
  • Significantly sped up release cycles
  • Increased volume of releases
  • Improved visibility, consistency, and reliability of release processes across the pipeline
  • The ability to efficiently manage deployment environments and dependencies
  • Reduced or eliminated downtime
• Improvement to Application Delivery with CA Release Automation:
  • Time to market: By 50-75%
  • Ability to handle more releases: By 50-75%
  • Speed of release cycles: By 50-75%
  • Release quality: By 50-75%
  • Tracking for compliance and audit: By 50-75%

Introduction

This case study of a medium enterprise financial services company is based on a June 2016 survey of CA Technologies Release Automation customers by TechValidate, a 3rd-party research service. The profiled company asked to have their name blinded to protect their confidentiality.

Challenges

• Reasons for automating application releases:
  • Get to market quicker
  • Increase the volume of release deployments
  • Reduce release failures and improve deployment quality
  • Manage the complexity of applications, tools and environments
  • Get better control over the release process and pipeline
  • Capture and re-use deployment best practices
  • Track releases for compliance and audit purposes
• Chose CA Release Automation over:
  • Serena
  • Xebialabs

Use Case

• Usung CA Release Automation version 6.1.
• Currently using CA Release Automation to:
  • To orchestrate the release pipeline – deploying an application from stage to stage
  • To extend Agile development methodologies into the release pipeline
  • To accurately deploy service updates across multiple applications and environments
  • To deploy in a compliance-driven environment
  • To improve team collaboration and accountability for application deployments
  • To provide Continuous Delivery as an IT service

Results

• Most valuable features of CA Release Automation:
  • Release execution flexibility to pause, restart, or roll back a deployment
  • A consolidated reporting dashboard
  • Re-usability of workflows and components
  • Ability to deploy a large number of applications across multiple environments
• Rating of CA Release Automation’s features when compared to the competition:
  • Depth/breadth of integrations: Highly superior
  • Deployment workflow design: Superior
  • Release execution/reliability: Superior
  • Visibility to release activity: Highly superior
  • Scalability: Highly superior
• Value achieved by implementing CA Release Automation:
  • The ability to reliably release applications on demand
  • Significantly sped up release cycles
  • Increased volume of releases
  • Improved visibility, consistency, and reliability of release processes across the pipeline
  • The ability to efficiently manage deployment environments and dependencies
  • The ability to easily integrate with existing environment and tools
  • Reduced or eliminated downtime
  • Improved collaboration and accountability between the Development and Operations teams
• Improvements to company’s capabilities with CA Release Automation:
  • Time to market: By 50-75%
  • Ability to handle more releases: By 50-75%
  • Speed of release cycles: By 50-75%
  • Release quality: By 50-75%
  • Tracking for compliance and audit: By 50-75%

Introduction

This case study of a S&P 500 financial services company is based on a June 2016 survey of CA Technologies Release Automation customers by TechValidate, a 3rd-party research service. The profiled company asked to have their name blinded to protect their confidentiality.

Challenges

• Reasons for automating application releases:
  • Get to market quicker
  • Increase the volume of release deployments
  • Reduce release failures and improve deployment quality
  • Manage the complexity of applications, tools and environments
  • Get better control over the release process and pipeline
  • Capture and re-use deployment best practices
    *Chose CA Release Automation over:
  • Automic
  • Electric Cloud
  • Hewlett Packard Enterprise (HPE)
  • IBM UrbanCode
  • Xebialabs

Use Case

• Using CA Release Automation version 5.5.
• Currently using CA Release Automation to:
  • To orchestrate the release pipeline – deploying an application from stage to stage
  • To extend Agile development methodologies into the release pipeline
  • To accurately deploy service updates across multiple applications and environments
  • To deploy in a compliance-driven environment
  • To improve team collaboration and accountability for application deployments
  • To provide Continuous Delivery as an IT service

Results

• Most valuable features of CA Release Automation:
  • Depth and breadth of integrations with 3rd party and in-house technologies
  • Release execution flexibility to pause, restart, or roll back a deployment
  • Visual UI for building workflows
  • Artifact management, modeling, and tracking
  • Re-usability of workflows and components
  • Ability to deploy a large number of applications across multiple environments
• Rating of CA Release Automation’s features when compared to the competition:
  • Depth/breadth of integrations: Superior
  • Deployment workflow design: Highly superior
  • Release execution/reliability: Highly superior
  • Visibility to release activity: Superior
  • Scalability: Superior
• Value achieved by implementing CA Release Automation:
  • The ability to reliably release applications on demand
  • Getting customer feedback faster
  • Significantly sped up release cycles
  • Increased volume of releases
  • Improved visibility, consistency, and reliability of release processes across the pipeline
  • The ability to efficiently manage deployment environments and dependencies
  • The ability to easily integrate with existing environment and tools
  • Reduced or eliminated downtime
  • Improved collaboration and accountability between the Development and Operations teams
• Improvements to Application Delivery with CA Release Automation:
  • Time to market: By 35-50%
  • Ability to handle more releases: By 50-75%
  • Speed of release cycles: By 35-50%
  • Release quality: By 35-50%
  • Tracking for compliance and audit: By 15-35%

Introduction

This case study of a medium enterprise insurance company is based on a September 2015 survey of CA Technologies Release Automation customers by TechValidate, a 3rd-party research service. The profiled company asked to have their name blinded to protect their confidentiality.

Challenges

• Reasons for automating application releases:
  • Getting to market quicker
  • Increasing the volume of release deployments
  • Reducing release failures and improving deployment quality

Use Case

• Using version 5.5 of CA Release Automation.
• Cites that CA Release Automation has been implemented for 0 – 12 months.
• Currently using CA Release Automation to:
  • To extend Agile development methodologies into the release pipeline
  • To accurately deploy service updates across multiple applications and environments
  • To deploy in a compliance-driven environment
• Tools and platforms integrated with CA Release Automation:
  • Jenkins
  • IBM Rational ClearCase
  • Nexus

Results

• Most valuable features of CA Release Automation:
  • Visual UI for building workflows
  • Re-usability of workflows and components
• Value achieved by implementing CA Release Automation:
  • The ability to reliably release applications on demand
  • Improved collaboration and accountability between the Development and Operations teams
• Company’s progress on journey to Continuous Delivery:
  • BEFORE using CA Release Automation: Scripting
  • AFTER using CA Release Automation: Tool Automation

Introduction

This case study of a Fortune 500 financial services company is based on a September 2015 survey of CA Technologies Release Automation customers by TechValidate, a 3rd-party research service. The profiled company asked to have their name blinded to protect their confidentiality.

Challenges

• Reasons for automating application releases:
  • Getting to market quicker
  • Increasing the volume of release deployments
  • Reducing release failures and improving deployment quality
  • Getting better control over the release process and pipeline
  • Capturing and re-using deployment best practices
  • Tracking releases for compliance and audit purposes

Use Case

• Using version 5.0 of CA Release Automation.
• Has been implemented for 2 – 4 years.
• Currently using CA Release Automation to:
  • To extend Agile development methodologies into the release pipeline
  • To accurately deploy service updates across multiple applications and environments
  • To deploy in a compliance-driven environment
  • To provide Continuous Delivery as an IT service
• Tools and platforms integrated with CA Release Automation:
  • Jenkins
  • SERENA Release Control
  • IBM Rational Build Forge
  • Home-grown deployment orchestrator

Results

• Most valuable features of CA Release Automation:
  • Depth and breadth of integrations with 3rd party and in-house technologies
  • Visual UI for building workflows
  • Re-usability of workflows and components
  • Support for complex processes, looping, and cross-server processing
  • Ability to deploy a large number of applications across multiple environments
• Value achieved by implementing CA Release Automation:
  • The ability to reliably release applications on demand
  • Getting customer feedback faster
  • Significantly sped up release cycles
  • Increased volume of releases
  • Improved visibility, consistency, and reliability of release processes across the pipeline
  • The ability to easily integrate with existing environment and tools
  • Reduced or eliminated downtime
  • Improved collaboration and accountability between the Development and Operations teams
• Company’s progress on journey to Continuous Delivery:
  • BEFORE using CA Release Automation: Scripting
  • AFTER using CA Release Automation: Continuous Delivery

Introduction

This case study of a large enterprise financial services company is based on a September 2015 survey of CA Technologies Release Automation customers by TechValidate, a 3rd-party research service. The profiled company asked to have their name blinded to protect their confidentiality.

Challenges

• Reasons for automating application releases:
  • Increasing the volume of release deployments
  • Reducing release failures and improving deployment quality
  • Getting better control over the release process and pipeline
  • Tracking releases for compliance and audit purposes

Use Case

• Using version 5.0 of CA Release Automation
• Has been implemented for 2 – 4 years
• Currently using CA Release Automation to:
  • To orchestrate the release pipeline – deploying an application from stage to stage
  • To provide Continuous Delivery as an IT service
• Tools and platforms integrated with CA Release Automation:
  • Jenkins
  • JFrog Artifactory

Results

• Most valuable features of CA Release Automation:
  • Depth and breadth of integrations with 3rd party and in-house technologies
  • Release execution flexibility to pause, restart, or roll back a deployment
  • A consolidated reporting dashboard
  • Artifact management, modeling, and tracking
• Value achieved by implementing CA Release Automation:
  • The ability to reliably release applications on demand
  • Significantly sped up release cycles
  • Increased volume of releases
  • Reduced or eliminated downtime
• Company’s progress on journey to Continuous Delivery stage:
  • BEFORE using CA Release Automation: Scripting
  • AFTER using CA Release Automation: Continuous Delivery