Every project begins with an objective—a goal. The Cloud migration project is no exception. One of the overarching goals of a Cloud migration project may be “achievement of business agility”. Business agility may be defined as the ability of a business to adapt or respond to changes in the environment and re-integrate itself nimbly. Cloud services package, balance, coordination, speed, reflex, strength and endurance and the resultant agility, with their offerings and is therefore an attractive option for those who seek business agility.
Like all other kinds of projects, Cloud migration projects that endow an enterprise with agility must begin with a plan. The plan can be divided into two clear parts. Each part must be meticulously executed.
In the first part, the planners must prepare the data for upload to the Cloud. This involves studying, categorizing data, identifying and defining domains, groups of users, listing, acquiring and allocating required resources, setting up controls, measures and monitoring capabilities and finally, uploading, managing and maintaining the digital assets in the Cloud. Each of these activities will have to be broken into their component parts and each activity component scheduled for execution within a specified time frame, so that there are no project overruns, resource overruns or other kinds of overruns that will drive up project costs and reduce the benefits that can be derived from the project.
The second part of the project plan will focus on identifying and signing up for a Cloud service that is best fit to the enterprise needs. This part of the project will involve listing out the service providers who match your requirements, studying their individual offerings, evaluating the security protocols in place, examining the Service Level Agreements (SLAs) and arriving at the final list of all the features and benefits that you can expect to derive from partnering with the service provider. This is a very complex procedure as no two service providers offer the same range of services using the same tools and technologies. The comparison will have to be at a broad level and several compromises will have to be consciously made by the enterprise. There is always a possibility that some of the trade-offs may prove expensive in the long term.
Fortunately, both these parts can progress in parallel and do not have to be taken up sequentially. This will result in some time saving.