9. Case study and Q&A with a change agent and
DevOps org leader: Val Scott
9
Please note:
This portion of the video/audio file and the contents herein are owned by HM Health Solution Inc. or its affiliates
(HMHS). This presentation was developed by HMHS for the private use of persons who are authorized to view
its contents. Any copying or distribution of these materials is prohibited without HMHS’s express written consent.
HMHS is providing this video/audio presentation as an informational service only. This presentation is provided in
an “as is” format without warranties of any kind, expressed or implied, including but not limited to warranties of
title, non-infringement or implied warranties of merchantability or fitness for a particular purpose.
HM Health Solutions Inc. Proprietary and Confidential Information. All Rights Reserved.
10. 10 HM Health Solutions Inc. Proprietary and Confidential Information. All Rights Reserved.
Case Study: HM Health Solutions Approach to Enterprise DevOps ROI
Shifting left in application development offers a faster
return on investment by allowing developers to catch
errors earlier in the software development lifecycle.
•Benefits:
Improves Software Quality
Cuts Time Between Releases
• Industry statistics have suggested that:
58% of defects originated in earlier lifecycle
activities.
70% of all IT projects are not successful.
30-40% of all IT work is re-work.
Shift Left Approach provides Quality Improvements and Lower Development Costs:
• Reviews and checks take place as early as possible in the project delivery.
• This ensures the trapping of defects on the left hand side of a typical project lifecycle.
Shift Left philosophy is defect prevention rather than defect detection in the delivery lifecycle of a project
or program of work and contributes to lower costs of software delivery.
Strategy of Shift Left
11. 11 HM Health Solutions Inc. Proprietary and Confidential Information. All Rights Reserved.
Case Study: HM Health Solutions Approach to Enterprise DevOps ROI
Test-driven
developmen
t
▪ IBM UrbanCode Ubuild
and UDeploy – Automated
Unit and Integration Testing
is performed with
immediate feedback on
failure
Show
failed tests
Specify required
improvements in code
▪ Test cases developed along requirements
▪ Unit/module testing concurrent with
desktop development
▪ Teams review code to
ensure integrity
▪ IBM UrbanCode UBuild
code is integrated into
main version continuously,
with build automation
processes in place
▪ Automated regression tests in pre-
production, along with final
QA/UAT
▪ IBM UrbanCode UDeploy allows
for Push-button ability to
deploy into production
Show code conflicts
Show build errors
Automated Build and
Test Activities and
Quality Standard
Checks
Put code in
review queue
Automated Build with
Code Commit and
Dependency
management
Show errors from pre-production
Automated
Deploy Packages
to pre-production
1
Automated
testing
2
Streamlined
code review
3
Automated
deployment
5
Continuous
integration
4
Leveraging DevOps and IBM UrbanCode Suite of Tools
12. 12 HM Health Solutions Inc. Proprietary and Confidential Information. All Rights Reserved.
Case Study: HM Health Solutions Approach to Enterprise DevOps ROI
26%
47%
Defect Count
Withdrawn
Testing
Production
27%
100%
2014 YTD Defect %
Calculating the Average Hours to Repair Defects in Test and Production
Baseline number of hours to repair defect:
• On average it takes ~ 30 hours to resolve a
single test defect
• On average it takes ~ 120 hours to resolve a
single production defect
Establish a baseline for measurement:
1. Determine how to measure the current
environment and defect costs.
2. Understand contributing costs to the
amount of time spent in repairing defects.
3. Establish the average hour spent in
repairing defects in the environments.
Your mileage may vary !
13. 13 HM Health Solutions Inc. Proprietary and Confidential Information. All Rights Reserved.
Case Study: HM Health Solutions Approach to Enterprise DevOps ROI
HM Health Solutions Relative Savings and Efficiency Gains
30
120
-75%
Relative Hours to Repair
Programmer Defects
Per Environment
Production
Test
55
10
-82%
Automation Efficiency
Gains in Minutes
New Process
Old Process
3
1
-67%
Release Process
Resource Demands
Old Process
New Process
Your mileage may vary !
14. 14 HM Health Solutions Inc. Proprietary and Confidential Information. All Rights Reserved.
Case Study: HM Health Solutions Approach to Enterprise DevOps ROI
2014 2015
Q3 Q4 Q1 Q2 Q3 Q4Activity
1/13/2015
Wave 5: Workflow Vendor
Wave 4: Message Broker
Wave 3: Mainframe
Wave 2: Mainframe Proof of Concept
Wave 1: WebSphere
DevOps Pilots
Wave 6: Client Desktop
6 Java Apps
238 WebSphere Apps
107 Mainframe Apps
43 Message Broker Apps
26 Workflow Vendor
26 Client Desktop
Mainframe POC & Pilots
HM Health Solutions Roadmap 2014-2015
15. 15 HM Health Solutions Inc. Proprietary and Confidential Information. All Rights Reserved.
Case Study: HM Health Solutions Approach to Enterprise DevOps ROI
• Assess your current environment to find the largest constraint
• Determine the scope of your maturity level goal
• Develop Business Case and seek management approval
• Proof of Concepts
• Identify savings opportunities and determine measurement
• Prioritize the target environment
• Pilots
• Roadmap
• Onboard, track, and compare before and after picture
• Defect and Testing practices
• Development and Release process
• Resource allocations
• Ring fence
• Track savings and real efficiency gains during rollout
• Track ROI on monthly basis
Tips on Getting Started with Enterprise DevOps and Rollout
16. 16 HM Health Solutions Inc. Proprietary and Confidential Information. All Rights Reserved.
Case Study: HM Health Solutions Approach to Enterprise DevOps ROI
• Develop Business Case and seek management approval
• Proof of Concepts
• Lessons Learned:
• Test cases should include reports on metrics
• Inventory and prioritize the target environment
• Roadmap
• Lessons Learned:
• Develop a structured process for tracking and measuring, along with a glossary of automation
terms.
• Onboard, track and compare before and after picture
• Defect and Testing Practices
• Lessons Learned:
• Use the Pareto principle (80-20) for the baseline defect measurement. (What is a programmer
error?)
• Ring fence
• Track savings and efficiency gains during rollout
• Lessons Learned:
• Methodically step through the savings with the onboarding team on efficiency gains. Quickly
report the gains when found.
• Track ROI on monthly basis
• Lessons Learned:
• Don’t be afraid to roll up your sleeves and dig into the data. There is a gold mine out there.
Lessons Learned In Calculating and Managing the DevOps ROI
17. 17 HM Health Solutions Inc. Proprietary and Confidential Information. All Rights Reserved.
Case Study: HM Health Solutions Approach to Enterprise DevOps ROI
Leveraging (3) Key Industry Components for Enterprise DevOps ROI
• DevOps
Continuous feedback integration and delivery.
Quality software development practices that manages the software packages during the
development process.
Increases our ability to shorten our delivery times.
• Shift Left Approach
Shifting software testing sooner in the software delivery lifecycle, allowing developers to
catch defects sooner.
Fastest way to realize one’s return on investment based on relative cost or repair in
production.
• Automation
Leveraging the automation gains from IBM Urbancode Suite.
Achieve a Managed Environment maturity level or higher with:
Scheduled, standard and automated processes
Allows for an increase in the delivery cycle.