最先，人事分配不善。发展趋势，迁移，新项目执行不成功 这便是云计算技术新项目经营的 怪圈 。云计算技术被炒得很火，因此那些IT企业里最有危害力的人便很快涉足在其中。可是，她们和首席信息内容官关联紧密其实不代表着她们一样有工作能力经营好云计算技术新项目。
以下两种经营方法必定会致使新项目不成功。第1种，将 1次运作终断便会摧毁业务流程 的程序流程植入云中，随后向那些互联网技术中的神灵祷告干万不必担任何错漏。这太探险了。此外1种就是将没人感兴趣爱好的程序流程植入云中，期待可以以此引发客户兴趣爱好。这类方式太不显眼了。大家应当找寻1种更加折衷的方法。
As best practices continue to emerge， so are the things that will kill your cloud project guarantee
Many panies are having great suess with cloud puting， and clear that the market continues to grow by leaps and bounds. However， with any new technology plays， there are those projects that do quick face-plants. These paths to failure are also emerging and highly avoidable.
Here are three surefire ways to fail with cloud puting， and what you can learn from them to avoid suffering that same fate.
First， put the wrong people on the project. This is the most mon way that cloud puting development， migration， and implementation projects fail. Cloud puting is a hyped "cool" space. So those who have the most political clout in an IT anization quickly position themselves on cloud puting projects. However， just because they are buddy-buddy with the CIO does not mean they have the architectural and technical skills to make the cloud work for the enterprise.
Bad decisions are also made in terms of deciding how to select technology types and technology providers. It's a manage-by-magazine world at many anizations. When you select what's popular versus what's a true architectural fit， you shoot yourself in the foot. I'm fixing a ton of these mistakes these days.
Second， security is an afterthought. This means that those driving the project do not consider security and pliance requirements until after deployment. It's almost impossible to retrofit security into a cloud puting deployment， so the approach and use of technology （such as encryption） should be systemic to the environment. This is a rookie mistake.
Third， select the wrong business problem to solve with cloud puting. The right approach is to pick new application development or existing application migration that is meaningful to the business， but that is not mission-critical.
There are two paths to failure here. The first is to pick the "kill the business with a single outage" type of application， put it in the cloud， and then pray to the Inter gods that nothing goes wrong. Too risky. The second is to pick a meaningless application that nobody cares about， move it to the cloud， and hope that somebody notices. Too underwhelming. Find something that falls in the middle.