Let's prepare a good action plan.
The “Asset Inventory” scope and the “Systems Dependency Map” area are worth assessing together with your current systems. A common list of dependencies helps indicate needed accesses, contact persons and activities that require prior preparation.
For "Performance Analysis" 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 continuity review" 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 “Maintenance and access assessment” 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. The following will be useful: a list of systems used and examples of situations requiring improvement. With this information, it will be easier for us to prepare a plan that meets the needs of your team.