Dennis Moore, General Manager for Emerging Solutions at SAP, spoke at the Enterprise 2.0 Conference about integrating web 2.
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.
Andrew McAfee made the following comment in a debate with Tom Davenport at the Enterprise 2.
This is a bit off-topic, but as someone who has been around the fringes of book publishing for years, I find it fascinating.O’Reilly is about to offer their books on a single-chapter basis, in addition to the traditional mode of whole-book sales.
I’ve started a photo-sharing site on Flickr. If you are curious at all, take a peek!
The Journyx project management blog offers the following advice when managing software development projects: Don’t reward for shipping on schedule. Anyone can ship garbage.
SearchCIO sponsored development of a white paper, called As the World Turns: CIOs and their ERP Dramas (registration required). It describes the risks.
Big4Guy writes a blog on big software deployments. His posting on Five Common ERP Implementation Pitfalls has the ring of truth for me, so here they are:Pin-pointed clarity as to why we are going in for an ERP.
Walt Mossberg, consumer technology columnist for the Wall Street Journal, called large corporate IT departments “the most regressive and poisonous force in technology today.” He was giving a speech to 250 university presidents.
In my experience, many project failures can be traced back to poorly written requests for proposals (RFPs). When you buy the wrong thing, you get the wrong result.
From an unpublished work by Axel Angeli, noted author and project expert:Sages and Dunces Projects fail because people are stupid, no doubt. But it is seldom the case that team members are stupid.