As good as the vision of a cloud-first strategy may sound, successfully putting it into practice is another story. Having already clarified the Cloud journey and looked at the process of envisioning, we will shift our focus today on how to develop a roadmap. Roadmapping for your migration is the single most important effort of your entire cloud journey. The success of your project will depend on it!
A roadmap, complete with milestones and planned resources, is an essential tool for stakeholder communication. It creates transparency concerning the time frame, the initiatives, and impacts on the organization. The roadmap—for example, in the form of a GANTT chart—allows those involved to visually see the cloud migration process for the first time, while the descriptions of the vision often include idle words and phrases.
Building the roadmap and collecting qualitative and quantitative infrastructure information requires the most time and effort. It is easy to be overwhelmed by the sheer volume of information, data, dependencies and options, even though numerous assessment tools are offered with the promise of providing a simple decision template for preparing your migration process.
In reality, objective data on server operating systems, CPU utilization and memory often meet carelessly maintained databases with information about related applications, roles and planned service life. Gathering the information concerning the applications used and identifying the service or application owners can take months. Time and resources are required to conduct interviews, research information, and to retrospectively enter and/or maintain the data in the database or CMDB. Months can go by without being able to present visible results to the IT organization and the board of directors, who need to be motivated for the cloud migration project.