Why IT projects still fail

[steve2470]

https://www.cio.com/article/3211485/project-management/why-it-projects-still-fail.html

In the age of agile development, devops and related management techniques, is IT project failure even a thing anymore? The answer, sadly, is yes.

In the past, IT failures often meant high-priced flops, with large-scale software implementations going on way too long and way over budget. Those failures can and still do happen. Case in point: IBM’s never-completed $110 million upgrade to the State of Pennsylvania’s unemployment compensation system.

But IT failure today is frequently different than in it was in the past, as agile, devops, continuous delivery and the fail-fast movement have changed the nature of how IT handles projects. These iterative management methodologies and philosophies are meant to minimize the chances of projects going spectacularly awry, but the fact of the matter is that IT projects still fail, just in new and sometimes more insidious ways.

Here’s what seven IT leaders and analysts say about the state of IT project failure today.

(more at link, obeying DU's 4 paragraph rule)

[beachbum bob]

1. i have seen major installs go wrong most my life becasues of

salespeople promising the sun and the sky and the deep blue sea to corporate management who themselves are clueless....and then they have these big dollar consultants come in with their stools and milk pans to milk the company dry...

projects go awry due to the same problems as always, incompetence and greed.....once you rid the projects of those elements, they usually go in fine

[SharonAnn]

2. #1 problem is "Scope Creep".