IT Project Failures: A Report on Case Studies and Lessons Learned

Desklib provides past papers and solved assignments for students. This report analyzes IT project disasters and offers mitigation strategies.

Contents
Abstract:......................................................................................................................................................2
Introduction:...............................................................................................................................................2
IT Project Disasters:.....................................................................................................................................2
Disaster 1: 2007, “Computer Issue” at LAX..............................................................................................2
Disaster 2: Queens Land Health Care, 2006.............................................................................................2
Disaster 3: AusNet, 2015.........................................................................................................................3
Findings:......................................................................................................................................................3
Conclusion:..................................................................................................................................................3
References:..................................................................................................................................................4

Abstract:
This assessment is regarding the malfunctioning that has been taking place for a long time in the field of
Information Technology. Reviewing those cases again, analyzing them, identifying the problem on our
level and providing the conclusion is the main objective of this assessment. Disasters in the field of
Information Technology can lead to a massive loss of money as well as a trust to the people that are
connected to this network.
Introduction:
In this report, some of the disaster and chaos in the IT field has been researched. People have been
using the networks, internet, remote connection, software, application and many more products of the
IT field, but sometimes, in the past cases, people and industries had faced some major issues like system
failure, system glitch and many more. In this assessment, these issues are researched and provided a
conclusion according to each case scenario. And also, findings according to some past cases and projects
that should consider when working on IT projects.
IT Project Disasters:
Disaster 1: 2007, “Computer Issue” at LAX
In 2007, As a consequence of a software problem with Border Protection Agency system the U.S. at Los
Angeles International Airport, about 17,000 passengers were grounded in the year 2007. After all the
investigation by the associated department, the problem that came up was a network card that
continued sending improper data across all the networks taking everything to an end, instead of shutting
down. This resulted in an eight-hour shutdown of the system in which no tourist could leave or enter in
Los Angeles.
Conclusion 1: To manage this kind of risks, A backup plan should be there that can be implanted
whenever thing go wrong.
Conclusion 2: Buying cheap parts for some critical mission essential applications can damage the whole
network or might lead to this kind of disaster.
Disaster 2: Queens Land Health Care, 2006
In 2007, on the orders of the ALP government, IBM Australia created a Payroll system for the Queens
Land Health care. This system went live in 2010 with a major glitch. The system wasn’t able to pay an
adequate amount of salary to the staff. Some were being overpaid, some underpaid and some weren’t
even paid. "It appears that IBM took the state of Queensland for a ride," Queensland Premier Campbell
Newman said after this malfunctioning. He also told parliament, "It could be the worst failure of public
administration in this nation."
To fix this malfunctioning, estimation was, it would take about eight years to fix it and would cost about
$1.25 billion to the Queensland government. Hence, a long legal battle begins between Queensland
Health Care and IBM Australia that hasn’t ended yet.
Conclusion 1: Make sure key software programs are functioning well on a minor level.

Conclusion 2: System should be tested on many levels before going live.
Disaster 3: AusNet, 2015
In 2015, AusNet had to pay $28.75 million to hundreds of thousands of their
customers because of a glitch in their smart meters and that lead to an
unbalanced IT system. Half of their meters were worsening to remotely transmit
electricity use data and remote connection which affected 230000 of their
customers. After that, as compensation to the customers, on the order of
Victorian government, AusNet had to refund $125 to each customer. The
organisation also has to spend $175 million to fix the malfunctioning in the
smart meters of the Victorian government.
Conclusion 1: Focus more on the system stabilization mainly in the case of
remote connections.
Conclusion 2: Instant shutdown of the network of the system as the problem
came into notice could save some money and trust of the customers.
Findings:
By the entire mentioned scenario, the main finding that came up is IT projects
aren’t that easy to work on and also if there is a system failure, application
failure or network crash, it isn’t easy to distinguish the problem before it is late,
even IT experts take time to shut down the system or find out the problem. But
once, when the problem is identified, there should be a backup plan, backup
system or emergency shut down for the network to lessen the loss of money
and trust as well.
Conclusion:
In this paper, all the major issues and problems raised in the field of Information
Technology have been discussed and also concluded according to each case. IT
world is a big world and also getting bigger by time but as the invention are
increasing, a number of disasters, chaos, malfunctioning also increasing day by
day. All one can do is learn from past mistakes and try to recover the faults in
their new project.

References:
Clark, T. (2014). The 4 top it project management disasters of all time. Retrieved from:
https://www.liquidplanner.com/blog/4-top-project-disasters-time-lessons/
Fielding, L. (2015). Top 10 it disasters: why you need a disaster recovery plan. Retrieved from:
https://macquarietelecomgroup.com/news/top-10-disasters-need-disaster-recovery-plan/