Let's prepare a good action plan.
The "Selection of CPU, RAM and disks" area and the "Linux and Windows Server" area are worth assessing together with the current systems. A common list of dependencies helps indicate needed accesses, contact persons and activities that require prior preparation.
For "Virtualization and Clustering" tasks, we determine what data and resources are needed for testing. Acceptance scenarios should correspond to users' daily work and indicate how to recognize the correct result.
The "Application and data migrations" area requires agreement on responsibility and the method of introducing changes. If the project combines several teams or suppliers, we describe the boundaries of their tasks and how information about the problem is communicated.
In the "Backup and recovery" section, knowledge transfer is also important. Documents and arrangements should remain available to authorized persons so that subsequent handling does not depend solely on the memory of the implementation participants.
Before starting work, we will determine the purpose of the project and the most important dependencies. A description of current tools and information about the expected date will be useful. With such information, it will be easier for us to plan the right first stage.
