Timothy Johnson describes how he was fired for writing truthful project management reports. Well, the reports didn’t make the project manager look very good, so I imagine it must have been a wee bit awkward for all concerned.
Beyond IT Failure
Michael Krigsman is a recognized authority on the causes and prevention of IT failures.
Michael Krigsman is recognized internationally as an analyst, strategy advisor, enterprise advocate, and blogger. Interact with Michael on Twitter at @mkrigsman.
An Infoworld article by Dan Tynan describes what can happen when the IT vendor who once loved you now hates you. From the article:…consider this cautionary tale of a small biotech firm in the Rocky Mountains that decided to dump its IT consultant.
In an article at SearchCIO, Linda Tucci describes a massive, $1.9B IT outsourcing deal between DuPont and CSC.
Aligned Strategy points to an article on how to hire a CIO. The article includes the following action items to address during the CIO hiring process:A high level IT strategy tied and aligned with the business plan (this is a starting point for the new CIO who will expand, refine and institute the full IT strategic plan).
David Jacobson makes reference to a Harvard Business School excerpt from a book titled Alignment: Using the Balanced Scorecard to Create Corporate Synergies. As David points out, the article says:Following are the eight alignment checkpoints for corporate, business units, and support units of a typical multi-business organization to hit during the annual planning process.
Thomas Otter asks "How long does it take to implement SAP?".
Dear Gentle Reader,I’m looking for stories about failed IT projects. Please help me find these "hidden gems.
CIO magazine has an article written by Allan Holmes, describing Maine’s attempt to develop and deploy a web-based system for processing Medicaid claims and payments. The project was started back in 2001, to help the state to modernize its systems and also ensure compliance with the Health Insurance Portability and Accountability Act of 1996 (HIPAA).
In a post titled IT project failures, Charlie Bess makes an insightful comment about a subject that should be obvious, but is often overlooked:Since the only reason the project exists is to achieve business benefits. Project managers need to have the business needs as the project objective.
The Wisconsin Technology Network has an article titled "Consultant says beware hidden costs of bad IT projects". Generally, the premise of the article is correct, that there are lots of hidden pitfalls that can cause serious damage to a project.