IBM recently announced a new line of “standardized” service offerings. ComputerWorld has an article today expressing some concerns from customers, who wonder whether they will continue receive the same level of service from IBM as in the past.
Beyond IT Failure
Michael Krigsman is a recognized authority on the causes and prevention of IT failures.
Michael Krigsman is an internationally recognized analyst, strategy advisor, and authority on enterprise software leadership, CIO innovation, and social business. Interact with Michael on Twitter at @mkrigsman.
The UK National Health Service (NHS) is in the midst of a £12.4 billion IT project meltdown, which has been called the “greatest IT disaster in history”.
A report by the Work Foundation in the UK is sharply critical of public sector ICT (information and communication technology) projects, saying that “too much recklessness blights government IT projects.”The press release includes the following tidbits:Contrary to the stereotype, public sector managers have sometimes been too gung-ho in their attitude to risk when developing and implementing information technology projects, wasting many millions of pounds of taxpayer’s money in the process.
Well, this is unusual. New Age Electronics has promoted Sam Changizi, its Director of Information Technology, to the position of CIO.
Hourly billing arrangements are typical on IT projects. However, open-ended billing can create an incentive for consultants to work lots of hours, potentially increasing project duration and cost beyond what may strictly be required.
Vinnie Mirchandani posted an insightful comment on this blog related to software implementation time and cost. He correctly points out that even so-called “successful” implementations often run substantially over-budget.
ComputerWorld offers a ten-point prescription for rescuing a failed project. From the article:Denial can also come into play.
Dear Gentle Reader: Please forgive the digression, but this post is not about project failures.Occasionally something comes along which I want to share.
The following quote is taken from an article explaining key differences between open source and commercial ERP software:Open Source ERP does not require much training. The source code is more than a training manual.
Dan Tynan writes in InfoWorld about consultants who seem to hang around forever and suggests methods for escape. You know the type: they rack up endless billing for their clients without much to show for it.