7 Steps to a Successful Linux and Open Source Migration - Part Two of Three
In our last blog post, we discussed the first three of seven steps to a successful Linux and open source migration and adoption. They were… (1) define your business level objectives, (2) survey your application landscape and environment, and (3) develop a scalable infrastructure blueprint. You can read that previous blog post here.
Here are two more tips that will help you achieve a smooth Linux migration:
This step is more complicated than simply choosing one of the applications from the first step. In this step, you’ll need your financial analysis and management skills front and center. To move forward, secure management commitment and executive-level sponsorship. You don’t want to start this level of infrastructure change without support from top management and a specific, named champion at the top.
Generally, it’s easiest for you to secure this level of management support through an objective financial analysis that documents proper validation and justification for the business-level objectives you identified in the first step. You’ll need to identify the business drivers and assess the return on investment (ROI) and total cost of ownership (TCO) considerations and implications, making sure to document both the hard and soft dollars involved.
Here you’ll begin the technical work. Surprisingly, the success of the migration rollout depends not only on the organization’s understanding of the importance of Linux and open source but also on all the ramifications of the technical changes that will be facing the company. Therefore, you’ll want to conduct pilot studies and build appropriate interoperability labs that will provide the necessary training, usability studies, and technical validation to ensure project success. This is your first chance to discover the technical and operational issues that could delay or derail the project. (If your migration project is destined to be delayed or canceled completely, it’s best that you discover it during the pilot study before you commit to the full expenditure.)
To reduce the likelihood of problems that may lead to delay or failure, you should also set up and test ongoing project management and risk management processes. This includes assembling your application testing labs, refining your change management processes, and initiating training and team building efforts.
Just two more tips left and they’ll be posted in our next blog. As always we’d love to hear your thoughts on migration experiences you’ve undertaken, so drop a comment.