As Cloud Computing gathers momentum, it promises significant cost-savings, gains in efficiencies realized by speed, flexibility, rapid and agile development processes, and at the end of the day – lets businesses focus on their core competencies reducing some worry and effort that had to be done in the past on non-cloud environments.
Figure 1 shows a typical decision process at the highest level, an organization may go through before deciding to make their Cloud Journey. (Disclaimer: This is a high-level diagram and may be different for each organization depending on the approach)
Businesses making the Cloud Computing journey will realize, it comes with a variety of opportunities and challenges. Big decisions, that are unique to each role, are included with a perspective unique to that role. In the following, I’ve tried to capture the “top three” relevant points.
Business Leadership: They are bombarded with Media Coverage, and articles in journals and trade publications. They are probably thinking: – What’s Real and What’s not? The biggest concern is looking past the hype to see if the requirements can be met “on the Cloud.”
CIO: The CIO is reading the same press and is likely inundated with requests from the business and IT leadership for a Cloud Strategy. Perhaps the CIO is thinking of “Not a question of Why, but rather “When”.
Figure 4, shows the CTO, the CIO’s right hand person in making key technology decisions in an Enterprise. It is highly probable the CTO is concerned about New Technology Adoption and Introduction as well as thinking of how the puzzle will come together. The CTO could also use a Converged Technology Roadmap.
The Enterprise Architect, is meanwhile thinking of how to make the puzzle fit at the next level of detail.
Meanwhile, the Infrastructure Leader is likely thinking about virtualization layers, and data-centers, capacity planning and such.
As the organization analyzes the impact, the IT Operations Leadership is likely wondering about alarms. This team is being alerted when a resource thresholds are crossed, and wondering if they would need to worry about applications and platforms running in the Public Cloud. They also focus on including service level agreements that may need to be reworked.
The Software Developer is likely loving the freedom offered by the Cloud and the efficiencies, but is also thinking if Tools and Projects have to be changed in a big-way or is the change and migration to Cloud, a seamless process.
The System Administrator is likely thinking about how to bridge capacity (also called Cloud Bursting) in some circles, possibly a new software layer and certification process. Some may be wondering if they are needed to work on a Public Cloud, or just on the Hybrid and Private Clouds.
The Project Manager, often the “cat-herder” and the person held responsible for making it a success, is likely thinking about Vendor Qualifications, the Software Development Life Cycle (SDLC), and the Release Roadmap.
The Security folks are likely wondering about the safety of using the Cloud – from different dimensions and aspects. After all, using a data center or servers connected to the Internet, is a new paradigm.