IT projects can still overrun or fail even when plans follow industry best practices. Past failures included inability to ship products due to lack of visibility into supply chain and inventory, though such issues are less common now. A large share of IT projects fail to deliver business impact. Going live with dashboards and monitoring does not guarantee the application solves business needs. Failures often stem from incorrect workflows, leading work to move outside the implemented IT systems. Temporary workarounds can become permanent, such as reliance on spreadsheets. Project teams may get stuck in long requirement iterations, losing alignment with the original vision and falling behind business change.
"These things are now fewer and far between." However, he says 75% of all IT projects often fail to deliver a business impact. Unpacking the reason behind these failures, he says: "You go live with something, data's moving and you are monitoring the system with dashboards, but [the application] never really solves the needs of the business.""
"In his experience, in cases where IT projects fail to deliver a business impact, often it is because the workflows are not right. What this means, according to Olkowski, is that over time, work starts to happen outside of the IT systems that the business has spent time and money implementing."
"Why this happens, according to Olkowski is because project teams get bogged down in the implementation. He says they spend so long iterating requirements with a group of people that they end up straying from the original vision. In addition to losing sight of the core project focus, he says: "You can't keep pace and speed with what's happening and changing with the business while you're doing all of this heavy lifting.""
Read at Computerweekly
Unable to calculate read time
Collection
[
|
...
]