Joel, I have seen plenty of failed technologies that sunk projects. Remember the baggage system at the new Denver Airport when it opened? Bags that were supposed to go to Dubuque went to DeKalb...
Perhaps, the failure of the Denver Airport baggage system was as much a people failure as it was technology, no?
Obviously, you need buy-in before a project launches. Let the users (employees) think they developed the system...that it fit their needs. I did a post on General Electric's new Proficy manufacturing execution software (link below) and the head of that program talks at length about how it got buy-in from plant managers and factory floor engineers. Anything short of that usually spells failure....
Imagine having thousands of applications to put into the cloud. What are the steps to taking on such a massive project? Well, this is what I told a customer who informed me that he had five thousand apps to migrate into the cloud. I suggested a six step approach.
1) Understand the vision, establish the priorities
I don't agree with David Linthicum's post in InfoWorld that contends the IaaS and PaaS markets will no longer support smaller providers. He also argues that the little guys will have to exit those markets and find something else to do.
While getting into the cloud fast can seem attractive, a deliberate step-by-step approach is the wisest course. Rushing to the cloud without considering all its implications is not a good idea. So here are five steps to consider as you evaluate cloud options.
Companies are adopting the cloud as they realize more and more benefits. Few jump in whole hog based on the cloud hype and there's been plenty of that. Still, as the cloud becomes more mainstream, new terms crop up.
By 2030, the amount of data is forecast to have grown to 1 Yottabyte (a lotta bytes, for sure...think 1 followed by 24 zeroes). That was the prediction of Martin Saddler from HPLabs, who I heard make a presentatation in London a few weeks ago.