Let's prepare a good action plan.
The "Servers and Application Resources" scope and the "Network and Access Segmentation" area are worth assessing together with current systems. A common list of dependencies helps indicate needed accesses, contact persons and activities that require prior preparation.
For "Account Administration" 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 "Backup and recovery attempts" area requires agreement on responsibility and how changes will be made. 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 "Coordination of system suppliers" section, the transfer of knowledge 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. The following will be useful: a list of applications and devices used and examples of problems. After a joint review, we will be able to prepare a plan that meets the needs of your team.