Why your Software Technical
Quality is vital
for Business Growth
4 MIN READ /
Software Consultant | code4thought
Is the Technical Quality of your Software Good Enough to Achieve Business Growth?
To complement, EY’s partner John De Yonge says “To realize sustainable competitive advantage CEOs must embrace three interconnected value drivers: humans at the center, technology at speed, and innovation at scale.” in his article “The CEO Imperative: How can today’s leaders realize tomorrow’s opportunities?”
- Technology is a top priority and the main driver for the sustainable future of an organization.
- The vehicle for an organization to achieve growth is the realization of competitive advantage.
Why is competitive advantage a factor to achieve a sustainable future and growth for your organization?
- Home Depot: On 11/21/2020, six years after its 2014 data breach, Home Depot agreed to pay US states $17.5 million for an incident that compromised the payment card data of 56 million individuals.
- Heathrow Airport Disruption: On February 16, 2020, more than 100 flights were disrupted when their departure and check-in systems were hit by “glitches.” This was fixed by the next day.
- Google Plus Security Glitch: A vulnerability in the Google+ social network exposed the private information of nearly 500,000 people using the social network between 2015 and March 2018. The major part of the problem was a specific API that could be used to gain access to non-public information. The software glitch allowed outside developers to see the name, email address, employment status, gender and age of network users. The error had been discovered in March 2018 and rectified immediately.
- NASA/Boeing Starliner: NASA awarded Boeing nearly $5 billion to develop the Starliner spacecraft, which is built to carry as many as five people. Now more than three years behind schedule, the project is under heavy scrutiny from a NASA investigation. Additionally, NASA confirmed that Boeing’s Starliner suffered not one but two major software defects during that test flight. The latter software problem could have caused “catastrophic spacecraft failure,” a panel of NASA safety experts said if Boeing had not caught the issue during the mission. The second software issue was a piece of code that could have caused two pieces of Starliner – its “crew module” and “service module” – to collide in orbit before the spacecraft re-entered the atmosphere. “What we wish we’d done better was the software, so there’s a lot of learning there,” Boeing Senior VP Jim Chilton said.
- Losses from Software Failures (37,46%)
- Legacy System Problems (21,42%)
- Technical Debt (18,22%)
- Finding/Fixing Defects (16,87%)
- Troubled/Canceled projects (6,01%)