Executive Dinner Series: Managing Software Risk within the Insurance Industry


It is becoming more and more obvious that the software risks and complexity that face today's legacy systems is a growing problem for many IT organizations. Are these legacy applications “Ever going to be replaced or retired?  Are they “Too Big to Fail”? Added concern around many of these applications involves their size and architectural interconnectivity whereby their failure would prove disastrous to the entire businessThere are few industries where this is more evident than the insurance industry.  At our recent  IT Executive Dinner with stakeholders from the Insurance industry, conversations were centered around application modernization, legacy application rationalization, and the funding mechanisms Insurance IT organizations use to improve their application assets.

3 Key Take Aways:

  1. The issues and challenges with legacy systems are pretty similar for everyone involved.
  2. The funding model for modernization, however, is not consistent among firms – some have an “ongoing improvement” approach and some think of it as part of a “transformation program”
  3. Non sequitur to the discussion, but there seemed to be consensus that Agile works pretty well with offshore.

Trends discussed:

  • Application Modernization - "the complexities on reducing cost and overall legacy applications continues to be a challenge, and we are looking for ways to manage this better" Saad Ayub
  • Legacy Application Rationalizaton = "rationalizing the portfolio is a continued challenge, and we are looking for efficiencies here " David Joy
  • Reusable assets or application components - "reusable assets and application components in the insurance industry are a 10x ROI" Billy McCarter
  • Sourcing and Vendor Management = "we need to move the needle and find SLAs that truly help drive cost and effectiveness" Bill Martorelli

All attendees agreed that portfolio rationalization and core application modernization is an ongoing journey. Legacy complexities were categorized by the group as coming from mainframe applications, customized packages or inter-application connections. Transformation programs offer an opportunity to improve the core application portfolio. Technical debt came up as a serious issue that, left unmanaged, can stall the ability of IT to continue to deliver for the business.

  This report describes the effects of different industrial factors on  structural quality. Structural quality differed across technologies with COBOL  applications generally having the lowest densities of critical weaknesses,  while JAVA-EE had the highest densities. While structural quality differed  slightly across industry segments, there was almost no effect from whether the  application was in- or outsourced, or whether it was produced on- or off-shore.  Large variations in the densities in critical weaknesses across applications  suggested the major factors in structural quality are more related to  conditions specific to each application. CRASH Report 2020: CAST Research on  the Structural Condition of Critical Applications Report
Open source is part of almost every software capability we use today. At the  very least libraries, frameworks or databases that get used in mission critical  IT systems. In some cases entire systems being build on top of open source  foundations. Since we have been benchmarking IT software for years, we thought  we would set our sights on some of the most commonly used open source software  (OSS) projects. Software Intelligence Report <> Papers
Making sense of cloud transitions for financial and telecoms firms Cloud  migration 2.0: shifting priorities for application modernization in 2019  Research Report
Load more reviews
Thank you for the review! Your review must be approved first
You've already submitted a review for this item