The Journey to Amazon public Cloud
One of the most spoken trends in IT world today are cloud services, and many organizations are checking the possibilities of moving to the cloud, There are several possible ways to migrate large-scale data centers to the cloud, and several aspects we should consider before, during and after starting the transition to the cloud. Amazon Web Services – the largest public cloud as of today, have several services and tools to ease the project, lower the risk and expenses.
This article suggests using approach, based on of best practice for this kind of project management and decision-making, to achieve a successful migration to Amazon cloud, while minimizing unnecessary expenses and maximizing ROI.
The objectives of this article:
- AWS Cloud Adoption Framework – general approach that Amazon support of migration project
- financial aspects of the project
- Prioritization – what considerations we should take into account when we prioritize and put into order the entities and applications we are migrating to AWS.
- How different project management approaches (Traditional, Kanban/Lean) can be used most effectively
- Using key AWS services to lower project risk and difficulties.
- How to measure completion criteria – when is it the time to migrate to the cloud and turn off the old services.
Organization’s typical phases of migration to the cloud:
- early adaptors
- Development & Test – R&D’s need are often changing so adopting cloud computing resources to speed up availability of temporary resources – A cloud is a natural option when you need a computing service for limited time.
- New applications – New applications require new computing resources, so naturally the cloud is a good option for more computing and storage resources.
- Early Majority
- Critical Mass
- Data Center Migrations
- Mission Critical Apps
- All in – or stopping in a hybrid point anywhere along the path
The migration project
To gain the most of the AWS platform, a critical point is to design a model for cloud migration that delivers optimal cost efficiency.
The model should include a winning case, education of IT organization for new skills, re-engineering of business processes and definition of the application migration methodology to transform your business model from the legacy platform to a cloud infrastructure.
Migration Project will desire to have predictable Start and end dates, direct cost and Overlapping cost – should be predicted and budgeted -Capital expense should go down to zero during migrations – i.e., – only for repair.
Take into consideration that Operating expense will increase significantly due to overlapping costs in the project time, then drop down below the previously budgeted level when direct cost closes.
Lower the risk – be ready for the project
- Train your teams while doing the work alongside the professional service staff
- Financial planning and ROI analysis – budget for overlapping expenses
- Discuss the merits of DEV/TEST and new project first approach – does this make financial sense?
- Understand that traditional project management will not work well
- Use agile methods- minimize the risk at each phase
- Reduce the overlapping burn rate – this is a real pain
- Consider avoiding the “Hybrid trap” by moving the heaviest workloads first
- Maximize the use of current app performance review, ticket counts, high severity events – this is a real pain killer
- Help the financial team budget for the CAPEX vs. OPEX transition and planning