Digital transformation is a project many business executive leaders have recently taken on, especially those in banking and financial services. These organizations are competing to digitally transform front-end systems that are connected to brittle legacy systems. The subsequent failure to identify the structural vulnerabilities in combined applications, produces security and reliability issues the negate the value of digital transformation.
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 business. There 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.
We knew that the most recent findings from our 2014 CRASH Report would cause a stir among the software development community — especially Agile advocates — but we were pleasantly surprised by the overwhelmingly positive reception the news received. Continue reading
Research shows applications built using a mixture of Agile and Waterfall will result in more robust and secure applications than those built using either Agile or Waterfall alone. Continue reading
Last Thursday we had a fascinating discussion with Suresh Bala, the head of Application Management at Wipro, Diego LoGiudice of Forrester, and Dr. Bill Curtis, the Director of the Consortium for IT Software Quality. Diego presented the latest trends in IT organizations in reference to splitting their activities and applications into systems of engagement and systems of record. This has been the Forrester view on IT, or what they call Business Technology (BT), for some time now. The systems of engagement being the fast-moving, often mobile-based, applications that are meant to disrupt competition and engage the customer in new ways. The systems of record being the traditional backbone IT systems that manage the core enterprise data and business processes.
Suresh Bala described how Wipro closely manages the software product in order to improve short- and mid-term agility on behalf of their clients. Suresh described an impressive system of tools that underlie their own Agile processes, while proactively managing technical debt. He also presented a pretty advanced scorecard, called AppInsight that they use in order to track how the applications under Wipro management are doing from a health and robustness standpoint.
Then, Bill Curtis took us to the conclusion by describing the metrics being standardized by CISQ, and how these measures can be used to manage the evolution of software, and to provide standard terms for software quality in application services contracts.
Agile software development is a streamlined, transparent process with speed built into each step. It’s so focused on speed, in fact, that developers call what they can successfully accomplish in a two week sprint their ‘velocity.’ But while Agile development teams do incorporate unit tests and the testing of functional aspects of their code, there is often little analysis of the structural quality above the module level. This is something that makes most architects in enterprise software organizations nervous about Agile.
From IT’s perspective, the business is always asking for new applications — apps to innovate, or simply make their jobs a little easier. The problem is, it always want them done quickly and be up and running perfectly at launch.
Our very own Dr. Bill Curtis sat down with ComputerWeekly to discuss the challenges of maintaining this level of development while simultaneously ensuring the application’s performance and resiliency. You can hop over to ComputerWeekly to read the full article here.