Software project failure

In big company, most departments can do their job perfectly, but the problem is that they don't communicate with each other. Take a look at this link.

Titanic Lesson for IT Projects

http://books.google.com.au/books?hl=en&id=UD-r7m2qdsoC&dq=titanic+lessons+for+it+projects&printsec=frontcover&source=web&ots=izMM_v4NCs&sig=U2-X0WkYMDwERR9hXkmvVypN_vk&sa=X&oi=book_result&ct=result&redir_esc=y#v=onepage&q=titanic%20lessons%20for%20it%20projects&f=false

In this book, what astonished me was not the lost caused by software failure, but that there are so many problems which seemed could be predicted and avoided. 

"IT projects have terrible track records. I just don't get why people don't learn,"   Mark Kozak-Holland.

http://spectrum.ieee.org/computing/software/why-software-fails

"The average company spends about 4 to 5 percent of revenue on information technology, with those that are highly IT dependent--such as financial and telecommunications companies--spending more than 10 percent on it. In other words, IT is now one of the largest corporate expenses outside employee costs. Much of that money goes into hardware and software upgrades, software license fees, and so forth, but a big chunk is for new software projects meant to create a better future for the organization and its customers."------cite from "Why Software Fails", IEEE

There are so many software failure may because that most companies didn't really understand the risk of software failure, or they didn't think they would fail on such a simple thing. Most executives may not know that once software was implemented, the whole systems would mess up and could hardly go back to the original stage. They treat software as hardware and think it can solve problems as soon as they are installed. That's why they spend so much money on it.

If we take a look on cases in these links, we can easily find out that most failure just repeat itself over and over again. It's all because of lack of a holistic and higher view on problems which they want to fix or on futures which they want to reach. These executives need EA to build a standard to link multiple IT networks, systems, applications, services, and databases across the entire enterprise, sharing information between departments and lines of business. By doing so, enterprises can not only save software cost, but also improve whole performance.

IT's biggest project failures and what we can learn from them

http://www.computerworld.com/s/article/9116470/IT_s_biggest_project_failures_and_what_we_can_learn_from_them

Failure example of IT project

http://www.it-cortex.com/Examples_f.htm

When executives set an IT project, they should consider about the risk of failure and the elements that may lead to failure, just like they consider about other investment. Besides, big enterprises may have similar problems. They should research about other failed cases in advance, trying to avoid the same causes. 

--
Here's a video which talks a lot about software failure.
http://blip.tv/tucs-tech-talks/an-illustrated-history-of-failure-2729174