6 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
The article examines the persistent failures in software development despite increased IT spending over the years. It highlights the reasons behind these failures, such as poor project management and unrealistic expectations, using examples like the Canadian Phoenix payroll system. The piece questions why the industry continues to overlook lessons from past failures.
If you do, here's more
Software failures remain a pervasive issue despite massive increases in global IT spending, which has risen from $1.7 trillion in 2005 to $5.6 trillion in 2025. The success rates for software projects haven't improved significantly over the last two decades, resulting in growing business and societal costs. Many failures stem from human errors like unrealistic goals, poor risk management, and inherent project complexity. The author emphasizes that the majority of software failures involve known issues, which raises the question: why haven't we learned from these past mistakes?
A striking example highlighted is the Canadian government's Phoenix payroll system, which was intended to modernize payroll processing for 430,000 employees. Launched in 2016, the project quickly led to widespread paycheck errors affecting around 70% of those paid through the system. The government’s approach, which included cutting essential testing and reducing the workforce involved, doomed the project from the start. Nearly 350,000 errors remained unresolved by March 2025, with a backlog that continued to grow, causing severe financial and emotional strain on employees.
Debates about software project failure rates persist in the IT community, but one fact stands clear: software development remains one of the riskiest endeavors. A report indicates U.S. organizations spend over $520 billion annually on legacy systems, with 70-75% of IT budgets allocated to maintenance. While newer methodologies like Agile and DevOps aim to improve the process, reports claim high failure rates for these approaches as well. The underlying challenge is a lack of organizational commitment to implement proven practices, leading to a cycle of failures that continues to plague the industry.
Questions about this article
No questions yet.