The great comedian Sid Caesar said it best. “The guy who invented the wheel was an idiot. The guy that invented the other three…. he was a genius!”
We must have been channeling our “inner Sid” when we published our recently released white paper, The Case for Cloud, detailing the path to developing a proper cloud strategy. Amazon Web Services (AWS) and Microsoft Azure wrote the book on utilizing software-defined methodologies to power a proper cloud architecture. We took that prototype, added a few wheels, and put together a model private/hybrid cloud environment to power businesses and healthcare organizations of all sizes.
Last week, we profiled a few leading vendors in the software-defined space. Today, we take a look at what your cloud migration plan should include, minus a reinvented wheel!
When developing a comprehensive cloud strategy to safely and effectively leverage these new platforms and capabilities, taking stock of internal resources and organizational design is paramount. The classic mantra of “People, Process, and Technology” fully applies to this cloud strategy and is an essential first step in the transformational process.
A solid cloud methodology includes four core phases:
We focus on several critical success factors regarding the planning and execution of the transformational process. These are not listed in order or priority and are prevalent throughout the engagement process.
- Cloud transition can fit into current OPEX and CAPEX budgets
- Organization modeling is critical for effective collaboration
- Setting the “Pace of Change” to match business needs
- Implementation enables strategic IT alignment with the business
- Planning can produce early program ROI
- Results deliver real competitive differentiation
Designing and deploying such a cloud-based infrastructure requires a new approach within IT: the traditional technical disciplines must be broken down in favor of seamless cross-functional teams focused on Architecture, Engineering, and Operations. Traditionally these teams frequently operate in technical silos rather than by a collaborative team approach. Placing these functions into cross functional teams allow for a deeper collaboration across disciplines. Collaboration across these three IT teams enables essential sharing of knowledge of long-term strategies, current implementations and day-to-day operational results.
Collaboration across these three IT teams enables essential sharing of knowledge of long-term strategies, current implementations and day-to-day operational results. All three teams working together ensure optimal alignment with business stakeholders. In addition to optimizing IT/Business results, increased collaboration across teams results in a higher engagement level of all resources leading to lower turn-over of critical staff.
The only “cloud” Sid Caesar ever saw was the one surrounding Imogene Coca’s head, but there’s truth in his words when it comes to developing a cloud strategy for businesses and healthcare organizations. Don’t reinvent the wheel. Model your environment after the guys who did it first, and adapt it to make it work for you.